DMfetch

Privacy Policy

Effective date: 17 November 2026

DMfetch is a tool that replies to comments on Instagram posts and sends direct messages for the Instagram professional account that has connected to it. It is run by Ozaru Limited, a company registered in Hong Kong (Room 401, 4/F, Silvercord Tower 1, 30 Canton Road, Tsim Sha Tsui, Kowloon, Hong Kong) (“we”, “us”). Contact: [email protected].

Who is responsible. For the data of people who comment on or message a connected account (“viewers”), the account owner decides why and how it is used, so the account owner is the controller of that data. Ozaru Limited processes it on the owner's behalf, through the settings the owner writes. For the data of people who create a DMfetch account (“account holders”), Ozaru Limited is the controller.

What DMfetch does

When a person comments a keyword on a post of a connected account, DMfetch can post a public reply and send that person a direct message, such as a link to a guide. It can check whether the person follows the account before sending the guide. The account owner decides which posts, keywords and messages are used.

Who this covers

  • Account holders: people who create a DMfetch account, with Google or an email address and a password, to connect and manage their Instagram professional accounts.
  • Account owners: people who connect their Instagram professional account to DMfetch.
  • Viewers: people who comment on a connected account's posts or message that account.

Data we receive and store

From the account owner, through Instagram / Facebook Login

  • Instagram account ID and username, and the Business portfolio ID the connection came from.
  • An access token that lets DMfetch act for the account. It is stored in our database and used only to call Meta's APIs for that account.
  • The settings the owner writes (keyword, post ID, reply and message text).
  • If the owner also connects a Facebook Page or a Threads profile: its ID, name or username, and an access token, used the same way. Threads has no direct messages, so on Threads DMfetch only posts public replies.

From people who create a DMfetch account

  • Your email address, and the name you give (optional).
  • A one-way hash of your password, if you set one. We never store the password itself.
  • If you sign in with Google: your Google account ID, name and email address, as Google shares them.
  • Your sign-in sessions (with the browser's user agent), sign-in attempts (used to limit repeated guesses), and the hashed form of any API tokens you create.
  • We use these only to sign you in, to send account emails (email verification and password reset) and to show which accounts are yours.

From viewers, through Meta's webhooks and API

  • Instagram-scoped user ID and username, the comment or message ID, and the comment or message text, which we need to match a keyword and respond.
  • Whether the viewer follows the account, when the follow check is used.
  • An email address, only if the account owner turned on the email step and the viewer types an address in reply. It is stored on the viewer's contact record, shown to the account owner in their contacts list, and the owner can export it. DMfetch itself does not send email to it.
  • Progress through a funnel (for example “gate sent” or “guide sent”), which tracked link the viewer opened and when, and an opt-out marker if the viewer asks to stop.

Technical records

  • An event log of what DMfetch did and why (type, IDs, time, error reason). For a matched comment it includes the commenter's username and the first 200 characters of the comment. It shows the owner what happened and helps fix failures.
  • A temporary copy of each webhook message from Meta (the raw message, including usernames and comment or message text), so it can be retried if processing fails.
  • For account holders, a sign-in session (user ID, workspace ID, expiry, browser user agent) and a browser cookie that identifies it.

We never see your Instagram or Facebook password: you sign in on Meta's own pages. If you create a DMfetch account with a password, we store only a one-way hash of it. We do not sell data, show ads or build advertising profiles.

How we use it

  • To create and secure DMfetch accounts and workspaces.
  • To run the reply and message flow the account owner set up.
  • To show the account owner what happened, including failures.
  • To keep the service secure and working.

We do not use the data for anything else.

Who we share it with

  • Meta Platforms (Instagram, Facebook, Threads): we send replies and messages through Meta's APIs. Meta's own privacy policy applies to its services.
  • Google, if you choose to sign in with Google: it tells us who you are. Google's own privacy policy applies to its service.
  • An email delivery service that sends our account emails (email verification and password reset) for us.
  • Our hosting: the app and its database run on a server at a cloud hosting provider. Traffic reaches the server through Cloudflare, which processes it on our behalf. These providers may not use the data for their own purposes.
  • We disclose data if the law requires it.

How long we keep it

  • Raw webhook copies: deleted 14 days after they are processed. Webhook de-duplication records: 14 days.
  • Event log (including the comment excerpt): 180 days.
  • Tracked-link records (which link a person opened, and when): 365 days.
  • Sign-in sessions: expire after 30 days and are deleted 14 days after they expire. Sign-in attempt records and used or expired email links: deleted 14 days after they are recorded or expire.
  • DMfetch account (email, name, password hash, Google ID): kept while the account exists, and deleted when the account holder deletes their workspace or asks us to.
  • Account, token, settings, viewer funnel records and contact records (including an email address, if one was given): kept while the account stays connected, and deleted when the owner disconnects and asks us to delete them (see the data deletion page).
  • Opt-out markers: kept until you ask us to delete them. Keeping one is how we make sure you are not messaged again; if you have it deleted, a later comment may start a new message.

Your choices and rights

  • Account owners can disconnect DMfetch at any time in Instagram (Settings → Website permissions → Apps and websites). That removes the app's access straight away. To have the account's stored data deleted, email us as described on the data deletion page.
  • Account holders can delete their whole workspace themselves at any time: Settings → Delete my workspace. This deletes the workspace's connected accounts, automations, contacts, activity and connections, and your DMfetch login.
  • Viewers can start a message to the account with “stop”, “取消” or “unsubscribe” as the first word to stop messages, or ask the account owner, who controls the data, or us to delete the data we hold about them.
  • To access, correct or delete your data, follow the steps at https://dmfetch.com/data-deletion or email [email protected]. We reply within 30 days.

Security

Tokens and data are stored in a private database that is not exposed to the internet. Webhooks are checked against Meta's signature before they are processed. No system is perfectly secure, and we will tell affected account owners if we find a breach that affects them.

Children

DMfetch is not for people under 13. We do not knowingly collect their data.

Changes

If we change this policy we will update the date above. If a change is significant we will tell account owners.

隱私政策

生效日期:2026 年 11 月 17 日

DMfetch 是一項工具,會代已連接的 Instagram 專業帳戶回覆貼文留言,並傳送私訊。營運者為 Ozaru Limited,一家在香港註冊的公司(Room 401, 4/F, Silvercord Tower 1, 30 Canton Road, Tsim Sha Tsui, Kowloon, Hong Kong;「我們」)。聯絡方式:[email protected]。

責任劃分。對於在已連接帳戶留言或傳送訊息的人(「觀眾」)的資料,由帳戶擁有人決定資料的用途和方式,因此帳戶擁有人是這些資料的控制者;Ozaru Limited 按擁有人所寫的設定,代擁有人處理這些資料。對於建立 DMfetch 帳戶的人(「帳戶持有人」)的資料,Ozaru Limited 是控制者。

DMfetch 的功能

有人在已連接帳戶的貼文留言關鍵字時,DMfetch 可以公開回覆,並向該人傳送私訊,例如一個懶人包連結。傳送前可以先檢查對方是否已追蹤該帳戶。貼文、關鍵字和訊息內容,全部由帳戶擁有人決定。

適用對象

  • 帳戶持有人:以 Google 或電子郵件和密碼建立 DMfetch 帳戶,用來連接和管理 Instagram 專業帳戶的人。
  • 帳戶擁有人:將 Instagram 專業帳戶連接到 DMfetch 的人。
  • 觀眾:在已連接帳戶的貼文留言,或傳送訊息給該帳戶的人。

我們接收和儲存的資料

來自帳戶擁有人(透過 Instagram/Facebook 登入)

  • Instagram 帳戶 ID、使用者名稱,以及連接來源的 Business 組合 ID。
  • 一個讓 DMfetch 可以代表帳戶操作的存取權杖。權杖存放在我們的資料庫,只用於向 Meta API 處理該帳戶的請求。
  • 擁有人自行撰寫的設定(關鍵字、貼文 ID、回覆和訊息文字)。
  • 如果擁有人也連接了 Facebook 專頁或 Threads 帳戶:這些帳戶的 ID、名稱或使用者名稱,以及存取權杖,用途相同。Threads 沒有私訊功能,因此在 Threads 上,DMfetch 只會公開回覆。

來自建立 DMfetch 帳戶的人

  • 你的電子郵件地址,以及你提供的姓名(可選)。
  • 你的密碼的單向雜湊值(如果你設定了密碼)。我們不會儲存密碼本身。
  • 如果你以 Google 登入:Google 提供的你的 Google 帳戶 ID、姓名和電子郵件地址。
  • 你的登入工作階段(連同瀏覽器的 user agent)、登入嘗試紀錄(用來限制重複猜測),以及你建立的 API 權杖的雜湊值。
  • 我們只會用這些資料讓你登入、寄出帳戶電子郵件(電子郵件驗證和重設密碼),以及顯示哪些帳戶屬於你。

來自觀眾(透過 Meta 的 webhook 和 API)

  • Instagram 範圍使用者 ID 和使用者名稱、留言或訊息 ID,以及留言或訊息文字(我們需要這些資料來比對關鍵字和回覆)。
  • 觀眾是否已追蹤帳戶(僅限啟用追蹤檢查時)。
  • 電子郵件地址:只有在帳戶擁有人開啟了「收集電子郵件」步驟,且觀眾回覆輸入電子郵件時才會取得。電子郵件會存放在觀眾的聯絡人紀錄中,顯示在擁有人的聯絡人清單,擁有人也可以匯出。DMfetch 本身不會寄信到這個電子郵件地址。
  • 觀眾在流程中的進度(例如「已傳送確認訊息」、「已傳送懶人包」)、開啟過哪個追蹤連結及開啟時間,以及觀眾要求停止時的退出標記。

技術紀錄

  • 一份事件紀錄,記錄 DMfetch 執行了哪些操作及原因(類型、ID、時間、錯誤原因)。比對到的留言會記錄留言者的使用者名稱和留言的前 200 個字。用途是讓擁有人看到發生了什麼,以及修正故障。
  • 每則來自 Meta 的 webhook 訊息的暫存副本(原始訊息,包括使用者名稱和留言或訊息文字),以便處理失敗時重試。
  • 帳戶持有人的登入工作階段(使用者 ID、工作空間 ID、到期時間、瀏覽器 user agent),以及用來識別該工作階段的瀏覽器 cookie。

我們看不到你的 Instagram 或 Facebook 密碼:你是在 Meta 自己的頁面登入。如果你以密碼建立 DMfetch 帳戶,我們只儲存密碼的單向雜湊值。我們不會出售資料、顯示廣告或建立廣告用途的使用者檔案。

我們如何使用資料

  • 建立和保護 DMfetch 帳戶和工作空間。
  • 執行帳戶擁有人設定的回覆和訊息流程。
  • 讓擁有人看到發生了什麼,包括失敗原因。
  • 維持服務安全和正常運作。

我們不會將資料用於其他用途。

我們與誰分享資料

  • Meta Platforms(Instagram、Facebook、Threads):我們透過 Meta 的 API 傳送回覆和訊息。Meta 的服務受 Meta 自身的隱私政策規管。
  • Google(如果你選擇以 Google 登入):Google 會告訴我們你是誰。Google 的服務受 Google 自身的隱私政策規管。
  • 電子郵件發送服務:代我們寄出帳戶電子郵件(電子郵件驗證和重設密碼)。
  • 主機服務:應用程式和資料庫在雲端主機服務商的伺服器上運行。流量經 Cloudflare 到達伺服器,Cloudflare 代我們處理。這些服務提供者不得將資料作自身用途。
  • 法律要求時,我們會披露資料。

保留期

  • 原始 webhook 副本:處理後 14 日刪除。Webhook 防重複紀錄:14 日。
  • 事件紀錄(包括留言節錄):180 日。
  • 追蹤連結紀錄(哪個連結被開啟過、何時開啟):365 日。
  • 登入工作階段:30 日後到期,到期後 14 日刪除。登入嘗試紀錄,以及已使用或已過期的電子郵件連結:記錄或到期後 14 日刪除。
  • DMfetch 帳戶(電子郵件、姓名、密碼雜湊值、Google ID):帳戶存在期間保留;帳戶持有人刪除工作空間或要求我們刪除時刪除。
  • 帳戶、權杖、設定、觀眾流程紀錄和聯絡人紀錄(包括觀眾提供過的電子郵件):在帳戶保持連接期間保留;擁有人解除連接並要求刪除時刪除(見「資料刪除」頁面)。
  • 退出標記:保留至你要求刪除為止。保留標記是為了確保不會再傳送訊息給你;如果你要求刪除,之後再留言可能會再次收到訊息。

你的選擇和權利

  • 帳戶擁有人可以隨時在 Instagram(設定 → 網站權限 → 應用程式和網站)解除連接 DMfetch,之後應用程式會立即失去存取權。如要刪除帳戶已儲存的資料,請依照「資料刪除」頁面的步驟寄電子郵件給我們。
  • 帳戶持有人可以隨時自行刪除整個工作空間:設定 → 刪除我的工作空間。這會刪除工作空間內已連接的帳戶、自動回覆、聯絡人、活動紀錄和連接,以及你的 DMfetch 登入。
  • 觀眾可以向帳戶傳送以「stop」、「取消」或「unsubscribe」開頭的訊息以停止接收訊息,或要求控制資料的帳戶擁有人或我們刪除我們持有的你的資料。
  • 如要查閱、更正或刪除資料,請依照 https://dmfetch.com/data-deletion 的步驟,或寄電子郵件至 [email protected]。我們會在 30 日內回覆。

安全

權杖和資料存放在不對外公開的私人資料庫。Webhook 處理前會先核對 Meta 的簽署。沒有系統是絕對安全的;如果發現影響帳戶擁有人的資料外洩,我們會通知受影響的擁有人。

兒童

DMfetch 不適用於 13 歲以下人士。我們不會在知情的情況下收集他們的資料。

更改

我們更改本政策時會更新上方的日期。如果更改重大,會通知帳戶擁有人。