Privacy Policy

1. Who we are

SnagSpy is operated by AFRICAN LEGACY GROUPE SARL, registered at Cocody 2 Plateaux, lot 1248, îlot 128, Abidjan, Côte d’Ivoire (RCCM CI-ABJ-03-2025-B13-00716).

For anything in this policy, including any request about your own personal data, write to [email protected].

2. We act in two different roles, and they are not the same

This distinction decides what we may and may not do with data, so it comes before everything else.

For the telemetry our customers send us — error reports, log lines, trace spans, session recordings — we are a processor. The customer decides what their application transmits and why; we act on their instructions and nothing else. If you are an end user of an application that uses SnagSpy, we are not the organisation that decided to collect your data, and requests about it are answered through that organisation rather than by us. We will help them answer you.

For our own account data — the address you signed up with, your organisation’s name, our audit log, our billing records — we are a controller, and this policy is our own. Requests about that data come straight to us.

3. What we collect about you as a customer

Your email address and your organisation’s name, because an account cannot exist without them.

Your IP address and the time of each sign-in, recorded in an audit log. That log exists so that an owner can see who reached their data and from where, which is a security control rather than an analytics one.

Records of what you were billed and what you used, if you are on a paid plan.

We do not build a profile of you, we do not track you across other websites, and we do not sell or rent any of it.

4. What we process on our customers’ behalf

Application telemetry: exception types and messages, stack traces, log lines, trace spans, and — where a customer switches it on — session recordings.

None of this is designed to contain personal data, and in practice some of it does. A stack trace can carry an email address that was in a variable; a log line can carry whatever the application logged. We say this plainly because the alternative is a policy that claims a cleanliness no error-monitoring product has.

Two controls sit in front of it. Anything credential-shaped is removed on arrival by a server-side scrubber, before it is stored, and it is deliberately biased towards removing too much. Session replay is off unless a customer turns it on for a specific project, and recordings are masked in the browser before they are transmitted, so the masked content never reaches us at all.

Neither control is a guarantee, and we do not offer one. A customer chooses what their software sends, and our Terms require them not to send special-category data or credentials deliberately.

Customers may also supply a reference identifying the end user affected by an error, so that "how many people did this break" can be answered. If that reference itself looks like a credential, we store an irreversible hash of it rather than the value.

5. Cookies and anything else stored on your device

If you are reading the public website and have not signed in, nothing is stored on your device. No cookies, no local storage, nothing. Nor is any third party contacted when the page loads: there are no analytics, no advertising, no external fonts and no third-party scripts, so no other company learns that you visited.

This is why you have not been asked to accept anything. Consent is required for storage that is not strictly necessary, and there is none to consent to.

When you sign in, we set one cookie, named slk_session. It holds your session and nothing else. It is marked HttpOnly so that scripts cannot read it, Secure so that it is only ever sent over HTTPS, and SameSite=Lax. It expires when your session does, and signing out deletes it. It is strictly necessary — you cannot be signed in without it — so it does not require consent.

The dashboard also remembers three interface preferences in your browser’s local storage: which project you last had open, whether you chose the dark theme, and whether the navigation is collapsed. They are set only because you performed the action that sets them, they never leave your browser, and they are not used to identify or track you. Clearing your browser’s site data removes them.

Signing in also leaves one marker in local storage recording that this browser has a session, so the public pages can offer your dashboard instead of a sign-in link. It holds no identity and grants no access — the session cookie above is the only thing that does — and the public pages read it without writing anything. Signing out removes it, and so does clearing your browser’s site data.

Our CDN, Cloudflare, adds network error-reporting headers to responses as part of operating the connection. These do not store anything on your device for our purposes and are not used to identify you.

6. Why we are allowed to process it

For running your account and providing the service you asked for: performance of our contract with you.

For keeping the platform secure and available, and for the audit log: our legitimate interests in operating a service that customers can trust, balanced against your interests — which is why the audit log records what was done rather than building any profile of you.

For customer telemetry: we act on our customer’s instructions. The lawful basis for that data is theirs to establish, not ours.

Where we ever rely on consent, we will ask for it plainly and you will be able to withdraw it as easily as you gave it.

7. How long we keep it

Retention is enforced by the platform on a schedule, not applied by hand on request.

Errors and events are kept for the period your plan provides: seven days on the free plan, thirty on Team, ninety on Business and Enterprise. Trace spans are kept for up to thirty days, log lines up to fourteen, and session recordings seven. An organisation may shorten any of these; none can be lengthened beyond the platform ceiling.

Uploaded source maps are kept longer than the errors that reference them, because a source map that expires first leaves recent errors unreadable.

The audit log is not customer-configurable, because a security record an account holder can shorten is not a security record.

Account data is kept while the account exists. When an organisation is deleted, its data is removed.

8. Where it is, and who else touches it

Your telemetry is stored in Germany, inside the European Union, on infrastructure operated by Hetzner. The nightly backup of it is held by Cloudflare R2 in a bucket restricted to the European Union — which guarantees the Union rather than any one member state, so that copy may rest outside Germany while the live data does not.

Cloudflare provides the connection into that infrastructure and terminates TLS, so data passes through its network in transit.

If, and only if, an organisation enables AI root-cause analysis, a deliberately minimised part of a single issue — the exception type, its message, the stack trace, the culprit and some counts — is sent to Anthropic in the United States. Never end-user identifiers, never whole events, never the raw attribute bag. Any organisation may decline this, and the feature does nothing at all unless the deployment has been configured with a key for it.

If, and only if, an organisation separately enables code review, the code changes its own build pipeline sends us are passed to the same provider, in the United States, to be reviewed. This is a second permission and it starts switched off: agreeing to send a stack trace is not agreeing to send source code, and turning off AI processing turns this off with it. We do not read your repositories — we hold no credential that could — and we review only what your pipeline sends. Those changes are not stored: they are used to produce the review and then discarded.

The current list — what each party receives, where it is, and whether you can decline it — is published at /en/subprocessors. We publish a change there before a new sub-processor begins processing, not after.

Transfers outside the European Union rely on the safeguards the law requires for the destination, and we will name the mechanism on request.

9. Your rights

Depending on where you live, you may ask for a copy of your personal data, ask us to correct it, ask us to delete it, object to processing based on legitimate interests, ask us to restrict it, or ask for it in a portable form.

Write to [email protected]. We will answer within one month, and tell you before that if the request is complex enough to need longer.

If you are an end user of an application that uses SnagSpy rather than our customer, please contact that organisation. They decide what is collected and we act on their instructions. If you contact us instead, we will pass the request to them and tell you that we have.

You may complain to a supervisory authority. In Côte d’Ivoire that is the national data-protection authority; in the European Union it is the authority where you live or work.

10. How it is protected

Passwords are stored hashed with Argon2 and are never recoverable. Access to the dashboard is scoped by role. The database and object storage are not reachable from the public internet: the only inbound path is through the CDN tunnel.

Credential-shaped values are removed from telemetry before storage, and again from the operational alerts our own systems send us.

More about how the platform is protected, and how to report a flaw you find, is on our security page at /en/security.

If a breach affects your personal data we will tell the relevant authority within the time the law requires, and tell you directly where the risk to you is high.

11. Children

SnagSpy is a tool for building and operating software and is not directed at children. We do not knowingly collect data from anyone under 16. If you believe a child has given us personal data, write to us and we will remove it.

12. Changes

When this policy changes we will update the date at the top. If a change materially affects your rights we will tell account owners directly rather than relying on you to re-read the page.

If the company operating SnagSpy changes — through a reorganisation or a transfer of the business — the controller of your account data changes with it. We will name the new operator and tell account owners before that takes effect, not after. Your rights, and the retention periods above, travel with the data.