Privacy Policy

What personal data Polaris collects, why, who processes it, how long we keep it and your rights.

Effective 1 November 2026. Version: Beta.

This policy explains what personal data Polaris collects, why, who we share it with, how long we keep it, and your rights.

Who we are

Polaris is run by Andreas Asprou LTD, a company registered in Cyprus (registration number HE 446408, registered office 10 Spyrou Kyprianou, Mesa Geitonia, 4001 Limassol, Cyprus). For personal data about our customers and visitors, we decide how it’s used, so we’re the “controller”. Contact us at andreas@plrs.sh.

Your content can be different.

If you use Polaris for work, your Organization is responsible for any personal data in your code, transcripts and other content. We handle that data on its instructions as a “processor”, under our Data Processing Addendum. This applies even on a Personal Organization.
If you use Polaris for yourself, not for a business, this policy covers your content too.

What we collect

Account information.

From GitHub when you sign in: your name, email address, GitHub username and ID, and profile picture.
If someone invites you to an Organization, we get your email address from them.
The Organizations you belong to and your role in each.
If you request beta access: your email, GitHub username and what you’d like to use Polaris for.

Your content.

Code your Machines clone from your repositories, and files you create or upload.
Session transcripts: your prompts, agent replies, command output and diffs.
Recaps, Previews and shared files.
Voice and dictation audio, if you use those features.

Credentials you connect. Agent sign-ins, API keys, GitHub tokens, and project Secrets and other environment variables. See “How we protect your data” below.

Billing information.

Your plan, usage, purchases, invoices and billing address.
Stripe collects your card details. We don’t store your full card number.
To prevent repeat free trials, we keep hashed versions of your GitHub ID and, where Stripe provides one, your card’s fingerprint.

Usage and device information.

Product analytics: which pages and features you use, with any text you type masked. It stores nothing on your device.
Error reports: browser type, the page and the error.
Server logs: requests, timings and error codes.
Our servers and providers see your IP address when you connect.

Cookies and storage on your device.

We use cookies needed to sign you in, keep you signed in, connect GitHub and open Previews. These don’t need your consent.
Our product analytics runs without cookies or other storage on your device.
Your browser keeps recent transcripts (up to 14 days), drafts, unsent dictation and preferences so Polaris loads fast. Signing out clears the saved transcripts.
We don’t use advertising cookies or third-party advertising trackers. We don’t respond to Do Not Track signals; we treat everyone the same.

Why we use it

Purpose	Data	Legal basis (EU/UK GDPR)
Provide Polaris: accounts, Machines, Sessions, sharing, Previews	Account data, content, credentials	Performing our contract with you; for members invited to an Organization, legitimate interests (providing the service the Organization uses)
Polaris AI features: recaps, dictation, voice	Transcript text, audio	Performing our contract with you; for work content, your Organization’s instructions
Billing, invoices and tax	Billing data, account data	Performing our contract with you; legal obligation (tax and accounting)
Preventing repeat trials and payment fraud	GitHub ID, card fingerprint	Legitimate interests (keeping free trials fair)
Keeping Polaris secure, preventing abuse, fixing problems	Logs, error reports, IP addresses, account data	Legitimate interests (running a safe, working service)
Product analytics	Usage data	Legitimate interests (understanding how Polaris is used, to improve it)
Improving Polaris by looking at Sessions	Content and transcripts	Legitimate interests (improving the product). You can ask us to exclude your Organization
Service emails: billing and changes to our terms	Email, name, Organization name	Performing our contract with you; legal obligation
Invitations to join an Organization	The invitee’s email, the inviter’s and Organization’s names	Legitimate interests (letting Organizations invite their members)
Legal claims and compliance	Records we must keep	Legal obligation; legitimate interests

Do you have to give us this data? We need your GitHub sign-in and, for paid plans, billing details. Without them we can’t provide Polaris. You choose what content and credentials to provide, and whether to use optional features. We also collect the technical records needed to run and secure Polaris.

Automated decisions. We don’t make decisions about you that have legal or similarly significant effects using automated means alone.

We don’t sell personal data, use it for advertising, or train AI models on it.

Service providers. We use service providers to run Polaris, and they may use your data only to provide their service to us. Stripe also uses some payment data for its own purposes, such as preventing fraud, under its own privacy policy. Our Subprocessors page lists each one, what it does, what it can see and where it is. In short:

AWS hosts our servers, database and file storage, mostly in Oregon, USA.
Sail runs the Machines your agents use. They can technically read everything on a Machine.
OpenAI, under our account, runs recaps, dictation and voice.
- A recap sends up to about 240,000 characters of a Session’s transcript, with known secrets masked.
- Voice sends your audio and the Session content its tools read.
- Recaps are on by default; Organization Owners and Admins can turn them off.
- We ask OpenAI not to store recap requests. OpenAI doesn’t train on this data. Its terms let it keep data for up to 30 days to check for abuse, or longer where the law requires.
GitHub handles sign-in and the repository access you grant.
Stripe processes payments.
PostHog (EU) runs product analytics and Sentry (EU) collects error reports.
Resend sends emails.
Restate runs background jobs. It receives IDs only.

Services you choose.

When you connect a model provider (Anthropic, OpenAI, OpenRouter or Google), your agent sends prompts and code to it under your own agreement with that provider.
The same applies to MCP servers, gateways and cloud accounts you connect.
Their privacy policies cover what they receive.

People you share with.

Organization Owners and Admins can read every Session in their Organization.
People you share a Session with can see it.
Anyone with a public Preview link or shared-file link can open it until it expires or you revoke it.

When the law requires it. We disclose data when we’re legally required to. Where we’re allowed to, we’ll tell you first.

If Polaris changes hands. If our business is sold or merged, your data would move to the new owner under this policy, and we’d tell you first.

International transfers

We’re based in Cyprus, in the EU. Our main systems and most of our providers are in the United States. When we send personal data outside the EU or UK, we rely on:

the EU–US Data Privacy Framework (and its UK Extension) where the provider is certified; or
the European Commission’s Standard Contractual Clauses (with the UK Addendum).

Email andreas@plrs.sh for a copy of the safeguards for a particular provider.

How long we keep it

Data	How long
Session transcripts and recaps	Until you delete their Workspace, or ask us to delete them
Machines and their files	Until you delete the Workspace
Account and Organization data	While your account is open. After you ask us to delete it, we remove it from our active systems within 30 days
Shared files	Your Organization’s chosen period (7, 30, 90 or 365 days; 365 by default), then deleted
Feedback reports you send	Until you ask us to delete them
Billing records and invoices	7 years after the end of the financial year, as Cypriot company and tax law requires
Trial checks (hashed GitHub ID and card fingerprint)	24 months after the trial ends
Billing usage records	As long as we need them for billing and tax
Analytics events waiting to be sent	Up to 7 days
Beta access records (IDs only)	400 days, locked against changes
Database backups	14 days
Server logs	14 days
Error reports (Sentry)	90 days
Product analytics (PostHog)	Until you delete your account; we then delete your events
Secret broker log (which key, when)	90 days
Cloud-access audit records	365 days
Voice call records (captions and summary, not audio)	30 days. We look at them only to fix problems
Dictation audio	Deleted from our servers once you insert or discard the text
Beta access requests	About 1 year
Transcripts saved in your browser	Up to 14 days; cleared when you sign out

Deleting a Workspace removes its Sessions from our active systems; backups clear within 14 days. It doesn’t remove shared files (they follow their own period) or feedback reports you’ve sent. Ask us and we’ll delete those too.

Self-serve account and Organization deletion isn’t built yet. Email andreas@plrs.sh. After checking the request comes from you, we remove the data from our active systems within 30 days, and backups clear within 14 days after that. We’ll tell you if we must keep anything, such as invoices, and why.

How we protect your data

Our Security page explains this in detail, including what we haven’t done yet. In short:

We encrypt data in transit and at rest.
Each Workspace runs on its own Machine.
Stored credentials are sealed.
Staff open customer content only for the reasons in section 11 of our Terms, and record each time.

Your rights

You can ask us to:

give you a copy of your personal data;
correct it;
delete it;
restrict or object to how we use it, including uses based on legitimate interests;
give you your data in a portable format.

These rights apply wherever you live, because we’re based in the EU. Where we rely on your consent, you can withdraw it at any time.

Email andreas@plrs.sh. We reply within one month. We may need to confirm your identity first. If the data is part of an Organization’s work content, we may need to involve that Organization.

You can complain to a data protection authority. Ours is the Commissioner for Personal Data Protection in Cyprus (dataprotection.gov.cy). You can also contact the authority where you live or work.

California residents: we don’t sell your personal data or share it for cross-context behavioural advertising.