A report contains your client’s spend, their results and often their strategy. Emailing it as an attachment means it now lives in an unknown number of inboxes, forever, with no way to correct or withdraw it. Sharing it as a link is better only if the link is controlled. This is how Screebl handles it, and how to explain it to a client’s security team.
The parts, and what each one protects against
A published link. A report is only reachable when you publish it. Drafts have no public address. Unpublishing removes the page; the link stops working immediately, which is something a PDF can never do.
A per-client access key. Each client can have an access key, set by the agency. When it is on, the shared link shows the report’s name and nothing else until the key is entered. A forwarded link, a link in a screenshot, a link in an old email thread: none of them reveal data without the key. You can rotate the key at any time from the client’s profile, and every existing link asks for the new one.
The client portal. Clients who log in see their own reports only. A client at agency A cannot see a report from agency B, and a client cannot see another client’s report at the same agency. Client accounts can read and export; they cannot edit or create.
Exports. PDF, Excel and CSV exports reproduce what the client sees, without the agency’s editing controls. Exports are generated when asked for; nothing is stored on the client’s device by the page itself.
The report assistant. When an agency enables the assistant on a campaign, it answers questions from that one report. It has the same gate as the report: no access key, no answers. It cannot reach other reports, other campaigns or anything outside the page it lives on.
Who can see what
| Role | Sees | Can do |
|---|---|---|
| Agency owner / admin | All reports of the agency | Create, edit, publish, unpublish, set access keys |
| Agency employee | Reports of the agency | Create, edit, publish |
| Client | Their own published reports | Read, export, ask the assistant |
| Anyone with a link | The report name, then the report after the access key | Read, export |
Roles are enforced on the server for every request, not only hidden in the interface.
Where the data lives
Clients’ security teams ask three questions: where, who, and how long.
- Where: application servers and file storage in the EU (Stockholm and Frankfurt regions), a managed database, and authentication by a managed identity provider.
- Who: the sub-processors are listed on our privacy page by name: cloud hosting, database, authentication, email delivery, the AI model provider used by the optional assistant, DNS, and maps. No advertising trackers anywhere, and no analytics of any kind on shared reports or the client portal.
- How long: for as long as the agency keeps the report. Deleting a report removes its data; deletion requests go through support.
We keep this list current on the privacy page because a questionnaire that is answered from memory is answered wrong.
Practical habits for account managers
- Set the access key when you create the client, not when someone asks. It is one field.
- Send the key separately from the link. A message with both is one message.
- Unpublish reports you would not want forwarded, such as pitch material for a lost account.
- Use client branding carefully. If the report will be presented as the client’s own, make sure their logo is the version they approved.
- Rotate the key when a contact leaves the client. Thirty seconds, and the old link in their inbox goes dark.
What we deliberately do not do
- We do not put report data into URLs. The address of a report is a short identifier, nothing more.
- We do not send the report contents by email. Emails carry the link.
- We do not track clients across the web. There are no advertising pixels on reports or on the marketing site.
- We do not let the assistant see anything but the report it lives on.
The one-paragraph answer for the questionnaire
“Reports are shared as links that are only active while published. Each client link can be protected by a per-client access key that the agency sets and can rotate. Clients can also log into a portal that shows only their own reports. All access is checked on the server per request. Data is processed in EU regions by the sub-processors listed on the provider’s privacy page, and nothing tracks the people who open a shared report or the client portal.”
That paragraph has closed most of the security conversations our customers have had. If a client needs more, our support address is on every page.
