This page explains, in practical terms, what Systeme Growth handles when you use the audit product. It describes the implemented service reviewed on 17 September 2026. It is not a guarantee that security incidents are impossible and it does not replace rights or obligations that apply under relevant law.
Data used to run an audit
When you submit a public page, the service validates the URL and creates an audit. It stores normalized capture and display forms of the URL, a derived cache key, the audit context you choose, timestamps, status, version information, and bounded page observations needed to produce the report. Raw input is not kept after validation. Display URLs redact selected sensitive query values, but the page address itself remains part of the audit record.
A page address can itself contain personal information or secrets, especially in query parameters. Automatic redaction cannot safely promise to recognize every sensitive value. Do not submit private pages, authenticated links, password-reset links, or URLs containing information you would not want included in an audit record.
The browser worker loads the authorized public page and may store desktop and mobile screenshots, page excerpts that pass the product’s suppression rules, findings, and readiness contributions. Screenshots can contain information visibly rendered on the submitted page. Capture is suppressed when the page contains a detected sensitive form. Result access uses a high-entropy capability token; anyone who has a valid result link may be able to open that result until it expires.
Systeme Growth audits public content. It does not attempt to sign in, bypass a paywall, or enter a private Systeme.io workspace. The private result link should still be treated like a password while the report remains available.
Retention and access
Audit evidence has a configurable retention period. The current application default is seven days after the audit reaches a terminal state. Screenshots use private object storage in the production design, with time-limited signed access created only after a valid result capability is presented. Cleanup is designed to delete artifacts before final database expiry; failures remain pending for retry rather than being reported as complete deletion.
Some bounded, non-content operational records can outlive screenshot evidence where the accepted architecture says so. For example, suppression digests exist to prevent future email sends, and bounded result-email events have their own retention rule. This draft does not claim that every record shares one deletion date.
Feedback, beta requests, and report email
The result page can record audit-level usefulness feedback and a selected intended action. The implemented feedback flow does not include a free-text field. A Pixel beta request can store an email address together with the versioned consent text and audit access record. Submitting that form is an intent signal; the current design does not by itself prove that the submitter owns the address.
If you request the full report by email, Systeme Growth stores the address and consent record, unlocks eligible report content in that browser, and queues the approved result-email sequence. Resend delivers those messages. The address remains tied to the audit lifecycle. A separate keyed digest can be retained for unsubscribe, bounce, or complaint suppression without retaining the address in that suppression table. The browser unlock uses an HttpOnly cookie scoped to the relevant audit grant.
Service providers
The production service uses PostgreSQL for application records, Cloudflare R2 for private screenshots, and Resend to deliver result emails. Resend receives the information needed to deliver those messages. The application remains responsible for consent records, scheduling, unsubscribe suppression, and the audit lifecycle.
Each provider receives information needed for its role. Systeme Growth does not claim that all data stays with one provider, in one database, or under one retention rule. Provider arrangements and production data flows must remain consistent with this page before a material change is released.
The Growth Pixel is a future measurement capability. The current Pixel beta form is a request to be contacted; this draft does not say that a tracking pixel is installed on a submitted page. Provider analytics, new tracking, or new external writes require their own authorization and privacy review.
Deleting your personal data
You can ask Systeme Growth to delete the personal data associated with your email address from the Delete my personal data page. The service sends a one-time verification link to that address; the link works once and expires after 30 minutes. Nothing is deleted until you confirm it.
When you confirm, you receive one processing receipt by email that states your address was verified and deletion is being processed. It carries an opaque reference and no personal data. Deletion then removes your address, any report-email request and its follow-up messages, any Pixel beta request, and the consent records tied to that address. The page where you confirmed shows when deletion has completed; because the address is removed in the same step, no completion email can follow.
What remains is deliberately minimal: an opaque, random deletion receipt that resolves to nothing, and a keyed digest that records the do-not-contact decision so no automated message is sent to that address again. Audit reports contain no personal data beyond the address and follow their own retention period. After deletion, you can hear from Systeme Growth again only by opting in afresh; an earlier consent is never restored.
Security and choices
The application includes URL admission controls, private-network blocking, browser request controls, bounded request handling, log redaction, and token-gated result access. These controls reduce specific risks but do not justify a promise that the service is perfectly secure.
Do not submit a page address containing secrets or personal information. Keep result links private. If you submit an email form, use the unsubscribe option in messages where available. Questions about privacy can be sent to updates@systemegrowth.com.
- Ask a question about information associated with your email.
- Request correction or deletion where the service can identify the relevant record and the request applies.
- Unsubscribe from result-email follow-up using the message link.
- Avoid submitting a private URL or a public URL containing secret parameters.
- Report a privacy or security concern to updates@systemegrowth.com.
This page will be updated when the product’s actual data flows, providers, retention rules, or customer choices materially change.