Trakis

Trakis

Data processing terms

For an agency or a business that audits its clients’ sites with Trakis: what we process on your behalf, and the promises article 28 of the GDPR asks a processor to make.

Last changed 17 November 2026.

Who is who

When your account audits a client’s site, connects a client’s Search Console or App Store data, or shares a report with a client, you decide why and how that data is used: you are the controller, or the processor of your client. Razvan Luca, who runs Trakis, then processes it on your behalf, as your processor or sub-processor. These terms are part of the terms of service for every such account, with no signature needed; a signed copy is sent on request to hello@trakis.io.

For your own account — who you are, how you sign in — Trakis is the controller, and the privacy page applies instead.

What is processed

  • Subject and purpose: auditing the sites you add, ordering their fixes, monitoring them, and the reports you share.
  • Duration: as long as the site or the connection is in your account; then deleted (below).
  • Data: what the sites’ public pages show, kept as addresses, titles, headings, links and short evidence; Search Console search analytics (queries, pages, clicks, impressions, positions); Bing Webmaster Tools search data (queries, clicks, impressions, positions) and the keyword look-ups made with it; App Store listing and keyword data; the names, logos and contacts you put on reports.
  • People concerned: anyone a client’s public pages or search queries happen to name; the contacts on your reports. Trakis looks for none of them.

What we promise

  • Your instructions. We process the data only to provide the service as you use it — your use of the account is the instruction — unless the law requires otherwise, and then we tell you first unless the law forbids it.
  • Confidentiality. Only Razvan Luca has access, bound to keep it confidential. The founder’s read-only view of an account never shows Search Console or Bing Webmaster Tools data.
  • Security. Encryption in transit; Search Console, Bing Webmaster Tools, App Store and AI keys stored encrypted; accounts kept apart in the database by row-level security; passwords and access tokens stored only as hashes; the database in the EU.
  • Other processors. You authorise the services listed on the privacy page. Before adding or replacing one, we update that list and email signed-in accounts at least 30 days ahead; if you object, you can delete the data or the account before it applies. Each is bound by data processing terms that protect the data at least as well as these.
  • AI providers. An AI provider is sent anything only with a key you add in the settings, under your own agreement with that provider: it is your choice of service, not one of ours. What is sent is on the privacy page.
  • Outside the EU. Transfers rest on the EU–US Data Privacy Framework or on standard contractual clauses, as the privacy page says.
  • People’s rights. We help you answer a request from a person whose data is involved: we can find, export or delete what we hold about them.
  • Breaches. We tell you without undue delay, and within 48 hours of learning of one, what happened, what data, and what we did, so you can meet your own 72 hours.
  • Help with your duties. We give you what you need for a data protection impact assessment or a question from an authority, about our part.
  • The end. Delete a site, a connection or the account, and the data goes at once; database copies kept for recovery replace it within 30 days.
  • Proof. We answer your questions about how the data is handled, in writing, and show you the record we keep of this processing.

What we do for ourselves

Trakis tunes how its audit weighs problems from the findings of saved audits — which checks fail, how often — never from Search Console data and never per person. For that use alone Trakis is the controller, as the privacy page says.