Privacy policy

1. What we collect

Three kinds of information, and they are treated differently:

• Account information — your name, work email, company, and role in a workspace, plus sign-in events. Authentication is handled by WorkOS; we never receive or store your password.
• Workspace content — everything you and your team put into Brikt: projects, schedules, activities, progress, comments, blockers, delay records, reports, files you upload, and the messages you send to Claude. This is your content, and section 7 of our terms says so.
• Technical information — IP address, browser and device details, timestamps, the pages and actions in a session, and error diagnostics when something breaks.

2. What we use it for

To provide the service: run the scheduling engine, serve your projects, deliver reports, and let the people you invited collaborate.

To authenticate you and keep the service secure, including detecting and investigating abuse.

To bill you, when you are on a paid plan, and to send the invoices and payment notices that go with it.

To support you when you ask, which sometimes means looking at your workspace to reproduce a problem.

To send service messages — changes that affect you, security notices, and billing events. We do not send marketing email from the product.

3. AI features and your project content

When you use Ask Claude, request a draft or proposal, import a schedule, or generate a narrative, the relevant schedule content and your message are sent to Anthropic's API to produce the response. That is what makes the feature work; without it there is nothing to answer from.

Anthropic's commercial terms do not permit content submitted through their API to be used to train their models, and we do not use your project content to train models of our own.

Project memory, when it is on, stores facts about your project and your team's preferences so that Claude's answers get better over time. Building it requires computing embeddings, which is done through Google's embedding API. Memory is scoped to your workspace: it is never shared with another customer, and Brikt does not carry what it learned on your project into anyone else's.

AI output is a draft. Every AI-authored change to a schedule arrives as a proposal a person on your team reviews and applies — Brikt does not let an AI commit a change on its own.

4. Who else processes it

Brikt runs on third-party infrastructure. Each of these providers processes data only to deliver its part of the service, under contract:

• Vercel — application hosting and delivery.
• Neon — the PostgreSQL database that holds your workspace.
• Cloudflare R2 — object storage for files you upload and for generated report documents.
• Upstash — Redis, used for rate limiting and short-lived state.
• Ably — realtime collaboration, so people editing a schedule together see each other's changes.
• WorkOS — authentication, sessions and identity.
• Stripe — payment processing and invoicing, on paid plans.
• Anthropic — the Claude models behind every AI feature.
• Google — embeddings for project memory.
• Resend — transactional email, when email delivery is enabled.
• Sentry — error monitoring, so we find out when something breaks.
• PostHog — product analytics. See section 7: it is present but collecting nothing today.

5. What we do not do

We do not sell personal information, and we do not share it for cross-context behavioural advertising.

We do not use one customer's project data to serve another customer.

We do not run advertising, and we do not embed third-party advertising or tracking on brikt.ai.

We disclose data outside the list in section 4 only when the law requires it, and we will tell you if we are permitted to.

6. Where it lives, and how it is separated

Brikt is hosted in the United States. The database runs in an AWS US region and the application is served from US infrastructure. We do not offer EU or UK data residency today; if you need it, tell us and we will be straight with you about where we stand.

Every table in the database carries row-level security, so a request can only read the workspace it is authenticated for. Sessions are encrypted and can be revoked. A report share link is a token: any miss — wrong, revoked, expired or malformed — returns one byte-identical 404, so the link cannot be used to discover what exists.

Brikt holds no security or compliance certifications, and this page will not imply otherwise. If you find a security problem, email [email protected] and we will take it seriously.

7. Cookies and analytics

Brikt sets a session cookie so that you stay signed in, and stores your interface preferences (such as the light or dark theme) in your browser. Those are necessary for the product to work and are not used to track you.

Product analytics are built into the application but are not switched on: no analytics key is configured, so nothing is collected and no analytics cookie is set. If that changes, this page will be updated before it does.

We do not use advertising cookies or cross-site trackers of any kind.

8. How long we keep it

Workspace content is kept while your workspace is active, and for a limited period after cancellation so that you can export it. After that it is deleted.

Audit records — who changed what, and when — are kept longer than ordinary content, because being able to show what happened is the point of having them.

Billing records are kept for as long as tax and accounting law requires.

You can ask us to delete your workspace and its content at any time. See section 9.

9. Your choices

Email [email protected] to request a copy of your data, to correct something, to have your workspace exported, or to have it deleted. We will confirm your identity and then do it.

If you are an invited collaborator rather than a member of the paying company, that company controls the project content you can see. Write to us anyway and we will route your request and tell you what we did.

Depending on where you live you may have additional rights over your personal information — access, correction, deletion, and the right not to be discriminated against for exercising them. We honour those requests through the same address, and we do not sell or share personal information in the first place.

10. Children

Brikt is a tool for people doing their jobs. It is not intended for anyone under 18, and we do not knowingly collect information from children.

11. Changes to this policy

We will update this page when what we do changes, and we will change the date at the top. For a change that materially affects how your information is handled we will give notice by email or in the product before it takes effect.

12. Contact

Clear Skies Aviation Enterprise LLC, doing business as Brikt — privacy questions, data requests and security reports all go to [email protected].