Privacy Policy

Quoyle collects nothing. This is not a legal hedge or a qualified claim. It is an architectural fact. The application does not declare the android.permission.INTERNET permission. The Android operating system enforces this at the kernel level. Quoyle cannot make network requests. There is no server. There is no endpoint. There is no path for data to leave your device unless you explicitly initiate it.

No accounts. No email addresses. No usernames. No passwords. No user profiles of any kind. There is no registration flow because there is nothing to register with.

No analytics. No Firebase. No crash reporting SDKs. No usage telemetry. No event tracking. No session recording. No A/B testing frameworks. The application has no mechanism to observe, measure, or report your behavior.

No advertising. No ad SDKs. No ad network integrations. No sponsored content. No affiliate tracking. No monetization of attention.

No third-party SDKs that phone home. The complete dependency chain is AndroidX, Jetpack Compose, Room, and Hilt — all first-party Google libraries that execute locally on your device.

The accessibility service is optional. When enabled, it reads the browser’s address bar and page title in real time to assemble bibliographic metadata for your quotations. This data is written directly to a local Room database on your device. It is never transmitted, cached remotely, or shared with any external process.

Your data leaves your device only through actions you explicitly initiate: exporting to a JSON file, sharing a quotation via the Android share sheet, printing a quotation card, or copying text to the system clipboard. There is no other path. No silent sync. No background upload. No telemetry sideband.

Encrypted at rest. Your quotation database is encrypted with AES-256 via SQLCipher, keyed through Android’s hardware-backed Keystore. The encryption key never leaves the secure hardware on your device. If your device backup is uploaded to a cloud service, the database file is an opaque, unreadable blob. When you export your library, you can optionally protect the file with a passphrase (PBKDF2-derived AES-256-GCM). Without the passphrase, the export is unreadable. The passphrase is never stored.

This page follows the same principle. No tracking scripts. No cookies. No external analytics. No third-party requests beyond locally-hosted fonts. View source to verify.
Effective: February 2026 /// Faveat Software Foundry