PilotControl.
Sign in

Privacy Policy

Last updated: October 23, 2026

1. Who we are and what this policy covers

PilotControl is a service to schedule and publish content on a brand's social media accounts, view its statistics and reply to its comments. This policy covers the control.pilot0.app portal, the Cloud web app (app.pilot0.app), the desktop app and PilotControl's integration with AI assistants such as ChatGPT. For any question about your data, write to [email protected].

2. Data we collect

  • Account: your email address (to sign in), your subscription status, your customer ID at the payment processor and the devices you linked.
  • Connected networks: the name and ID of each social media account you connect, and the authorization needed to publish and read on it. We do not store your social media passwords.
  • Cloud content: brands, the images and videos you upload or that an assistant sends at your request, titles, captions, destinations and schedule dates, the status and link of each post, and the statistics of those posts (views, likes, comments, reach).
  • Comments and messages: the comments and messages received by the connected accounts, including the author's username and text, and the replies you send or approve.
  • AI assistant integration: the permissions you grant (brand, type of access and dates) and a technical log of each request (which tool was used, the result and the time). We only receive what the assistant sends in each request, such as images, captions or the chosen network; we never receive or ask for your conversation history.
  • Service keys you add (for example, for Google Gemini): stored encrypted, never shown in full and never sent to an assistant.
  • When informational detection of possible multiple accounts is enabled, we correlate authenticated sign-ins using a network fingerprint protected by a private key, without storing the IP address in this record. Only the service owner sees matches; a shared network is not proof of abuse and never triggers automatic blocking. Signals cover the last 30 days; periodic cleanup removes expired records, with a maximum of 100 fingerprints per account.
  • Desktop app diagnostics: when an error happens, the app sends a technical report of the failure so we can fix it. You can turn this off from the Diagnostics and support menu.

3. Website visit statistics

The public pages of control.pilot0.app and pilot0.app send first-party statistics to our servers, without third-party services. Your account screens are not measured. We record the page viewed, browser language, referring site and campaign parameters (utm), device type, country derived from the connection, time on page, scroll depth and clicks. To count distinct visitors we compute a code from your IP and browser combined with a value that changes daily; neither the IP nor the full browser data is stored.

We use a single first-party cookie, pc_origen, which stores for 90 days the site you first came from, its campaign parameters (utm), the landing page, the date and whether the screen is touch-enabled. It does not identify you and is not shared. If you create an account, we store with it that origin, the device type and the operating system (for example, Android, iPhone, Mac or Windows), derived from the browser, and the country derived from the connection; we do not store the IP or the full browser data. It helps us learn how people who sign up found us.

4. Desktop app local mode

If you use the desktop app without the Cloud, your files, drafts, history, comments, messages and brand settings stay on your computer and are not sent to our servers, except for the diagnostic reports described above. Publishing and reading social networks goes through the integration provider described in section 6.

5. How we use the data

  • To provide the service you ask for: publish and schedule content, show history, calendar and statistics, and reply to comments when you ask for it or configure it.
  • To sign you in, bill the subscription, provide technical support and send operational notices.
  • To protect the service: limit abuse, detect unauthorized access and fix errors.

We do not sell your data, use it for advertising or build behavioral profiles.

6. Who we share it with

  • The social networks you connect (for example Instagram, Facebook, TikTok, YouTube, LinkedIn or X), when you publish, schedule or reply.
  • Our social media integration provider, which sends posts and reads statistics and comments on our behalf.
  • Providers that host the service: servers, database and content delivery network.
  • Our email provider, to send sign-in links and notices.
  • Payment processors (Stripe and PayPal). Your card details are handled by the processor and never reach our servers.
  • The AI providers you choose: Google Gemini, with the key you add, to draft replies and captions; and the assistant you connect (for example OpenAI's ChatGPT), which receives the results of the tools you ask it to use. What that assistant does with your conversation is governed by its provider's privacy policy.
  • Authorities, only when the law requires it.

7. How long we keep it

  • Images and videos in the Cloud: up to 30 days after the post is finished (afterwards only a thumbnail remains). An uploaded file that is never used is deleted after 7 days.
  • Workspace activity log and desktop app diagnostics: 7 days.
  • AI assistant permissions: each access token lasts 1 hour; renewal expires after 30 days without use and the permission ends after 180 days or when you revoke it.
  • Visit statistics: 13 months.
  • Account, posts, statistics and comments: while your account exists. If you ask us to delete it, we delete your data within 30 days, except billing records the law requires us to keep. Google and YouTube data also follow the specific retention and withdrawal controls in section 12.

8. Your controls

  • Revoke an AI assistant's access at any time at app.pilot0.app/mcp/connections, or from the assistant's own settings.
  • Disconnect a social network, delete drafts and scheduled posts, and turn off automatic replies from the app.
  • Turn off automatic diagnostic reports in the desktop app.
  • Request a copy, correction or deletion of your data by writing to [email protected].

9. Security

Connections are encrypted (HTTPS). Each account and brand is isolated from the others. Assistant access uses OAuth with per-brand permissions that you approve, tokens are stored as hashes and service keys are stored encrypted. No system is invulnerable: if we detect an incident that affects your data, we will tell you.

10. Children

PilotControl is not directed to children under 13 and we do not knowingly collect their data.

11. Changes and contact

If we change this policy we will publish the new version on this page with its date. For questions, data requests or complaints write to [email protected].

12. Google and YouTube

Signing in with Google and connecting a YouTube channel are separate authorizations. When connecting YouTube, you choose the channel and grant access to manage its videos and comments and read its analytics. We receive the channel ID and name, video metadata and status, comments and replies, and activity, audience and retention analytics. We do not request your passwords or access to your YouTube revenue.

We use this data for the features you request: publishing and scheduling, displaying history and results, and replying to comments. If you enable an AI feature or connect an assistant, the necessary text is shared with the provider you choose for that feature; that provider's data processing terms also apply. PilotControl does not sell Google or YouTube data, use it for advertising, or train its own general-purpose models with it.

In the Cloud, direct connection authorizations are encrypted on the server and isolated by account, Workspace and brand. In desktop local mode, your own authorizations remain in your installation. Data is transmitted to Google or YouTube to perform authorized operations; YouTube credentials are not sent to assistants.

You can withdraw access in PilotControl Connections or in your Google account permissions. Withdrawing Google's permission may affect other connections authorized with the same Google account for this project; those connections may need reconnecting. For a direct Cloud connection, disconnecting in PilotControl disables the authorization and requests revocation from Google. If Google does not confirm it, the app reports the pending state and temporarily keeps the encrypted credential only to complete that request.

For the direct Cloud connection, after access is withdrawn we remove the channel's API data copies as soon as possible and within seven days. We periodically check authorizations and stop using those Google withdraws or expires; affected copies are removed within thirty days. API metadata is refreshed or deleted at least every thirty days; authorized analytics are retained only under current permissions. Your own text, drafts, files and records of posts you created are distinguished from those API copies; to request their deletion too, write to [email protected].

The integration is also subject to YouTube's Terms of Service and Google's Privacy Policy. Processing and transfers of data received through Google APIs are subject to the Google API Services User Data Policy, including Limited Use requirements.