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

Your privacy, in plain words.

Draft for owner and legal review, prepared 18 November 2026. Not an approved policy. The legal operator name, address, verified privacy contact, applicable jurisdictions, age eligibility and lawful processing grounds must be established before launch.

What is processed

Device registration uses a random device identifier and platform details. An account may include an email and display name. Manual scans process the link, message or APK you choose to submit. Scan records contain results, reasons, timestamps and redacted targets. Message content is not retained by default. Never submit passwords, financial credentials or another person’s private information without authority.

VPN and DNS

The Android local VPN processes domain lookups routed to its virtual DNS resolver. It checks a local signed list and forwards allowed lookups to the operator’s authenticated encrypted DNS endpoint. The operator’s resolver and authoritative DNS providers may process the requested domains. DNS filtering does not read HTTPS page content or encrypted chats. Blocking events remain local unless sharing is explicitly enabled.

Purposes and access

Data supports requested scans, account/session operation, abuse prevention, support and reviewed threat intelligence. Privileged staff access is limited by roles and audited. A report does not automatically become a public allegation or threat-list entry. Reports must not contain private messages or personal data unnecessary for review.

Storage and retention

The intended default application retention window is 30 days for scans and transient reports, subject to the implemented retention job and a documented, reviewed exceptions schedule. APK uploads should be removed after analysis. Required incident records, legal holds, audit logs and backups may follow separate periods established before launch. The operator must publish exact periods and verify deletion in backups. No blanket legal-compliance claim is made.

Third parties and international processing

The design uses self-hosted detection and no external AI or threat lookup API by default. Existing Cloudflare DNS/proxy and the VPS host can process routing metadata or traffic according to actual deployment. No advertising or analytics SDK is configured. The operator must identify hosting locations, subprocessors and any cross-border processing before release.

Your controls

You choose what to submit, whether message content may be stored, whether events are shared, and when DNS protection runs. You can view and delete local history and request account deletion through the app or authenticated web flow. Review the data policy for client storage. Access, correction, grievance and deletion procedures require an approved operator contact.

Security and limitations

Transport encryption, scoped access, token rotation and restricted file analysis reduce risk. No system is perfectly secure or detects every scam. Security claims are subject to independent validation.

Before public release

Complete the operator details, publish a verified grievance/privacy contact, verify lawful processing and consent requirements under applicable Indian law, review children’s data handling, document breach response and approve this policy. The app is not ready for unrestricted public onboarding until these tasks are completed.