Skip to content
News

Security and privacy: our commitment

How your conversations are stored, who can access them, and the choices we made so that trust is not just a promise.

The GPTPro Team4 min read
Share:
A GPTPro data-centre aisle lined with server racks

You send us your drafts, your ideas and sometimes your customers' data. That deserves a plain answer about what happens to it, rather than a paragraph of reassurance. Here is how GPTPro is built.

1. Your conversations belong to you

Your conversations are yours: you can consult, export and delete them at any time. Deleting a conversation deletes its messages and its attachments — not just its title in your history.

2. Access is scoped, not implied

Every request is checked against the account that made it. There is no shared bucket, no publicly guessable URL for an attachment, and no internal shortcut that lets one account read another's history.

3. Encrypted in transit and at rest

Traffic between your browser and our servers is encrypted end to end, and stored files are encrypted at rest. Generated images and attachments are served through signed, short-lived links rather than public addresses.

4. European hosting, GDPR by design

Our infrastructure is hosted in Europe and operated under the GDPR: a documented legal basis, a defined retention period, and the right to access, correct and delete your data from your account settings.

5. Shared conversations are opt-in

A conversation only becomes reachable by a link when you create that link yourself, and it stays behind an unguessable token. Nothing is indexed and nothing is public by default.

Conclusion

Security is not a feature we ship once — it is a set of constraints we design against. If you have a question about a specific point, our team would rather answer it than have you guess.

About the author

Every week the GPTPro editorial team shares analyses, guides and news about artificial intelligence and its uses.

See all articles

Related articles

See all articles