IN DEVELOPMENT Thoughtful protection. Transparent by design. Meet Veyrak ↗
veyrak.
Check a link ↗
VE Y R A K / DATA & RETENTION DRAFT

Less data. Clearer choices.

Draft. Retention and backup periods require owner/legal approval and operational verification before public launch.

Website storage

The website remembers only your theme preference in local storage. Scan access tokens stay in browser memory and are lost on refresh. It requests a temporary guest account when you submit a scan. No advertising cookies, tracking pixels or remote web fonts are configured. Administrator sessions use necessary session and CSRF cookies.

Manual scans

Links, messages and APKs are transmitted to the self-hosted API when you request a scan. Remove sensitive information first. URL queries and fragments should be removed from stored history. Full message storage is off by default; the message still needs transient processing for the requested analysis.

History and reports

Default scan retention is 30 days, enforced by a scheduled task when operational. Local Android history can be cleared separately. Submitted reports require moderation and must not contain unnecessary personal information. Audit and security records can require a distinct retention schedule.

Backups and deletion

Account deletion removes or anonymises linked application data according to the implemented deletion flow. Encrypted backups have a separate rolling expiry, and a deletion ledger must prevent restoration of deleted accounts. Backup encryption, expiry, restoration and deletion reconciliation need verification before launch.

External services

No paid AI, analytics SDK or external threat lookup service is enabled by default. Hosting, Cloudflare routing and DNS resolution have their own metadata-processing implications. See the privacy draft for required disclosures.