Privacy Policy
Last updated: November 17, 2026
1. What this policy covers
This policy covers the CloudCrane website, the dashboard at /app, the connector your assistant signs in to, and the apps we serve, each at its own address (<name>.cloudcrane.ai).
Your assistant (Claude, ChatGPT or another) is not part of CloudCrane. What you tell it, and what our connector hands back to it, such as your apps' code, is handled under that assistant's own privacy policy.
2. Information we collect
What you put into your apps: nothing
What you save in an app stays on your phone, in the app's own storage there, except what an app sends to the sites it lists. It is never sent to us. An app may reach at most five websites, each named with why under View app details on its install screen, before you add it (a weather app asking a forecast service for your city, say); an update that adds a site names it, with why, and opens only when you tap Update; every app runs under rules that stop it reaching any other, and an app's address answers nothing but requests to open it. The one exception is an app that connects directly to other phones, for a game played together, say: View app details on its install screen says it can reach past the sites it lists. Backup and sync are not offered yet.
How you found us, and when you use us
When you first visit, we note the website that sent you (its name only, such as reddit.com, never the page you were on), any campaign tags in the link, and the page you landed on. If you make an account, that note is kept with it once and never changed; if you don't, it is gone in 30 days. Once you have an account, we keep which days you used CloudCrane, on the website or through your assistant: the date, nothing about what you did. We use both only to see how many people find and use CloudCrane and where they come from.
When an app breaks
When an app's own code fails on your phone, it tells us what went wrong, so its maker and their assistant can fix it. We keep only the kind of error, the line of the app's code, its version and day, and the words of the message that are in the app's own code or are a browser's usual error words; anything else in it, numbers included, is replaced before it's kept, so nothing you typed or saved is. We count how often each problem happens; we keep nothing about which phone, who, or from where. You can turn this off in the app, under About this app.
Locking an app
You can lock an app with Face ID, a fingerprint or your phone's screen lock, under About this app. It makes a passkey on your phone for that app alone, and your phone checks you each time: nothing about it is sent to us. It stops someone holding your phone from seeing the app, but what the app saves isn't encrypted by it.
Apps you share with people
Some apps let you share what you save with people you invite, each on their own phone; an app that can says so under View app details on its install screen. It stays on each phone, and changes pass between them through us, encrypted on the phone with a key we never hold, so we can't read them. We keep those encrypted changes so phones can catch up, and we can see that a shared list exists, which app it belongs to, how big its changes are and when they were made. The key travels in the invite link, so anyone with the link can see and change the list. We delete our copy 12 months after the list last changed; what's on each phone stays, but the list stops syncing and its invite link stops working.
Reminders
Some apps can remind you at a time; an app that can says so under View app details on its install screen, and asks before it sets one. What a reminder says stays on your phone. We keep only what's needed to wake your phone at the right time: the time, whether it repeats, your time zone, the local time of day, the address your browser gives for notifications, and a scrambled form of a random key your phone made for the app. At the time we send your phone an empty message through your browser's notification service (Google's, Apple's, Mozilla's or Microsoft's), and your phone shows the words it kept.
From the website
- Contact form: your name, email address, the subject you choose and your message.
- Job application: your name, email address, the role, any links you share, and the CV you upload.
From your account
- Account: your email address. If you sign in with Google, also the name and profile picture your Google account gives us; we never receive your Google password. If you sign in with a code by email, we keep only a scrambled (hashed) copy of the code. You may add a display name and a job title.
- Workspace: its name, its plan, who is in it and in which role, and the addresses invited to join.
- Your apps: each app's name, its address, and every version of its code, with the note saying what changed, who or which assistant made it, and the warnings our checks raised. Unless you keep an app to yourself or to the people you invite, anyone with its address can open it and read its code, so the code should hold nothing personal; our checks warn when it seems to.
- Who you share an app with: the email addresses you invite to it, who invited them, and whether each has signed in to open it. We email each address once, with the way in. Take someone off and we delete their address.
- Assistants you connect: the name each gives itself, the addresses it sends you back to, what you allowed it (read, or read and build) and when it was last used.
- A log of each call an assistant makes: which tool, what it asked for (the app's name, address, version and note; an app's code is logged only as its length), whether it worked, how many results it got and how long it took. Never the results.
- If a workspace pays for a plan: the Razorpay subscription, its plan, status and billing dates.
- From when CloudCrane had friends (it no longer does): the email addresses asked, who accepted or declined, and when. Nobody sees them now.
- Which of your apps are public. A new app is public unless it seems to hold personal details; you can make any app private. A public app's name, icon, blueprint, install link, version numbers, dates and notes saying what changed (unless a note seems to hold personal details) are shown to anyone on Explore, on this website and in the dashboard, with your handle and its picture, or your name and photo if you turn that on in Settings, never your email; never what you saved in it. Someone who remixes it is also given, for their assistant to build from, what its screens say (its buttons, headings and fields), the names it saves under, its colours and fonts, and its tests (unless a test seems to hold personal details); never its code.
- Your upvotes and saves on public apps.
- An icon picture you upload for an app (PNG or JPEG), kept until you change it or delete the app.
- Your handle, how the public knows you, and any picture you upload for it (PNG or JPEG), which anyone can see. Your handle has a page listing your public apps and how many upvotes, saves and remixes they have; never a private app. Without one, we draw a picture from your handle on our own servers.
- Remixes: when you remix a public app, a copy of its blueprint (what it does, never its code or what anyone saved), with its name and what its maker shows publicly, kept in your workspace. If you build it and your app is public, both apps' pages show that one was built from the other.
When you use either
- Server logs: the method and path of each request (never the query string or the body), its status, and the ids of the request, account and workspace it was for. Passwords, tokens and keys are removed before a line is written. We don't log IP addresses; asking for a sign-in code uses a scrambled copy of yours, in memory only, to limit how many are sent.
- Views of a public app's page, to count them on Explore: the app and the day, with the visitor as a scrambled (hashed) copy of the day, their IP address and browser. The address isn't kept, and the same person is a different visitor the next day. Crawlers aren't counted.
3. How we use it
- To answer your message or review your application.
- To run the service: signing you in, emailing you sign-in codes, invitations and a welcome, checking each app before it is published, serving your apps at their addresses, letting the assistants you approve publish and change them, and billing a plan you pay for.
- To keep the service secure and working, including rate limits and taking down apps that break our rules.
- To meet legal obligations.
We don't show ads, and we never use anything you give us to train a model. The only thing we send an AI model provider is what Explore's search needs to find apps by what they do: the words typed into it, and what public apps already say about themselves (section 4). Nothing about who searched goes with them.
4. Who we share it with
We do not sell, trade or rent personal information. We use these providers, and no others. Razorpay is in India; the others are outside it, so your data is transferred internationally and protected by the contractual terms we hold with each.
| Provider | What it does | What it sees |
|---|---|---|
| Replit | Hosting this website and the server, and the file storage | Everything the server handles; its file storage holds every version of your apps' code, and CVs sent with job applications |
| Neon | The database | Everything listed in section 2 that we keep, apart from the files above |
| Cloudflare | Serving each app at its own address | Each app's code, name and icon, and the requests a phone makes to open it, including its IP address |
| Sign-in with Google, and the fonts on this website and the dashboard | Your name, email and profile picture at sign-in; your IP address when a page loads its fonts | |
| Resend | Sending email | Your address and the message: sign-in codes, invitations, the welcome email, and contact messages and job applications (with the CV) sent on to us |
| Razorpay | Payments, if a workspace pays for a plan | Your email address and name, the workspace's id and plan; you give your payment details to Razorpay directly, and we never see them |
| OpenAI | Searching Explore by what an app does, only while we have it turned on | What public apps say about themselves (name, purpose, category, tags, journeys) and the words typed into Explore's search; never anything about who searched |
| Sentry | Error reports, only while we have it turned on | An error, its stack and the ids of the request, workspace or job it happened in; for an error in your browser, the page's path. Never a body, cookie or IP address |
While we have tracing turned on, a tracing service also receives, for each request, its route, status, duration and ids: never a body, a header or anything you saved.
When an app reminds you, the notification service your own browser uses (Google's, Apple's, Mozilla's or Microsoft's) carries an empty message from us to your phone at the time. It sees that your phone was woken then, never what the reminder says.
5. How long we keep it
| What | How long |
|---|---|
| Contact messages and job applications, including CVs | 12 months, then deleted automatically |
| Your account (email, name, profile picture, and the name and job title you add) | Until you ask us to delete it |
| A workspace: its name, plan, members and invitations | Until it is deleted. An invitation link works for 7 days; deleting a workspace deletes its apps too |
| An app and every version of its code | Until the app is deleted, from Apps or by your assistant; that deletes every version's code too. The address stays reserved, so nobody else is given it |
| Sign-in sessions | 30 days, then deleted |
| Where your first visit came from (a website's name, campaign tags, the page you landed on), and which days you used CloudCrane | With your account, until you ask us to delete it. Before you have an account, the note is a cookie in your browser for at most 30 days |
| Sign-in codes sent by email (kept only as a hash) | A code works for 10 minutes; the record that one was sent is deleted after a day, when the next code is sent |
| Assistants you connect: the name they give, where they send you back, and their tokens, kept only as hashes | Tokens until they expire (an hour, or 30 days to renew), then deleted. An assistant nobody approved is deleted after 30 days. The record of a connected one is kept until its workspace is deleted, also after you sign it out, which ends its access at once |
| The log of your assistants' calls | 12 months, then deleted automatically |
| A handle you gave up | Held for 90 days so nobody can pose as you, then deleted |
| A picture you upload for your handle | Until you remove or replace it, or delete your account |
| A reminder's time, and the address that wakes your phone (never what the reminder says) | A one-off until it's sent; a repeating one until you cancel it. The address goes when you stop reminders, after 90 days with none sent and the app not opened, or within a day of the app being deleted, taken down or no longer sending reminders |
| The encrypted copy of a shared list, which we can't read | 12 months after its last change, or within a day of its app being deleted or taken down. Each phone keeps its own copy |
| Problem reports: what broke in an app, its kind, line, version, day and a count, with no phone, person or IP address | 30 days, then deleted automatically; sooner if the app is deleted |
| A workspace's subscription | Until the workspace is deleted |
| Friend requests and friendships, from when CloudCrane had friends | Until the account that sent or accepted one is deleted. Nobody can see them |
| Upvotes and saves | Until you take one back, or the app or your account is deleted |
| Views of a public app's page, as one scrambled (hashed) visitor a day; no IP address is kept, and one day's visitor can't be matched to the next | Until the app is deleted |
| Remixes | Until you remove one that is waiting, or its workspace is deleted. One your assistant built stays with the app it became, as where it came from |
Deleting your account deletes the workspaces you alone are in, with their apps, your sessions and sign-in codes, and your friendships and the friend requests you sent. A deleted app's address tells the phones that still have it that it was deleted.
6. Security
Each workspace is isolated twice over: a membership check on every request, and row-level security in the database itself, so one workspace cannot read another's apps even if a query has a bug. Sessions, sign-in codes, invitation links and assistants' tokens are stored only as hashes, and logs remove sensitive fields before they are written. Every app runs at its own address, apart from this site and from every other app, and our cookies are set so that no app can read them.
We hold no third-party security certification today. When that changes, it will say so here, and not before.
7. Cookies
We use no advertising cookies and none from anyone else. The addresses apps run at set one only for an app kept to its owner or to the people invited to it: __Host-cc_pass, which says who you are to that one app so it opens for you. It lasts 180 days, renewed while you use the app, and the app's own code cannot read it. One cookie of ours, cc_src, notes where your first visit came from (see above); it lasts 30 days at most and is deleted when you sign in. Signing in sets __Host-cc_session, which keeps you signed in for 30 days; signing out deletes it. Signing in with Google also sets two cookies for the ten minutes it takes: __Host-cc_oauth, which checks that Google's answer belongs to the sign-in you started, and __Host-cc_next, the page to return you to. Both are deleted when you come back. Those three are httpOnly, so scripts cannot read them.
The dashboard keeps a few conveniences in your browser, such as the workspace you chose last; they never reach us.
8. Your rights
You can delete any app, with every version of it, from Apps or by asking your assistant, and sign an assistant out in Settings, under Assistants, at any time. You can also ask us for a copy of your personal data, ask us to correct it, or ask us to delete it or your whole account. For any of these, email support@cloudcrane.ai and we will respond within 30 days.
9. Contact
Questions about this policy, or about how your data is handled, go to support@cloudcrane.ai.
