Trust

Where your data lives and who touches it

Every statement on this page describes something that exists in the system. What we do not have, we say at the end.

Path of a piece of data

Path of a piece of dataThree bands, top to bottom: your browser, the Renka server where the application and the database live, and an external artificial intelligence provider. A token goes down and back up across all three. Between your browser and the server there is a gate: Roko does not change your data unless you confirm.Your browserYou type and confirm hereRenka serverApplication and database.Data separated by company.Content is processed here.External AI providerReceives what it needs to answer.We do not name it publicly.Roko changes nothing without your confirmation
Where it is stored
The application and the PostgreSQL database run on a server contracted by Renka, not inside another platform's account. Some supporting providers (hosting, email, artificial intelligence) are outside Colombia, and the privacy policy says so.
Isolation between companies
Each work record carries its company's identifier, and the database applies row-level security: a person only reads and writes the data of the companies they belong to. The rule lives in the database, not only on screen.
Inside a company, the application limits what each member can see and change in the money and management modules according to their role.
Roko changes nothing unless you confirm
When Roko proposes an action that modifies data, it stays as a pending proposal. Only the person who received it runs it, by confirming, and the proposal is kept with its status and date. Platform users can see those actions in their trust panel.
Who else can access: support leaves a trace
The Renka team only enters a client company with an open support session. Every visit and every data change is kept in a record the company can read (owners and administrators) and that the database does not allow to be edited or deleted. That record stores which table and columns were touched, not the content of the values.
Audit trail
The facts someone may need to reconstruct (archiving, restoring, deleting, an AI provider failing and the switch to another) are written to an append-only record: the database rejects editing or deleting its rows. Inside the platform you can compute a record's fingerprint and compare it with one you noted earlier.
How long it is kept
Website chat conversations that do not become a qualified inquiry and are not handled by a person are deleted automatically after 30 days without activity. Other data is kept while the commercial relationship lasts. The detail and your rights of access, correction and deletion are in the privacy policy.
Artificial intelligence: what happens to content
Roko processes content on our server and sends an external artificial intelligence provider what is needed to produce the answer. That is why we do not claim end-to-end encryption: the server sees the content in order to work with it.
We do not publish the names of AI providers. If one fails, the system switches to another and leaves a note in the trail.

What this page does not say

  • We do not claim end-to-end encryption.
  • We do not invoke third-party security certifications.
  • The audit record has no hash chain or external timestamp: the fingerprint is for comparing against one you noted, not for proving on its own that nobody touched it earlier.
  • We promise nothing about what an external provider does with content outside our server.

If you already use the platform, the trust panel shows what Roko did with your data and lets you verify records. Open the trust panel

Trust: where your data lives and who touches it · Renka Consulting