Legal
Privacy policy
Controller: J&L Serverid OÜ (registry code 11478495), Haaviku tee 9, Külitse alevik, Kambja vald, 61702 Tartu maakond, Estonia. Contact: support@sprintproof.com.
This policy covers three things: this website and its free tools (sprintproof.com), the SprintProof app where teams plan features, and the SprintProof plugin for ChatGPT and Codex, which is not available yet.
On this website
Waitlist. If you join the waitlist we store your email address, and the company name and team size if you give them, plus the page you signed up on. We use them to tell you when SprintProof opens. Legal basis: your consent, which you give by joining and can withdraw at any time. Kept until you leave the waitlist, and deleted 12 months after we email you that SprintProof is open. Joining the waitlist adds you to no other mailing list.
Planning poker. A room stores the names and cards of its participants. Rooms are deleted after 24 hours without activity. Your browser keeps a random token for each room you join so it can vote for you; it is not used for tracking.
Free estimator and story points calculator. The estimator sends the numbers you type to our server to run the simulation and does not store them. The story points calculator runs in your browser.
In the SprintProof app
Your account. Your name, email address, the sign-in method you use and the workspaces you belong to, with your role in each. If you arrive from a link that names where it was posted (for example a launch site or a newsletter), we keep that one word with your account, to see which places bring people to SprintProof.
Signing in. You can sign in with an email link or a passkey. Each sign-in session records its time, IP address and browser, so you can see and end your sessions and so we have evidence if a payment is disputed.
Passkeys. If you use a passkey, we store the public part of it and when it was added and last used. You can remove a passkey in Settings.
Workspace content. What your team puts into SprintProof: feature plans, briefs, interview answers, parts, estimates, comments, sign-offs, tasks, your own checks, and the brand kit (logo, colors, fonts). It belongs to your workspace and is visible to its members, and to anyone you share a read-only link with. Plans someone deletes stay in Recently deleted for 30 days, then they are removed for good. When the workspace is deleted, its content is removed.
Usage and credits. Which AI actions were run, by whom, and how many credits they used, so admins can see usage and set limits. A new workspace gets 100 AI credits once, free of charge.
You need to give an email address to join the waitlist or create an account, and payment details and a billing address to buy a plan or top-up. Without them we can't provide that part of the service.
What we keep after deleting
When a workspace or an account is deleted, its content is removed. We keep:
- Billing and usage records (payments, credits, AI use per day) for 7 years, for tax and payment disputes.
- Sign-in history (time, IP address, browser) for 120 days after a session ends, for security and payment disputes. This also applies while your account exists.
A deleted account's name and email address are removed. Comments and billing records it left stay, without them.
AI processing
AI features (the interview, breakdown, gap review, task drafts, presentations and questions to the planner) send the relevant parts of a plan to AI models through OpenRouter. Models come from Anthropic, OpenAI and Google, chosen per job; OpenAI’s embedding model is also used to match a plan to checks in the library. We store which model ran, token counts, cost and status for each call, not the prompt or the answer.
Text written in a plan is sent to TypeSafe (USA) to be screened for prompt injection.
The AI suggests and people accept: nothing in a plan changes until someone clicks.
Payments
Subscriptions and credit top-ups are handled by Stripe. Stripe receives your billing details and card. With Stripe Tax, checkout also collects your billing address and, for a business, its VAT ID, to calculate and report VAT. Legal basis: legal obligation. We store the subscription status and plan, and which version of the Terms of service was accepted at checkout and when. Stripe’s privacy policy applies to what it processes.
Payment disputes. If a payment is disputed, we send Stripe evidence for it: the purchase, the terms acceptance, the sign-in history of the account that paid and the workspace’s usage.
Withdrawals. If you withdraw from a contract, we keep your name, email, the contract reference and the date and time of your withdrawal, to confirm it and handle the refund (legal obligation). Kept for 3 years.
Integrations
If an admin connects Jira, Linear or GitHub, we store an access token for that connection and send the tasks you choose to push (title, description, acceptance criteria, why the task exists, estimate range, a task-type label, dependencies and a link to the plan). An admin can disconnect at any time.
ChatGPT and Codex plugin
The plugin is coming soon and is not available yet. When it is available, connecting it signs you in to the same workspace through OAuth. You approve what it may do, and admins can turn plugin access off or make it read-only. What ChatGPT or Codex itself stores is covered by OpenAI’s policies.
What the plugin reads. With your approval, plans (title, brief, parts, estimates, gap questions), tasks, review comments and sign-offs, the workspace’s credit balance and which integrations are connected. Looking up checks in the check library needs no account.
What the plugin writes. Changes to plans and tasks you ask for: drafting a breakdown, editing or removing a part, answering a gap question, creating or updating tasks (status, owner, acceptance criteria, dependencies, a pull request link, time spent), requesting a review and creating a presentation. AI suggestions are applied only after you accept them. The plugin cannot manage members, billing or integration connections, and it cannot sell anything.
What is sent. Only the plan context, parts, review content, identifiers and credit data needed for the request you made. The plugin does not ask for your chat history. When you plan a change to code, the source code and secrets stay on your machine and only descriptions and the paths needed are sent. Do not put passwords, payment details or sensitive customer records into a request.
Permissions. The plugin gets separate permissions to read and to write plans and tasks, and to read workspace information. Each request is checked against your current workspace membership and the workspace’s plugin setting (off, read-only or full). You can disconnect the plugin at any time in Settings > Security, under Your sessions, where each plugin connection is listed with a Disconnect button. Admins can also set plugin access to off or read-only there.
How long it is kept. Request records are kept for up to 7 days. Files the plugin creates are deleted within an hour after their 15-minute download link expires. Connection records are deleted 120 days after the connection ends; the approvals you gave are kept until you delete your account or workspace. Anything saved into a plan is workspace content and follows the rules above.
Sharing. Plugin requests that use AI go through the same providers as in the app (see AI processing). A plan becomes public only when you share it with a link, never because the plugin touched it.
Contact. Questions about the plugin or your data: support@sprintproof.com.
Why we use your data
- To provide the service (contract). Your account, workspace content, usage and credits, AI processing, integrations, the plugin and payments.
- Security and abuse prevention (legitimate interest). Server logs, sign-in history, rate limits, and evidence for payment disputes. Our interest is keeping SprintProof and your data safe.
- Legal obligations. Billing and usage records are kept for 7 years for tax, and the billing address and VAT ID collected at checkout are used to calculate and report VAT.
- Consent. The waitlist notice. We send no marketing email: the emails we send are sign-in links, invitations, mentions, order confirmations and withdrawal acknowledgements.
Server logs, cookies and analytics
Our servers log requests, including IP addresses, for security and abuse prevention. Server logs are kept in files of a fixed size, and older entries are overwritten as new ones arrive. Sign-in records are kept while the session lasts and for 120 days after it ends. The app uses cookies only to keep you signed in and to protect forms. This site sets no advertising cookies. Cloudflare Web Analytics counts page visits without cookies. We count visits on our own server, without cookies. PostHog, hosted in the EU, counts sign-up and checkout steps under a coded ID, with no cookies and without your name, email address or IP address. Other usage figures come from our own database.
Processors and transfers
Hosting provider (EU), Cloudflare (content delivery and protection), Zoho’s ZeptoMail (sending sign-in, invitation, mention, order and withdrawal emails), OpenRouter and the model providers it routes to (Anthropic, OpenAI, Google), TypeSafe (prompt-injection screening, via OpenRouter), Stripe (payments), PostHog (sign-up and checkout counts, EU). Jira (Atlassian), Linear and GitHub receive data only when an admin connects them. They act on our instructions under data processing terms, except where they are separate controllers, such as Stripe and the tools you connect.
Some of these providers process data outside the European Economic Area, including in the United States. Where a provider is certified under the EU–US Data Privacy Framework, the transfer rests on that certification. Otherwise it rests on the European Commission’s standard contractual clauses; OpenRouter’s privacy policy, for example, says it relies on them for EU transfers.
You can get a copy of the standard contractual clauses from support@sprintproof.com.
Your rights
You can ask to see, correct, export, restrict or delete your data, object to how we use it, or leave the waitlist, by writing to support@sprintproof.com. We respond within one month, as the GDPR requires. Where we rely on consent you can withdraw it at any time. Workspace admins can delete plans and the workspace itself. You may complain to the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon, aki.ee) or to the supervisory authority where you live.
Changes
We may update this policy. The date below changes. We will give reasonable notice of material changes.
Last updated 10 November 2026.