Privacy policy

Effective date: 21 October 2026

This policy explains what information Design Pilot collects, how we use it, where we store it, who can see it, and how you can delete it. It includes how Design Pilot accesses, uses, stores and shares Google user data.

1. Who we are

Design Pilot is made and run by AuraScale. In this policy, "we" and "us" mean AuraScale. "You" means a person who uses Design Pilot.

For any privacy question or request, email support@dpilot.dev.

2. What Design Pilot is

Design Pilot has two parts.

• A desktop app for Mac and Windows. It runs on your computer.
• An online service at api.dpilot.dev. It stores accounts, teams and projects, and keeps everyone on a project in sync.

The app starts AI coding tools that you have installed and signed in to yourself. Those tools write prototype screens as HTML and CSS. Section 5 explains what that means for your data.

This website (dpilot.dev) sets no cookies, runs no scripts and does not collect information about visitors.

3. Information we collect

Account information from Google sign-in

You sign in with your Google account. We ask Google for the openid, email and profile permissions. From Google we store:

• your name;
• your email address;
• your Google account ID;
• your Google Workspace domain, if your account belongs to one.

We do not store your Google profile photo. We do not receive your Google password.

When you sign in, we create a sign-in session that lasts 30 days. We store only a one-way hash of the session token. The token itself is kept in your computer's system keychain.

Team and plan information

• The teams you belong to, your role (owner, admin or member) and your seat type.
• Invitations: the email address invited, who sent the invitation, and whether it was accepted.
• Requests for edit access, and who approved or declined them.
• Your AI plan type and the number of AI agents to run at once, if you set them.
• Billing status: plan, seat counts, billing period, trial dates and the IDs Polar gives the team's customer record and subscription. We never see or store card numbers.

Project content

Everything your team puts in a project is stored by the online service. This includes screens, styles, images, design tokens, the AI chat, project settings, checkpoints and library items (templates, presets, design systems and skills).

Context files

Context files are reference files you add to a project, such as a brief, a statement of work or a brand guide. You can upload them from your computer or link them from Google Drive. We store each file. For some file types we also store a plain-text copy, so the AI can read it.

Records of AI runs

For each AI run we store who started it, which AI tool, model and sign-in profile name were used, the instruction typed, which context files the run used, its status and its usage figures. We also store a log of the run: the AI tool's messages, the tools it used and the files it changed. This log can include text the AI tool read from your context files.

Emails we send

We send emails about your team: invitations, requests for edit access and their answers, notices when someone joins through your company domain, and trial reminders. We keep a record of each email: the address, the type of email and the details shown in it.

What we do not collect

Design Pilot has no advertising, no analytics service and no crash-reporting service. We do not store your IP address in our database. Our hosting provider, Cloudflare, processes IP addresses and other request data to deliver and protect the service (see section 8).

4. Google user data

This section covers all data Design Pilot receives from Google.

Google sign-in

Section 3 lists what we store from sign-in. We use it to create your account, show your name to your teammates, match you to team invitations sent to your email address, and offer to join your company's team when its admins turn on joining by company domain. We also use your email address as the address for the team emails in section 3, and we send it to Polar when you start a checkout (section 8).

Google Drive

Linking Drive files is optional. When you first choose "Add from Google Drive", the app asks your Google account for one more permission: https://www.googleapis.com/auth/drive.file. With this permission, Design Pilot can open only the files you pick in Google's file picker. It cannot see or list anything else in your Drive. Our server refuses and revokes any grant that is wider than this.

For each file you pick, Design Pilot reads:

• the file's name, type, size, last-modified time and revision;
• the file's content (Google Docs and Slides are saved as a PDF plus a plain-text copy; Google Sheets are saved as a CSV file; other files are saved as they are, up to 25 MB);
• the file's sharing list in Drive (the email addresses, domains and "anyone with the link" settings it is shared with).

How Drive data is used

• The file's content becomes a context file in the project you linked it to. People on the project can open it, and the AI tool can read it during a run if the "AI can use" switch is on for that file. The switch is on when the file is linked. You can turn it off at any time.
• The sharing list is compared with the project's members. If some members can't open the file in Drive, the app tells you their names before you link it, and later shows "Wider than Drive" if the Drive sharing narrows. We do not store the sharing list. We store only the result: whether everyone on the project can open the file.
• Every hour, and before each AI run, the service checks each linked file for changes using the Drive permission of the person who linked it. If the file changed, the service saves the new version.

How Drive data is stored

• File copies and their text copies are stored in Cloudflare R2 storage, as part of the project.
• To keep checking linked files, we keep the refresh token Google gives us for your Drive permission. It is encrypted (AES-256-GCM) with a key that only our server holds. We also store the Google email address the permission belongs to and the permissions granted.
• We never read the local folder that Google Drive for desktop keeps on your computer.

How Drive data is shared

• With the people on the project (section 7). They get the copy even if they cannot open the file in Drive themselves. The app warns you about this before you link the file.
• With the AI coding tool a project member runs on their own computer, under their own account with that tool's provider (section 5). This happens only when a run starts and the "AI can use" switch is on for that file.
• With our service providers, only to store and deliver the service (section 8).

We do not sell Google user data. We do not use it or transfer it for advertising, retargeting or interest-based ads. We do not use it to decide credit-worthiness or for lending. We do not transfer it to data brokers or information resellers.

Google user data and AI models

We do not use Google user data to create, train or improve any AI or machine learning model, and we do not let anyone else do so on our behalf. Design Pilot has no AI model of its own.

When a project member lets an AI tool read a Drive copy, the tool sends that content to its provider so it can answer. This happens under that member's own account with the provider. That provider's terms, and the member's account settings, decide how the provider handles the content, including whether it may use it to improve its models. Check them before you let AI use a file.

People reading your data

AuraScale staff do not read your files, Drive copies or project content, except when you ask us to (for example, to help with a support request), when it is needed for security (for example, investigating abuse or a bug), or when the law requires it.

Stopping Drive access

• In the app, open Project settings, then Context files, and choose "Disconnect" next to your Google account. We revoke the permission at Google and delete the stored token.
• You can also remove Design Pilot's access from your Google Account's security settings (Third-party apps and services). The next check finds the permission gone and stops using it.

When access stops, the copies already in projects stay there, held out of AI runs, until someone on the project removes the copy, links it again or chooses to keep using it. To delete the copies, use "Remove copy" on each file (section 11).

5. AI tools on your computer

Design Pilot does not include an AI model and does not send your content to an AI provider from our servers. Instead, the app starts an AI coding tool that you install and sign in to yourself, on your own computer. Today the app runs Claude Code (made by Anthropic). The app also detects Codex (OpenAI), OpenCode, Antigravity CLI (Google), Gemini CLI (Google) and Cursor Agent (Cursor) if you have them installed, but it does not run them yet. Each one stays switched off until it passes our safety checks.

When you start a run:

• the app writes the project's screens, the files the run may change, and the context files with "AI can use" switched on, into a working folder on your computer;
• the AI tool reads those files and your instruction, and sends them to its provider under your own account;
• the AI tool's answer comes back to your computer, and the app saves the changed screens to the project.

Your relationship with the AI provider is your own. Its terms and privacy policy apply to what the tool sends. We have no agreement with these providers that covers your content, and we do not receive your AI account credentials.

Context files can be switched off for AI at any time with the "AI can use" switch. Files switched off are not copied into the run's folder.

6. How we use information

We use information only to provide and improve the features you see in Design Pilot:

• to sign you in and keep you signed in;
• to run teams, invitations, roles, seats and plan limits;
• to store projects and keep everyone on a project in sync;
• to link, check and refresh Google Drive files you chose;
• to let you check and restore earlier states of a project;
• to send the team emails listed in section 3;
• to bill paid plans through Polar;
• to keep the service secure, fix problems and prevent abuse;
• to meet legal obligations.

We do not sell personal information. We do not use it for advertising.

7. Who can see your information

Inside your team

• Your teammates see your name and email address, your role and your seat.
• A project set to "team" is visible to every member of that team.
• A project set to "private" is visible to its owner, the team's owner and admins, and the people added to it.
• Everyone who can see a project can see its context files, including Drive copies, and its AI run records.
• Projects never move between teams. People outside your team cannot see your team's projects, names or email addresses.

Context files are never included in anything shared outside the team.

Outside your team

We share information only:

• with the service providers in section 8, to run the service;
• with the AI provider of a tool you or a teammate run, as section 5 describes;
• when the law requires it, or to protect the rights and safety of our users, the public or AuraScale;
• as part of a merger, acquisition or sale of AuraScale's assets. For Google user data, we will ask for your explicit consent first.

8. Service providers

• Cloudflare hosts the online service and this website. It runs our server code (Workers), our database (D1), our file storage (R2), the live project sync (Durable Objects) and our outgoing email (Cloudflare Email Service). It also hosts app updates at releases.dpilot.dev.
• Google provides sign-in, Google Drive and the Google file picker.
• Polar (polar.sh) sells paid plans as the merchant of record. It collects payment details, charges cards, handles sales tax and VAT, and sends receipts. When a team admin starts checkout, we send Polar the team's ID, the number of seats and the admin's email address. Polar's own privacy policy covers the payment details it collects.

We do not use any analytics, advertising or crash-reporting provider.

9. What stays on your computer

• Your sign-in session token, in your computer's system keychain.
• A working folder for each project you open, inside the app's data folder. It holds the project's files, and the context files used by the latest AI run.
• Sign-in profiles for AI tools, if you create them, in a folder named .design-pilot in your home folder. These hold the AI tool's own sign-in. Design Pilot does not send them to our servers.

These files stay on your computer until you delete them. Signing out removes the session token from the keychain.

10. How long we keep information

• Account and team information: while your account exists. We delete it when you ask us to (section 11).
• Projects: until the project is deleted. A deleted project is removed for good 30 days after deletion, with its files, checkpoints, version files and AI run logs.
• Teams: when an owner deletes a team, its projects are deleted at once and removed for good 30 days later. The team record is removed after that.
• Context files and Drive copies: until someone removes the file from the project, or the project is deleted. When a file is removed, we delete the stored copy and its text copy straight away, unless the same file is still in use elsewhere (for example, in a copy of the project). Then it is deleted when nothing uses it.
• Drive permission tokens: until you disconnect Google Drive, revoke access in your Google Account, or Google tells us the permission is no longer valid.
• Sign-in sessions: each session expires after 30 days or when you sign out. Expired session records are kept until your account is deleted.
• Email records: while your account exists.
• Backups: our database provider keeps recovery copies of the database for a limited time, so deleted database records can remain in those copies until they expire, which takes up to 30 days.

If a paid plan ends, nothing is deleted. Extra projects become read-only until the team upgrades again.

11. Managing and deleting your data

You can do these in the app:

• Stop the AI from reading a file: turn off "AI can use" for that file in Project settings, Context files.
• Delete a context file or Drive copy: choose "Remove copy" for that file in Project settings, Context files.
• Disconnect Google Drive: choose "Disconnect" in Project settings, Context files.
• Delete a team (team owners): Team settings, then "Delete team". This deletes all of the team's projects as described in section 10.
• Sign out: from the account menu.

To delete your account, delete a single project, get a copy of your data, or correct it, email support@dpilot.dev from the email address on your account. We will reply within 30 days. When we delete your account, we delete your profile, sessions, Drive permission token and team memberships. Projects you worked on belong to your team, so they stay with the team unless the team asks us to delete them.

Depending on where you live, you may have rights to access, correct, delete or export your personal information, to object to or limit how we use it, and to complain to your local data protection authority. Email us to use any of these rights.

12. Security

• All traffic between the app and the online service uses HTTPS.
• Google Drive refresh tokens are encrypted at rest. Sign-in session tokens are stored only as one-way hashes.
• Every request to a project checks that the person is a member of its team and is allowed to see it.
• AI tools run inside a folder the app prepares for each run. On macOS the app limits what the AI tool can read and change outside that folder.

No system is perfectly secure. If we learn of a breach that affects your information, we will tell you as the law requires.

13. Where information is processed

Cloudflare runs our service on its global network, so your information may be stored and processed in countries other than your own. We have not chosen a specific storage region.

14. Children

Design Pilot is a work tool. It is not meant for anyone under 16, and we do not knowingly collect information from them.

15. Changes to this policy

If we change this policy, we will post the new version on this page with a new effective date. If a change affects how we use Google user data or other personal information in a new way, we will tell you in the app or by email, and ask for your consent where the law or Google's policy requires it, before the change applies.

16. Contact

AuraScale
Email: support@dpilot.dev