D.O Command
PTENES

D.O COMMAND · PRODUCT

Privacy notice

Last updated: October 23, 2026

1. Scope

This notice covers the public docommand.app website and the D.O Command product. It is specific to the software product and is separate from privacy terms for another business's document or consular services.

When a business subscribes, D.O Command processes the account and subscription details needed to create and manage access (name, email, plan, billing status). Payments are processed by Stripe: customers enter their payment details directly with Stripe, and D.O Command does not receive or store full card numbers. The interest form collects name, email, language, consent to be contacted and, if provided, a message to record interest and allow a response. These details are stored in the product database and available to authorized operators. The hosting provider may also process technical request data to deliver and protect the service. Do not submit sensitive information through this form.

2. Information processed in the product

When a business receives access to D.O Command, the product may process information needed to operate its workspace, depending on the features enabled and used:

  • account and team details such as name, email, role and workspace membership;
  • business, service, team and workspace configuration details;
  • client and contact records and service context entered or imported by the customer;
  • messages, tasks, calendar events and finance records the team adds to the product;
  • files and data submitted for import;
  • connection details and tokens needed for providers the customer chooses to connect; and
  • onboarding answers used to propose a compatible setup.

3. How information is used

Information is used to authenticate members, operate and configure the workspace, show records entered by the team, process requested imports and run enabled features. Onboarding answers may be interpreted by AI-assisted features to propose a structured plan. AI proposes; the customer reviews and confirms before configuration. The product does not promise to create arbitrary software.

Do not submit sensitive personal information that is not needed for the business's work. The customer's team decides what information to enter and who within the workspace should access it.

4. Workspaces and connections

Each business operates in a workspace. Server-side operations involving workspace data check member participation and apply workspace access boundaries. This describes product controls; it is not a compliance certification or a promise of zero risk.

If a customer connects an external provider, information needed for that connection may be sent to or received from that provider. Availability and approvals vary. Use is also subject to the selected provider's terms and privacy notice.

5. Data from Meta products (Facebook, Messenger, Instagram, WhatsApp)

D.O Command lets a business connect its own Facebook Page, Instagram professional account, Meta ad account and (when available) WhatsApp Business Account to its D.O Command workspace, so the business's team can answer its customers and review its own ad results in one place. A connection is made only when an owner or admin of the workspace signs in with Facebook Login for Business, Instagram Business Login or WhatsApp Embedded Signup and approves the requested permissions. Each connection belongs to one workspace and is never visible to other workspaces.

What we receive and why

  • Basic profile of the person who connects: Meta user ID and name, used only to identify which person authorized the connection and to process deauthorization and deletion requests. We do not request or store the person's Facebook email address, friends, photos or personal posts.
  • Facebook Pages (pages_show_list, business_management): the list of Pages the person shared with D.O Command, including Pages managed through a Business Portfolio (ID, name and the person's tasks on the Page), so the business can choose which Page to connect. We keep the Pages Meta returns for that authorization, including Pages Meta lists as explicitly granted. A Page already connected to another workspace is not stored again.
  • Page content and messages (pages_read_engagement, pages_manage_metadata, pages_messaging): Page name and settings, subscription of D.O Command to the Page's webhooks, recent Page posts and comments when the Page connection can read them, and the Messenger conversations between the Page and people who message it (message text, attachments, sender name and Page-scoped ID, timestamps). Used to show those conversations in the business's inbox, to let the business review those posts and comments, and to send the replies its team writes. We do not send unsolicited or bulk messages.
  • Instagram professional account (instagram_business_basic, instagram_business_manage_messages): account ID and username, and the Direct Message conversations between the account and people who message it (message text, attachments, sender username and Instagram-scoped ID, timestamps). Used to show and answer those messages in the business's inbox. This Instagram Login request does not include permission to publish content or to manage comments.
  • Ad accounts (ads_read): the ad accounts the person can access (ID, name, status, currency, time zone, owning business) and read-only campaign, ad set, ad and performance metrics (for example spend, impressions, reach, clicks). Used only to show the business its own ad results. D.O Command does not request permission to create, edit or pause campaigns.
  • WhatsApp Business (whatsapp_business_management, whatsapp_business_messaging, when enabled): the WhatsApp Business Account, phone number and message template information the business authorizes during Embedded Signup, and the WhatsApp messages exchanged between the business's number and its customers (text, media, phone number, profile name, timestamps, delivery status). Used to run the business's WhatsApp inbox. Messages outside the 24-hour customer-service window are sent only with templates approved by Meta.
  • Access tokens issued by Meta for the connection, used only to make the API calls above.

How we use it, and what we never do

Data from Meta products ("Platform Data") is used only to provide the features the business turned on: its unified inbox, replies written by its team, optional AI help the team asks for (for example a summary of a WhatsApp conversation, suggested next steps, or an audio transcription), and its own ad reporting. We do not sell, rent or license Platform Data. We do not use it for advertising, profiling or data brokering. We do not combine one business's Platform Data with another's. We do not use Platform Data to train AI models. We follow the Meta Platform Terms and Developer Policies.

Storage and security

Platform Data is stored in the D.O Command production database hosted in the United States. Access tokens are encrypted at rest, scoped to one workspace, and never shown in the interface or written to logs. Traffic uses HTTPS. Webhook calls from Meta are accepted only with a valid Meta signature. Inside D.O Command, only members of the business's own workspace can see its connected data, according to the roles the business assigns.

Service providers

Platform Data is processed on our behalf only by: Railway Corp. (application hosting and database); OpenAI, L.L.C. (only when a team member uses an AI feature on a conversation, for example a summary, suggested next steps, or a WhatsApp audio transcription; the content needed for that request is sent); and Cloudflare, Inc. (network proxy and protection in front of the app). Our login-email provider does not receive Platform Data. Each provider processes data only to perform its service. We disclose Platform Data to public authorities only when a valid legal order requires it.

Retention

  • Access tokens are deleted as soon as the business disconnects the account in D.O Command, removes D.O Command in its Facebook or Instagram settings, or asks us to delete its data. Closing a workspace also deletes stored provider credentials immediately.
  • Conversation history and ad metrics are kept while the workspace is active, so the business keeps its own customer history. Closing a workspace does not by itself erase that history, and the Meta deletion callback does not erase it either. When the business asks us to delete that history, we delete it within 30 days, unless the law requires us to keep it longer.

Disconnecting and deleting your Meta data

  • In D.O Command: Integrations → Meta (or Instagram / WhatsApp) → Disconnect. This removes the stored tokens. For Facebook, D.O Command also asks Meta to revoke the authorization when that Facebook user is not still connected to another workspace. If Meta does not confirm the revocation, the stored tokens are still deleted.
  • On Facebook: Settings & privacy → Settings → Apps and websites (or Business Integrations) → D.O Command → Remove. On Instagram: Settings → Website permissions → Apps and websites → D.O Command → Remove.
  • When you remove the app and ask Meta to delete your data, Meta sends us a signed deletion request at https://app.docommand.app/api/data-deletion (Facebook Login) or https://app.docommand.app/api/instagram/data-deletion (Instagram Login). We verify Meta's signature, delete the stored tokens and the Meta identity of that connection (ID, name, username), release the connected Pages and ad accounts, and give you a confirmation code. You can check its status at https://app.docommand.app/data-deletion?code=<your code>. This callback does not erase the workspace's conversation history.
  • You can also email [email protected] from the address linked to your account, with the workspace name. We answer within 30 days. See also Data deletion requests.
  • If you messaged a business that uses D.O Command (on Messenger, Instagram or WhatsApp), that business controls your conversation. Ask that business to delete it, or contact us and we will forward your request.

6. Hosting, service providers and legal requests

The product relies on technical infrastructure for hosting, authentication, operational email delivery and features enabled by the customer. Those providers process data as needed for their functions and applicable agreements. Information may also be disclosed when a valid legal obligation requires it.

D.O Command does not publish one fixed provider list for every product feature; providers may vary with workspace configuration and service environment. Providers that process data from Meta products are named in the previous section.

With your optional consent, we use Google Analytics 4 to measure visits to public site pages and public entry routes of the app. The tool loads only after you allow analytics. Private workspace screens are excluded from tracking; URL query parameters and customer data are not intentionally sent to Analytics. You can decline or change this choice using "Privacy choices". Google processes measurement data under its own privacy policies.

7. Retention and data requests

Workspace information is kept as needed to provide the service, follow applicable instructions and agreements, and meet legal or security obligations. Workspace export or removal follows available product features and the terms agreed with the customer.

Users of existing workspaces should direct requests to the workspace owner or the support channel provided during onboarding or in the direct customer agreement. You may also contact [email protected]. This public site does not accept requests through a form.

8. Updates and contact

This notice may be updated as the website or product changes. Relevant changes will be communicated to workspace customers through an appropriate channel. The version published here describes product practices; specific agreements may supplement this notice.

D.O Command is a product of D.O Global Services, operated by Patrick Gomes DeOliveira · Fall River, MA, USA · [email protected]. This entity is responsible for the processing described in this notice.

← Back to product