Legal

Privacy policy

What we collect, where it goes, how long we keep it, and how to get it deleted.

Effective 14 October 2026. Questions and requests: access@prusik.one.

1. Who is responsible

Prusik (the company behind Prusik; legal entity and registered address to be stated here before launch) is the controller for the personal data described here. Contact: access@prusik.one.

2. What we collect

  • Account data. Your name, email address and Google account id from Google sign-in, and the time you signed up.
  • Workspace content. The messages you send, the files you upload or connect, the outputs you receive, and the settings you choose. You decide what goes in.
  • Usage and billing. Which model handled each call, how many tokens it read and wrote, what it cost, and your credit balance. Purchases are recorded with a Stripe reference; we never see your card number.
  • Audit log. An append-only record of security-relevant events: sign-ins, tier changes, approvals, outbound requests the firewall checked, and sign-ups. It exists so that you and we can verify what the agent did.
  • Technical data. IP address and browser details in server logs, kept for a short time for security and troubleshooting. We set one session cookie and run no analytics or advertising trackers.
  • Contact forms on getprusik.ai. What you type into the access-request and trust-model forms: your email address, your name for the trust-model download, and, for an access request, what your team handles and who must not see it. It is delivered to us as a message in our Slack workspace and used only to reply to you.

3. Why, and on what basis

We process this data to provide the service you asked for (contract), to keep it secure and to bill for it (contract and legitimate interest), and to meet legal obligations such as tax records. We do not sell personal data and we do not use workspace content to train models.

4. Who processes it for us

ProcessorWhat forWhere
Google CloudHosting of the application and its storage, and Google sign-inFrankfurt, Germany (europe-west3)
NEAR AI Cloud and the model providers behind itRunning the AI models. In the Basic tier with zero data retention; in Guarded and Secret inside a trusted execution environment, as described in the technical overviewProvider dependent; frontier models are pinned to EU endpoints where the provider offers them
TypeSafeThe outbound firewall's classifier decides whether a request the agent wants to send may leave. In the Basic tier it sees that request, its target and the recent turns of the conversation; in Guarded only the request payload; in Secret nothing, because nothing goes outUnited States
StripePayments. Stripe holds your card details and your billing contact under its own privacy policyEU and United States
SlackDelivery of the website's contact-form messages to usUnited States
RailwayHosting of the website getprusik.ai, which stores nothing itselfUnited States

Where data leaves the EU, we rely on the provider's standard contractual clauses or an adequacy decision.

5. How long we keep it

  • Workspace content stays until you delete the conversation or file, or close your account.
  • Payment records (amount, date, Stripe reference, billing contact) are held by Stripe for as long as tax law requires, typically 10 years. Our own credit ledger (the balance and each charge) is deleted with the account.
  • Per-call usage records (which model, token counts, timings, the account's number; never content) are kept after account closure for capacity planning. The agent label on them, which can echo a task name, is blanked when the account closes; they then carry the account number only, not your name or email, which are deleted with the account.
  • Contact-form messages stay in our Slack workspace until the request is closed, at most 12 months.
  • The audit log is permanent. Its event rows (who did what, when, with the hash chain that proves they were not altered) are never deleted, not after account closure either; they carry your email as the actor and event metadata, not your content. The content attached to some events, such as what the outbound firewall was shown, carries an expiry set by the tier (30 days in Basic, 14 in Guarded, none in Secret) after which it may be removed.
  • Server logs are kept for 30 days.
  • Skills you shared or published stay available to the people you gave them to after your account closes, without your name; private skills are deleted with the account.
  • Closed accounts are deleted within 30 days of the request, except for the records above and one abuse-prevention record: the email address and Google account id of the closed account, kept so that the welcome credit is granted once per person and not once per account. It holds no content and is removed when an administrator lifts it.

6. Your rights

You can access, correct, export or delete your data, object to processing, and complain to your data protection authority. Write to the address above from the email on your account. We answer within one month.

7. Changes

We will post changes to this policy here and, for material changes, tell you in the app or by email before they take effect.