Privacy

The public checker needs no account or file upload. A separate invitation-only workspace pilot saves decisions and review history when its users explicitly choose to do so. No paid subscription is active.

What the checker stores

Your answers are stored in your browser’s local storage so you can resume a check.
Client-policy owner/version and provenance or policy evidence references, if supplied, are part of the structured answers and downloaded Evidence envelope. Use internal identifiers, not confidential document text or secrets.
The public API evaluates the structured context in memory and returns the result. It does not persist public checker contexts or downloaded Evidence envelopes. If you explicitly save a result in a private workspace, that copy is stored as described below.
“Download evidence” and “Email me this result” work entirely on your device (a mailto: link opens your own email app).

Private workspace pilot

The controller is Bartosz Kowalczyk, ul. Gieysztora 4/161, 02-999 Warszawa, Poland. Contact: privacy@disclara.eu.

Only invited users can create accounts. We retain their email address, password hash, account/role identifiers, hashed session and one-time tokens, invitations and security timestamps. Authenticator secrets are encrypted; setup and sign-in events are recorded. Email recovery is available only when the approved OVH SMTP connection is configured; identity-checked administrator recovery remains available.
When users explicitly save work, we retain client-space names, structured checker answers/results, asset/version identifiers and optional hashes, client-policy revisions, reviewer schedules, decisions, notes, notifications and timestamps. Manual publication observations additionally retain a post URL/ID, surface/region/variant, observed labels, evidence reference or optional hash, account attribution and timestamps. Disclara does not fetch the post or upload screenshot bytes in this workflow. We do not receive or store the creative file. Saved evidence can be exported as JSON or printed to PDF.
We use these records to operate the requested pilot, control access by client space and preserve a review trail. Do not enter confidential source documents, unnecessary personal data or secrets in free-text fields.
When a pilot ends, access is disabled and sessions are revoked. Live pilot records are deleted by day 83; backup copies expire within the following seven days, so the maximum is 90 days after the pilot ends. There is no automatic deletion date while the pilot remains active.
Technical hosting, backups and security logs protect the service. Encrypted offsite backups use an existing Hetzner volume; decryption keys are not stored there. The approved email provider is OVH, with contact@disclara.eu as sender. Email includes access links or an action notice, not complete checker answers. Queued access-link payloads are encrypted and expire; SMTP acceptance is not proof of inbox delivery. Access is limited to authorized operators. We do not sell workspace data.

You may request access, correction, deletion or information about your data at the address above. You may also complain to the Polish supervisory authority (UODO). The pilot operator must confirm the legal basis and any processor/transfer disclosures before inviting external client users.

Analytics

Events and server logs use only schema dimensions: workflow role, provider system-timing classification, provider/deployer decision state, AI-use stage and materiality outcome (not the written rationale), publication workflow, exact/platform-only capability match and fallback state, content type, jurisdiction, result state, component count, ruleset/evaluator version, status codes, latency and a request ID.
Guide-to-checker and guide-to-image-preflight clicks, plus image-preflight start and completion, are recorded as aggregate-oriented server events with page path, platform, scenario and categorical result state where applicable. They use no analytics cookie or cross-session identifier.
Feedback sends only the selected category and the one-way context hash.
No raw asset content, prompts, pasted text or file contents are ever sent.
The server uses the connection IP transiently for rate limiting; it is not an analytics dimension.

Contact

Privacy questions: privacy@disclara.eu