The answers your privacy questionnaire asks for
Where customer support data is stored, how it is separated and who can read it. Verifiable facts inside the product, with the name of the feature that implements each one.
There is no GDPR badge that replaces the data controller’s responsibilities. Here you will find concrete tools for notices and consent, exporting or erasing a person’s data and reconstructing operations. This page does not claim certifications OglutTicket does not hold.
No passwords
There is no password selection screen anywhere in the product. People sign in with email and a six-digit code. There is no password database to breach and no shared password left with a former employee.
One person’s data
Permanent erasure and export of one customer’s data are product features with a dedicated permission. You do not send a request to the supplier and wait.
Action log
Every operation is recorded and cannot be edited. A request conversation has no anonymous events: every message, assignment and status change is dated and attributed.
Versioned legal documents
The privacy notice, cookie policy and terms have a version and effective date. Registration consent is stored as evidence together with the version accepted.
Separated workspaces
Each organisation has its own address and data. Separation is not a naming convention: every database query is bound to the workspace receiving the request, and an unknown address is rejected rather than ever receiving another organisation’s data. This applies to requests, attachments and the action log.
Attachments are not publicly reachable
Storage cannot be read from a public address. Every file passes through the application, which checks who is requesting it and which ticket it belongs to before serving it — including browser previews.
The privacy notice is yours
Each organisation places its own privacy notice on its public form: it is the data controller for its customers, not us.
Data is stored in Europe on AWS
The infrastructure runs on Amazon Web Services in the Frankfurt European region. The database, attachments and email delivery service are hosted there. Traffic to the portal is encrypted in transit.
Workspace isolation is the property we test most insistently because it must never fail. Eight automated tests try to reach another organisation’s data — reading a request, assigning it to a person who does not exist there, or reusing a session cookie at another address — and must be rejected every time.
Nine more tests verify something often overlooked: a rejected operation must not have written anyway. Each test requires both the rejection and an unchanged database value, because a rejection that has already modified data is both the worst and hardest defect to see.
Your customer conversations leave this system only if you choose. Artificial intelligence starts off; while it remains off, no messages or attachments are sent to any model, ours or a third party’s. If you enable it, you choose the model — Claude, ChatGPT, Gemini or Grok — and submitted text is sent to that provider, named as a processor in the data agreement and listed as a recipient in the notice. Even then, AI suggests rather than decides: triage, reply drafts and summaries. A person still answers your customer.