SECURITY
What the code does to keep a client's data theirs, in sentences you can check. No borrowed certifications, no vendor list, and every sentence names something the code actually does.
Every request to the API resolves the workspace from your membership, not from anything the browser sends. One client's data is never read from another client's workspace, and the rule lives in the API, where the interface cannot skip it.
Owner, member, client. A client seat can see the campaigns, the Library, the reports and the performance, and can change nothing. The refusal happens in the API, not only in the interface, so a hidden button is never the only guard.
A new route requires sign-in automatically. The public ones are listed in one place with their reason, and a test fails if any route is left unclassified, so a route cannot fall open by accident.
Every table that holds customer data carries row-level policies, so the API's checks are not the only fence. The database's privileged key is used on the server only and never enters the code sent to the browser.
Sharing a report again revokes the previous link. Revoking is one action from the report itself, and the old link stops working at that moment.
Levrit is served over HTTPS only. The response headers forbid other sites from framing a Levrit page, trim the referrer sent outward, and switch off browser permissions nothing here uses: camera, microphone, location, payment.
The contact form, invitations and the other public endpoints carry a per-address request limit, so a token cannot be guessed at volume. The limit is in the code, not a promise.
Campaign drafts and generated visuals are kept in your browser, and synced to Levrit's storage only so your work can follow you to another device. Clearing site data for levrit.io removes the local copy.
If you connect an ad account or a social account, disconnecting it in Levrit deletes the access token and the data that connection imported. With no connection, Levrit holds no data from that platform about you.
The Account page has a deletion request button; one email from your account address works too. We delete the account, its campaigns, assets and stored visuals, and tell you when it is done. The window is written on the data deletion page. Invoices that Indonesian tax law says to keep are kept for that period only.
Levrit has not been audited by a third party and wears no certification badge. This page names what the code does, and every sentence is tested each time the code changes. If an audit happens, its name goes here afterwards, not before.