What Plune does with your data

Who is responsible

• Plune is run by a sole proprietor, ФОП Маєвський Л. Л., Ukraine. Write to [email protected].
• Plune is in beta and is not in production yet. Where a detail below is marked as set before launch, it is not decided yet, and this page will be updated first.

What Plune holds

• Your account: the email address you sign in with, and a display name, language and theme if you set them.
• Your work: projects, test cases, runs and results, and the audit log that records who changed what.
• For every file a run leaves behind (a screenshot, a trace, a video, a log): its name, type and size. Where the file itself lives is below.
• A session cookie, plune_session, set when you sign in with an emailed link. It lasts seven days. The link lives 15 minutes and works once.

Where your files live

• A project can connect a bucket of its own (AWS S3, Cloudflare R2 or another S3-compatible storage). Files then go straight between your browser or CI and the bucket, through short-lived signed links. Plune keeps one line about each file and never holds a copy of the bytes.
• Without a bucket, screenshots (up to 2 MB) and JSON or text files (up to 512 KB) are kept in Plune’s built-in storage, up to 1 GB per project. Traces, videos and other files are not kept at all; only their names are.

What is stored encrypted

• The API key of an AI provider and the secret access key of a bucket are stored encrypted. They are never shown again, to anyone. To change one, you replace it.

AI providers

• Plune has no AI provider of its own. Nothing goes to an AI provider unless an owner of a project connects one with a key of their own and ticks the consent box.
• When someone on that project asks for a draft from code, the code of that one test, the name and tags of the case, the model and the language go to the provider the owner chose. Secrets in the code are masked first. The other tests of the file and any run or result do not go.
• An owner can also connect one fallback provider, with its own key and its own consent box. The code goes to the fallback only when the primary provider fails for a reason on its side, and never when the primary rejected the key or address.
• Removing a provider’s key erases it. Switching AI off for a project switches off both providers.

Other services that handle data

• Resend sends the sign-in emails. When you send the product-updates or the waitlist form on plune.ai, Resend keeps your address as a contact in that list from that moment, marked as not subscribed until you confirm it, and sends the confirmation email. To leave a list, or to have an address you never confirmed removed, write to [email protected].
• plune.ai is served from a server at Hetzner.
• Database backups are kept in a Cloudflare R2 bucket.
• plune.ai and docs.plune.ai count visits with a self-hosted Umami, which sets no cookie.
• Plune does not take payments yet. When it does, card payments will go through Monopay (Ukraine) or Lemon Squeezy (other countries); Plune will not see or store card numbers. This page will name them before the first payment.

Keeping and deleting

• Deleted runs and cases wait in the Bin for 30 days. An owner of the project can put them back; after that they are gone for good. The audit log stays.
• In the built-in storage, when a project is full, its oldest files leave first to make room.
• On the Free plan, runs older than 30 days are deleted for good, without the Bin, and so are the oldest runs beyond 200 000 results per account; the newest run and any run still in progress stay. Paid plans will keep full results for 6 months, with daily summaries kept longer. Encrypted database backups are kept for up to 3 months.
• You can delete your account in Account → Profile. Projects and companies that nobody else is in go to the Bin with it; if you are the only owner of one where other people work, hand ownership over first — until then the account cannot be deleted. A deleted account waits in the Bin for 30 days — to restore it, write to [email protected] — and is then purged: your email address and name are removed from the account, and your sessions, tokens and invitations go. Encrypted backups may keep a copy for up to 3 months.
• Some history keeps your name or address after that, for as long as the project or company it belongs to keeps its history: where it was written into the activity log (“added … as member”). Elsewhere in a project — as the author of a saved version of the requirements matrix, or of a run — you are shown as “deleted account”. A company that removed you from a domain it uses for single sign-on keeps your address so that signing in does not bring you back; a new invitation from it lifts this.
• We keep this history so that each team can see who did what in its own work, and to keep Plune secure. Our legal basis is legitimate interest (GDPR Art. 6(1)(f)). You have the right to object to this at [email protected].
• Files in a bucket of your own are not ours; delete them there.

Your rights

• You can delete your account yourself, as above. For a copy of your data or a correction, write to [email protected]. The legal terms of service are set before launch.

Questions

Write to [email protected]. The Draft from code and Files in your own bucket pages in the documentation describe the two features above in full.