Privacy Policy
Last updated: October 13, 2026
This policy explains what we collect when you use aigopilot.com and the AigoPilot apps (the studio for Windows, AigoPilot Agent for Mac and Windows, and the iPhone app), why we collect it, and what you can ask us to do with it. "AigoPilot", "we" and "us" mean Doment Digital FZE LLC, the company that runs aigopilot.com. You can reach us at info@aigopilot.com.
Who is responsible for your data
Doment Digital FZE LLC is the company responsible for the personal data described in this policy. Our registered address is Business Centre, Sharjah Publishing City Free Zone, Sharjah, United Arab Emirates, and our contact email is info@aigopilot.com.
What we collect
When you sign in. You sign in with Google, GitHub or Apple, and the one you choose shares a few details with us. Google shares your name, email address, profile picture and a Google account ID. GitHub shares your name or user name, your primary verified email address, your profile picture and a GitHub account ID. Apple shares an Apple account identifier, an email address (Apple's private relay address if you chose to hide yours) and, the first time, your name. We use them to create your account, show who is signed in and send you email about your account. We do not ask for anything else: we cannot see your password, contacts, files or mail, and we do not ask GitHub for access to your repositories.
When you buy a plan. Payments are handled by Stripe. You type your card details on Stripe's page, not ours, and we never see or store your full card number. Stripe tells us your customer ID, which plan you chose, whether the subscription is active and when it renews. On your billing page we show the card brand, its last four digits and its expiry date, which we fetch from Stripe when you open the page. Stripe keeps your billing address and invoices.
When a plan was bought through Paddle. Plans bought earlier from the European Union, the United Kingdom or Liechtenstein were paid through Paddle, and Paddle still handles their renewals and refunds. New plans are sold through Stripe only. These payments are handled by Paddle, which sells in its own name as our reseller. You type your card details on Paddle's checkout, not ours, and we never see or store your full card number. Before the checkout opens we give Paddle your email address and your name, so that the purchase is tied to your account. Paddle tells us your customer ID, which plan you bought, whether the subscription is active and when it renews, and what was paid. On your billing page we show the card brand, its last four digits and its expiry date, which we fetch from Paddle when you open the page. Paddle keeps your billing address and invoices under its own privacy policy, at paddle.com/legal/privacy.
When you take part in the referral program. We keep your referral code, which purchases were made with it, the commission each one earned, the payouts we made to you and the payout details you give us (a PayPal address or bank details). If you buy with someone's code, we record that the purchase came through them. They see the date, the plan and the amount paid, but never your name or email address.
When you use the website. Our server keeps ordinary technical logs: IP address, browser type, the page requested and the time. With your sign-in session we store your IP address and browser description so we can spot misuse of an account.
When you write to us. We keep your messages so we can answer them and look back at earlier conversations.
When a website uses the Chat Agent plugin. Chat Agent is a plugin that puts a chat on a member's own website. The chat runs on our server (chat.aigopilot.com). For each chat we store the name and the email address the visitor typed, the messages of the conversation, the address of the page it started on, the visitor's IP address and the language the visitor wrote in. We hold this for the member whose site it is. That member decides what their visitors are told and is responsible for telling them. We use it only to run that site's chat: to answer, to hand the conversation to the member, and to email the member's reply to a visitor who has left. The messages are sent to OpenAI to write the answers and the translations, on our key or on the member's own key. The member reads and answers the conversations in the AigoPilot studio and in the iPhone app. A notice that a visitor is waiting goes to the member's iPhone through Apple's push service: it carries the site's name and one short reason, and never the visitor's name, email address or message. While the site's subscription runs we keep its conversations. When the subscription ends we keep them for 30 days, so that subscribing again brings them back, and then we delete them.
The apps on your computers and phone
This section covers the AigoPilot studio for Windows, AigoPilot Agent for Mac and Windows, and the AigoPilot iPhone app. The Mac app also has a short page of its own: Privacy Policy for AigoPilot Agent for Mac.
Your work stays with you. AigoPilot keeps your projects, coding sessions, email, leads and sales data on your own computers. The apps do not send that work to us.
Your coding tools. Coding sessions run through Claude Code, Codex or Grok, installed on your computer and signed in with your own account. Those tools talk to their own providers, and what the providers receive and keep is governed by their terms and privacy policies. AigoPilot never reads, stores or reuses the sign-in tokens or cookies of those tools. The same holds for other services you connect yourself, such as an email account, Stripe or an advertising platform: the app talks to them directly with your own accounts. We are independent of Anthropic, OpenAI and xAI.
Between your own devices. You pair a second computer or a phone with your studio yourself, with six digits shown on one device and typed or scanned on the other. After that, everything that travels between them (code, prompts, transcripts, files of a project you move) is encrypted end to end with keys that were made on your devices and stay there. We do not hold those keys.
What reaches our servers from the apps.
- Update checks. AigoPilot Agent downloads a small public list of the newest builds from aigopilot.com about once a day, and a newer build when there is one. The request carries no account and no device identifier. Our server and Cloudflare see the IP address it came from, as with any web request.
- Announcements. When the studio starts, it reads a public file on aigopilot.com to see whether we have news to show. The request carries nothing about you.
- The relay. When two of your devices are not on the same network, they can meet at our relay (relay.aigopilot.com). The relay passes bytes that are already encrypted between your devices, so it cannot read them. It sees the IP addresses of the two ends and a room name derived from a device key, and it keeps no account, no file and no record of who connected to whom.
- Notices on your iPhone. If you pair an iPhone, the studio sends notices to it through aigopilot.com and Apple's push service. The text of a notice is sealed with a key that only your phone and your studio hold, so neither we nor Apple can read it. With it travel the address Apple gave your phone for notices and a few plain fields the phone needs to present it: which sound to play, the name you gave your studio, and fallback words the phone chose itself. We pass these to Apple and do not keep them.
- Marketplace plugins. A plugin works only after you link the studio to your aigopilot.com account, by confirming a short code on this site. We then keep the name of that studio and a one-way hash of the token it was given. SearchPlan sends the search phrases to be measured to our server, which asks Google and Bing for the figures and counts the run against your credits. Social Studio places a picture on our server for up to thirty minutes so that Instagram can fetch it. The writing in both plugins is done by your own coding tool on your own computer.
No analytics in the apps. The studio and the agent contain no analytics, advertising or tracking software and send us no usage statistics or crash reports. The iPhone app sends its data only to your own studio.
Cookies
We use two cookies, both needed for sign-in: one that keeps you signed in for up to 30 days, and one that lasts ten minutes while sign-in with Google, GitHub or Apple completes. If you arrive through a referral link, a third cookie remembers that referral code for up to 60 days, so the discount can be applied when you buy. We also use Google Analytics, which sets its own cookies to tell us how many people visit, which pages they read and roughly where they come from. It does not tell us who you are, and we use it for nothing else. You can block it with Google's opt-out add-on (tools.google.com/dlpage/gaoptout) or your browser's settings. There are no advertising cookies on aigopilot.com.
We send email that belongs to your account: a welcome message when you sign up, a confirmation when you buy, your download link, receipts and notices about your subscription. We send it through Google Workspace from info@aigopilot.com. If we ever send news or offers, each one will have an unsubscribe link.
Who else handles your data
- Google, for sign-in, for sending our email, and for counting visits to this website (Google Analytics).
- GitHub and Apple, for sign-in when you choose them. Apple's push service also delivers the sealed notices to a paired iPhone.
- Stripe, for payments, invoices and the page where you manage your subscription.
- Paddle, the reseller and merchant of record for the plans bought earlier through Paddle: for those payments, their invoices and the page where you manage that subscription.
- OpenAI, whose models write the answers and the translations of the support chat on this website and of the Chat Agent plugin.
- Our hosting provider, whose servers run aigopilot.com and the relay and store our database.
- Cloudflare, which sits in front of our website to protect it and make it faster.
Each of them handles data for us under its own terms and only for these purposes. We do not sell or rent your personal data to anyone. We would share it with an authority only when the law requires us to.
Google user data
AigoPilot's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use the name, email address and picture from Google only to run your account, and never for advertising.
How long we keep it
We keep your account for as long as you have one. If you ask us to delete it, we delete your profile and sign-in data within 30 days. Payment records and invoices are kept for as long as tax and accounting law requires, which can be several years. Server logs are kept for a short time to keep the site running safely, then deleted.
Your choices and rights
You can ask us for a copy of the personal data we hold about you, ask us to correct it, ask us to delete your account, or object to how we use it. Write to info@aigopilot.com from the email address on your account and we will reply within 30 days. You can also remove AigoPilot's access to your Google, GitHub or Apple account at any time from that account's settings. Depending on where you live, you may have the right to complain to your local data protection authority.
Security
Connections to aigopilot.com are encrypted. Sign-in sessions are stored as one-way hashes, card details never reach our servers, and access to our systems is limited to the people who need it. No system is perfectly secure, and if something goes wrong that affects your data, we will tell you.
Children
AigoPilot is a tool for people building and running software products. It is not meant for anyone under 16, and we do not knowingly collect data from children.
Changes to this policy
If we change this policy, we will update the date at the top. If a change affects how we use data you have already given us, we will email you before it takes effect.
Contact
Questions about privacy: info@aigopilot.com.