Versioned document. This page is the complete 2026-08-23 version. Skyflo will not change its body in place. A later revision will be published at a new dated URL, and skyflo.ai/legal/privacy will then serve that newer version. The permanent link to this exact version is skyflo.ai/legal/privacy/2026-08-23.
1. Who we are and what this covers
Skyflo is operated by Operantix Systems Private Limited (CIN U62010PN2026PTC252795), a company registered in Pune, Maharashtra, India (“Skyflo”, “we”, or “us”). We are the controller of the personal data described here.
This policy covers three surfaces, and they behave differently, so the difference is stated throughout rather than averaged into one paragraph:
- skyflo.ai, the public website. No sign-in. Analytics run here.
- app.skyflo.ai, the account console. Sign-in required. No analytics run here.
- Skyflo Desktop, the macOS application where agents actually run.
Your use of the Services is also governed by the Terms and Desktop Licence.
2. In short
- Agents run on your linked Mac, not on Skyflo servers. Missions, repository content, code, and files stay on that machine, and Skyflo does not receive or store them.
- The account console holds account records only: who you are, which organisation you belong to, which devices you have linked, which plan you are on, and which documents you accepted.
- Signing in with Google gives us your basic Google profile and email address, and nothing else. We do not request access to Gmail, Drive, Calendar, Contacts, or any other Google service.
- We do not sell personal data, we do not use it for advertising, and we do not use Google user data to train AI models.
- Sending any part of a mission to a model Skyflo runs is off by default and requires you to switch it on after reading a published disclosure.
3. What we collect
3.1 The website, skyflo.ai
- Analytics. We use Google Analytics 4 on this host. It sets cookies and collects a device identifier, your IP address, the pages you view, the referring page, your approximate location derived from IP, and browser and operating-system details. Google Analytics does not run on the account console.
- Email you give us. If you request access to the private beta or join a waiting list, we store the email address you type, the page the request came from, and, on the high-intent form only, the use case and cloud provider you select. These rows are stored in our Supabase database.
- Demo bookings. The demo page embeds Calendly. Whatever you enter into that scheduler, typically your name, email address, and any notes, is collected by Calendly and shared with us so we can hold the meeting.
- Server and delivery logs. Our hosting provider records request metadata such as IP address, user agent, requested path, and timestamp for operational and security purposes.
3.2 The account console, app.skyflo.ai
Signing in is handled by Clerk, our authentication provider. You may sign in with Google, with GitHub, or with a one-time code sent to your email address. Skyflo does not offer password sign-in and therefore never holds a password for you.
Depending on the method you choose, Clerk receives and holds your account identifier at that provider, your name, your email address and whether the provider reports it as verified, and your profile picture URL. Section 4 covers Google specifically.
In our own account records we store:
- your Skyflo user identifier and email address;
- your organisation identifier, its name, and your role in it;
- one record per linked Mac: an identifier, the device name it reports, the platform, when it was linked, when it was revoked if it has been, and whether the device reported that its signing key is held in hardware;
- your plan and entitlement snapshot;
- your acceptance of each published policy document, recorded as the document version, its SHA-256 digest, and the time you accepted it;
- your managed-content choice and the setting derived from it.
3.3 Payments
Paid subscriptions are sold through Dodo Payments as merchant of record. Card numbers and other payment credentials are entered on Dodo’s hosted checkout and are never sent to or stored by Skyflo. We receive the subscription state we need to run your account: plan, billing interval, status, and provider reference identifiers.
3.4 Skyflo Desktop
Skyflo Desktop runs on your Mac and does the work there. Missions, plans, prompts, repository content, code, files, terminal output, and agent results are held on that machine. Skyflo does not receive them and does not hold your code.
Two things do leave the machine, both because you asked for them:
- Model requests you configure. When Skyflo Desktop calls a model provider using your own API key, the content of that request goes from your Mac to that provider under that provider’s terms and privacy policy. Skyflo is not in the path and does not see it.
- Managed content, if you switch it on. Managed content is off by default. It can only be enabled after you read the published managed-content disclosure and record an affirmative acceptance in the console. While it is on, mission titles may be generated by a model Skyflo operates, which means the title prompt reaches our infrastructure. Nothing else about a mission is sent under this setting. Switching it off takes effect on the next title; anything already sent has already been sent.
4. Google user data
This section describes exactly what Skyflo does with data received from Google when you choose Sign in with Google. Google Sign-In is optional; GitHub and a one-time email code are the alternatives, and the account works identically either way.
4.1 What we access
Skyflo requests only the basic OpenID Connect scopes: openid, email, and profile. Through them we receive your Google account identifier, your email address and whether Google reports it as verified, your name, and your profile picture URL.
We do not request, and therefore cannot access, any Google API scope beyond those. Skyflo does not read, write, or store your Gmail messages, Google Drive files, Google Calendar events, Google Contacts, Google Photos, or any other Google service data.
4.2 How we use it
Google user data is used only to create and authenticate your Skyflo account, to identify you inside the account console, to address service and transactional email to you, to attribute your organisation membership and device approvals, and to detect and prevent abuse of the sign-in flow. It is not used for advertising, for profiling, or for building a marketing audience.
Skyflo does not use Google user data to develop, improve, or train generalised AI or machine-learning models.
4.3 How we store it
Your Google identity record is held by Clerk, our authentication processor, in its systems. Our own account database stores your Skyflo user identifier and your email address, and links them to your organisation, devices, plan, and acceptances. We hold this for as long as your account exists, and then as described in section 9.
4.4 How we share it
We do not sell Google user data, and we do not transfer it to third parties for advertising or for any purpose unrelated to running Skyflo. It is disclosed only to the processors listed in section 8 that are necessary to operate the account, and only where the law requires disclosure or where you have directed us to share it.
Skyflo’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
4.5 How to withdraw it
You can disconnect Skyflo from your Google Account at any time at myaccount.google.com/permissions. Doing so stops future Google sign-ins; it does not by itself delete your Skyflo account. To have the account and its data deleted, write to contact (at) skyflo.ai as described in section 12.
4.6 A separate matter: Google Analytics
Google Analytics on the skyflo.ai website is unrelated to Google Sign-In. It measures website traffic, it runs only on the marketing host, and it involves no access to your Google Account. See sections 3.1 and 7.
5. Why we process it, and on what basis
| Purpose | Data used | Lawful basis (UK and EU GDPR) |
|---|---|---|
| Create and authenticate your account | Identity data from Clerk, including Google or GitHub profile and email | Performance of a contract |
| Run the account console: organisations, linked devices, plans | Account records in section 3.2 | Performance of a contract |
| Take payment and manage subscriptions | Subscription state from Dodo Payments | Performance of a contract |
| Evidence that you accepted a published document | Acceptance records: version, digest, timestamp | Legal obligation and legitimate interests |
| Keep the service secure and prevent abuse | Logs, device records, sign-in challenges | Legitimate interests |
| Answer support requests and hold demos | Email address and what you write to us | Legitimate interests and consent |
| Measure website traffic | Analytics data in section 3.1 | Consent, where consent is required |
| Tell you when the private beta opens | Email address you submitted | Consent |
| Generate mission titles with a model we run | Mission title prompt, only when you enable managed content | Consent |
Where we rely on consent you can withdraw it at any time, and withdrawing it does not affect processing that already happened.
6. Where your work lives
This is the part of Skyflo that is most often assumed rather than read, so it is stated plainly.
Agents run on your linked Mac. The mission record, the repositories they touch, the files they read and write, and the output they produce are held on that machine. Skyflo does not hold your code. The account console manages your account, not your work.
The boundary has two honest exceptions, both described in section 3.4: model requests that you configure travel from your Mac directly to the provider whose key you supplied, and mission titles travel to Skyflo only while you have managed content switched on.
9. How long we keep it
- Account records are kept while your account is open. When an account is deleted we remove or anonymise them within 30 days, except where a longer period is required by law.
- Acceptance records for published documents are kept for as long as the agreement can still be relied on or disputed, because their purpose is to evidence what you agreed to and when.
- Billing records are kept for the period required by tax and accounting law.
- Beta and waiting-list emails are kept until you ask us to remove them, or until the programme they relate to closes.
- Website analytics are kept no longer than Google Analytics’ maximum event-level retention window of 14 months.
- Operational logs are kept for a short rolling period for security and debugging.
10. Security
Both hosts are served over HTTPS with HSTS and a per-host Content-Security-Policy, so the marketing surface and the authenticated console are not treated as one trust boundary. The account API is called only from our servers using your verified session; the browser never holds an account-API credential. The console is excluded from search indexing.
Because password sign-in is not offered, there is no Skyflo password to leak. Where your Mac supports it, the key that identifies your device is generated in the Secure Enclave and cannot be extracted; the console shows you which of your devices reported a hardware-backed key, and you can revoke any device at any time.
No system is perfectly secure. If a breach affects your personal data we will notify you and the relevant authority where the law requires it.
11. International transfers
Skyflo is established in India, and the providers listed in section 8 operate in the United States, the European Union, and elsewhere. Personal data may therefore be transferred outside the country where you live. Where such a transfer is from the United Kingdom or the European Economic Area, we rely on the European Commission’s Standard Contractual Clauses or another lawful transfer mechanism, together with the safeguards our providers commit to in their own terms.
12. Your rights and choices
Subject to the law that applies to you, including the UK and EU GDPR, India’s Digital Personal Data Protection Act 2023, and the California Consumer Privacy Act, you may ask us to:
- confirm what personal data we hold about you and give you a copy;
- correct data that is wrong or incomplete;
- delete your account and the data attached to it;
- export your data in a portable form;
- restrict or object to a particular use, including any use we base on legitimate interests;
- withdraw a consent you previously gave, such as the managed-content choice or a waiting-list signup.
Write to contact (at) skyflo.ai from the email address on your account. We confirm your identity before acting on an access or deletion request, because an unverified deletion is somebody else’s account being destroyed. We answer within the period the applicable law sets, and within 30 days where no period is set.
If you are in the United Kingdom or the European Economic Area you may also complain to your local supervisory authority. If you are in India you may raise a grievance with us at the same address and then, if unresolved, with the Data Protection Board of India.
13. Children
Skyflo is not directed at children. You must be at least 18 years old, or the age of legal majority where you live, to use the Services. We do not knowingly collect personal data from children, and we will delete it if we learn we have.
14. Changes to this policy
We will not edit this published version in place. If we change this policy we will publish a new version at a new dated URL, and skyflo.ai/legal/privacy will serve that newer version from the moment it goes live. Where a change materially affects how we handle data you have already given us, we will give notice and, where the law requires it, ask for consent.
15. Contact
Privacy questions, rights requests, and complaints go to contact (at) skyflo.ai, or by post to Operantix Systems Private Limited, Pune, Maharashtra, India. Please include enough information for us to identify your account and respond.