Privacy policy

Version 1.0. Effective [EFFECTIVE_DATE]. Words in square brackets are placeholders.

The short version

  • We keep your data in the EU. Photos, rooms and accounts live on servers in Germany and Finland.
  • We do not use your photos, videos or rooms to train AI models. Our vendors may not either.
  • We remove location data from your photos when you upload them.
  • We do not sell your data. We do not run ads. We do not track you across sites.
  • You can export all your data and delete your account in settings, with no email to us.
  • One step runs outside the EU: the assistant sends scene data and small views of your room to Anthropic. Section 7 explains.

1. Who is responsible

The controller is [COMPANY_NAME], [COMPANY_FORM], Krivių g. 5, 01204 Vilnius, register number [REGISTRATION_NUMBER] (“plintus”, “we”). For your data, write to privacy@plintus.ai.

We have no data protection officer, because the law does not require one for us. If that changes, we will name one here.

For the content of Studio customers, the customer is the controller and we are the processor. The data processing agreement covers that.

2. What data we handle

Data What it is Where it comes from
Account data Name, email, sign-in method (Google, Apple, X or email), language, units, workspace and role You, and the sign-in provider you pick
Sign-in and session data A session cookie, time of last use, browser type, a hash of the session id Your browser
Content Photos, videos, 3D rooms, designs, versions, comments, share links, assistant questions and answers You
Guest data A random session id and the content a guest uploads Your browser
Payment data Plan, seats, credit balance, credit ledger, invoices, billing name and address, VAT ID, the last 4 digits and brand of your card. Stripe holds the full card number. We never see it. You and Stripe
Usage data Which features you use, job records (type, time, cost in credits, result), errors Our systems
Site and product statistics Page views and named events (for example “signed up”). No cookies. No personal data. Our own analytics, Umami
Technical data IP address, browser, device, graphics card name, error reports Your browser and our servers
Support mail What you write to us and our reply You
Link click data A random click number when you press a buy link Our systems

Your photos can show things we did not ask for, for example people, family pictures, documents, or a view from a window. We do not look for those things and we do not identify people. We do not process faces to recognise anyone. If you can, keep people out of your photos.

Purpose Data Legal basis (GDPR)
Give you plintus: make your account, scan rooms, make pictures, run the editor and the assistant, share rooms Account, content, session, guest, usage Contract, Article 6(1)(b)
Take payments, give credits, send invoices, handle refunds Payment, account, usage Contract, Article 6(1)(b). Tax and accounting law, Article 6(1)(c)
Keep records that tax and accounting law require Invoices and payment records Legal duty, Article 6(1)(c)
Send service mail: scan done, invoice, renewal reminder, share and invite mail, security notices Account, usage Contract, Article 6(1)(b)
Keep plintus safe: stop abuse, bots and fraud, apply the daily limit on guest spend, fix errors, back up Technical, usage, session Legitimate interest, Article 6(1)(f). Our interest is a safe, working service
Measure and improve plintus with cookie-free statistics Site and product statistics Legitimate interest, Article 6(1)(f). Our interest is to know what works. We collect no personal data for this
Answer your support questions Support mail, account Contract, Article 6(1)(b), or legitimate interest, Article 6(1)(f)
Track partner link clicks so stores can pay us a commission Link click data Legitimate interest, Article 6(1)(f). We send no personal data to the store or the network
Send you product news or offers by email Account Consent, Article 6(1)(a). We do not do this at launch. We will ask first, and you can say no
Use your content to improve AI models Content Only with your consent, Article 6(1)(a). We do not do this today
Answer legal claims, follow the law, answer authorities Any, as needed Legal duty, Article 6(1)(c), or legitimate interest, Article 6(1)(f)

When we rely on legitimate interest, you can object. See section 10.

4. How long we keep it

Data How long
Guest content 7 days, then deleted. If you sign in within 7 days, it moves to your account
Account data and content While your account exists
A deleted project Its files are removed within 7 days. Backups age out within 30 days
A deleted account Account, workspace, content and sign-in record are removed. Comments you made are kept without your name. Steps are in section 9
Sessions 30 days since last use, or until you log out
Server and app logs 30 days. They hold user ids, but no emails and no images
Backups 30 days
Export file link 7 days
Invoices, payment records, credit ledger As long as accounting and tax law require ([RETENTION_YEARS_ACCOUNTING] years). They are linked to an anonymised customer after you delete your account
Support mail 2 years after the last message, then deleted
Error reports (Sentry) 90 days
Link click data 13 months
Cookie-free statistics They hold no personal data, so we keep them as long as they are useful
Records of consent, if we ever ask for it As long as the consent applies, plus the time we need to prove it

5. Who gets your data

Service providers (processors). They work on our orders. subprocessors.md lists each one with its country, its task and the data it gets. The list is the one we keep up to date. In short: Hetzner (hosting and file storage), Bunny (delivery of public files, no user content), Stripe (payments), Auth0 (sign-in), Anthropic (assistant), Black Forest Labs (idea pictures), RunPod (processing of scans on GPUs in the EU), Sentry (error reports).

Our own servers. Email (mailcow), analytics (Umami), search, logs and dashboards run on servers we run ourselves, at Hetzner. No other company gets that data.

Other people in your workspace and people you share with. Team members see what their role allows. A share link shows what you chose to share to everyone who has the link.

Sign-in providers. If you sign in with Google, Apple or X, that company handles your sign-in under its own privacy policy, as a separate controller. They tell us your name and email.

Stores. When you press a buy link, you leave plintus. The store and its partner network get your visit under their own policies. We tell them nothing about you.

Authorities and advisers. We give data to courts, tax and other authorities when the law says so. We use lawyers, accountants and auditors, who are bound to secrecy.

A sale of the business. If another company takes over plintus, your data moves to it. We tell you first, and this policy keeps applying.

We do not sell your data and we do not share it for advertising.

6. Photos, video and AI

This is the part most people ask about, so here it is in one place.

  1. Where your photos go. You upload straight into our storage at Hetzner in the EU. Only you, and the people you share with, can open them. We create short-lived links to read them.
  2. What we remove. We remove location data (GPS) and other hidden data from photos on upload. We keep the picture itself.
  3. Room scans. Our scan software runs on GPUs in the EU. A GPU provider (RunPod) runs the job. It gets your photos or video for the length of the job and deletes them when the job ends.
  4. Idea pictures. We send your photo to an image service, Black Forest Labs, on its EU endpoint. It sends back the new pictures. Black Forest Labs is a German company.
  5. Pictures of your design. We make them with our own render and an image service.
  6. The assistant. To answer, the assistant needs your scene data (the list of items and sizes in your room) and small pictures of your room. We shrink them to at most 1568 px on the long side and remove their hidden data. We never send your raw uploads or your name and email. The service is Anthropic’s Claude. Anthropic runs it in the US or worldwide, not only in the EU. So this step leaves the EU. We rely on the EU standard contract clauses with Anthropic, or on the EU-US Data Privacy Framework if Anthropic takes part in it, and on a data processing agreement. If you need processing in the EU only, tell us: we plan a second route through Google Vertex AI in the EU region for such customers.
  7. No training. We do not use your photos, videos, rooms, designs or questions to train AI models. Our contracts with these vendors say they may not use your data to train models. If a vendor changes this, we stop sending it your data or we ask you first.
  8. No decisions about you. We do not make decisions about you by automated means that have legal or similarly large effects. The AI makes pictures and proposals for your room. It does not judge you, rank you or decide on your access, credit or price.
  9. Labels. AI-made pictures carry labels. See ai-labels.md.

7. Moves outside the EU

We keep data at rest in the EU. Some of our service providers, or their parent companies, are in the US. This is where data can leave the EU:

Provider What it gets Why How we protect it
Anthropic Scene data and small room pictures, when you use the assistant Answers from the assistant Standard contractual clauses or the EU-US Data Privacy Framework, data processing agreement, no training, no names or emails sent
Stripe Payment and billing details Payments Stripe Payments Europe in Ireland handles EU payments. Transfers to Stripe in the US use standard contractual clauses or the Data Privacy Framework
Auth0 (Okta) Name, email, sign-in details Sign-in. EU tenant Data stays in the EU tenant. Support access from the US, if any, uses standard contractual clauses or the Data Privacy Framework
Sentry Error reports. Emails and images are scrubbed Fix errors. EU region EU region. Standard contractual clauses or the Data Privacy Framework for US access
RunPod Photos or video during a scan Room scans. EU data centres Processing in EU data centres. Standard contractual clauses for the US parent company

If a provider uses other companies to do its work, they are listed in the provider’s own list, which we link to in subprocessors.md. You can ask us for a copy of the standard contractual clauses.

8. Cookies and similar tools

We use only the cookies that plintus needs to work, for example to keep you signed in. We use no advertising cookies and no tracking cookies, so there is no cookie banner. cookies.md lists each one.

9. Your rights

You have these rights under the GDPR:

  • Access. Ask what data we hold about you, and get a copy.
  • Correction. Ask us to fix wrong data.
  • Deletion. Ask us to delete your data.
  • Restriction. Ask us to pause the use of your data while we check a claim.
  • Portability. Get your data in a form a computer can read, and move it elsewhere.
  • Objection. Object to the use of your data that we base on our legitimate interest.
  • Withdraw consent. If we use your data by consent, you can withdraw it at any time. Past use stays lawful.
  • Complain. You can complain to a data protection authority. Ours is [SUPERVISORY_AUTHORITY]. You can also use the authority in the country where you live or work.

The two you need most are in settings.

  • Export my data. Settings, Privacy, Export. We email you a link to a zip file with your records in JSON and all your files. The link works for 7 days. We email you again when it is ready.
  • Delete my account. Settings, Privacy, Delete. We remove your Auth0 sign-in, your personal workspace and its files, and your memberships. We keep your comments without your name. We keep invoices, as accounting law asks, linked to an anonymised customer. We email you when it is done.

For anything else, write to privacy@plintus.ai. We answer within one month. If your question is hard, we may need two more months, and we tell you why. We may ask you to prove who you are. It is free, unless a request is clearly unfounded or excessive.

10. Security

Photos and rooms are stored on EU servers. Connections use encryption. We store files under hashes, and read them only through links that expire. Staff tools run only on a private network and need a second step to sign in. We log staff actions. We keep a plan for data breaches. If a breach puts you at risk, we tell you and the authority within the time the law sets.

11. Children

plintus is for people aged 18 and over. We do not knowingly collect data from children. If you think a child has given us data, write to privacy@plintus.ai and we delete it.

12. Changes

We may change this policy. We tell you by email and in the app at least 30 days before a change that matters starts. Old versions stay on this page.

13. Contact

[COMPANY_NAME], Krivių g. 5, 01204 Vilnius. Email: privacy@plintus.ai.

plintus opens soon

Leave your email. We write when you can try it with your room, and about nothing else.