qrst

QRST privacy policy

Updated November 7, 2026. This policy describes QRST Mail and QChat accounts at qrst.xyz and QRST for Android, including QChat inside QRST. The combined Android app 0.4.0 uses the same QRST account and history as the web app. This policy also covers earlier QRST Mail and QChat apps. Available features vary by app and version. Contact QRST at caspianstrike@gmail.com for privacy, support or account deletion.

Information we process

To recover interrupted email sends, QRST temporarily stores the normalized send content and attachment references until your mailbox copy is saved. Uncertain provider outcomes are held for review rather than automatically resent. Signed hard-bounce and complaint events can create delivery holds; we retain hashed recipient addresses and event references to prevent repeated unwanted delivery, without storing the message body in that list.

Supported Android updates can keep pending direct text messages encrypted on your device so an interrupted send can be retried with the same message reference. Pending text can survive an app restart until QRST accepts it, you remove it, or you sign out. Automatic retries stop after 12 attempts or 24 hours and require your review; this does not automatically delete the pending text. This local queue is excluded from operating-system and cloud backup. It is not end-to-end encryption. Version 0.4.4 holds loaded conversation history in memory rather than a persistent offline archive.

In supported later Android versions, an optional recent-history cache is off by default and can be enabled separately for each account on a device. It stores encrypted text and message metadata for up to five direct conversations, 50 recent messages per conversation and 1 MB in total, excluding media bytes. Entries older than seven days are not shown and are cleaned up when accessed. Normal server authentication is required when the app starts. Cached history may then be shown after a connection failure and can be out of date; reconnect to refresh edits and deletions. Disabling the option, signing out, receiving a session-revoked response, or requesting account deletion clears the cache and its saved choice. Local encryption is not end-to-end encryption.

In supported Android versions, a separate optional mail cache is off by default. After a successful mailbox refresh, enabling it saves up to 50 recent messages on this device, including sender and recipient details, cc, subject, date, status and message bodies up to 8,000 characters. Attachments are not saved. The copy is encrypted with an Android Keystore key and expires after seven days. If a mail network request fails, the app may show this saved copy, which may be out of date; actions that change mail require a connection. Turning off the option, signing out, ending or revoking the session, or requesting account deletion clears the cache and its saved choice. Device-side encryption is not end-to-end encryption.

Optional usage sharing helps QRST understand engagement. It is off until you enable it for your account. Supported web and Android versions send a small activity signal while foregrounded and recently used, containing only the platform; QRST associates it with your account and server time. We estimate active time in 30-second intervals and combine simultaneous web/app use without double-counting. Owner-only dashboards show aggregate counts and estimated time, not message contents, keystrokes or browsing history. Activity older than 30 days is excluded and is removed on subsequent activity requests. Turning usage sharing off clears your recorded activity. Account deletion also removes these records. Firebase Analytics remains disabled; this is separate first-party measurement.

Where supported, optional Android app unlock uses your device’s system fingerprint, face or device-credential prompt. QRST stores the enabled preference locally; it does not receive or store your biometric data or device PIN. This local lock does not replace account authentication.

We process your first and last name, chosen email address, phone number and verification status; email addresses, subjects, bodies, drafts, delivery information and attachments; direct and group messages, audio files and read receipts; points transfers and reservations; and sign-in/session, account status, rate-limit and administrative records. You choose which files to upload. Optional contact matching, activity visibility and notifications process the information described below. Microphone access is optional and requested only when you choose to record a voice message.

Why we use it

We use this information to create and secure accounts, verify phone numbers, deliver email and direct messages, store files, maintain points history, prevent abuse, provide support and operate the service. Message content is stored on our servers; QChat does not currently provide end-to-end encryption.

Personal profiles and linked devices

Optional QChat profile names, bios and photos are stored with your account. You choose whether they are visible to everyone on QRST, people in your chats and groups, or only you. Your username remains visible. Photos are cropped and re-encoded before upload. Linked-device controls show active signed-in sessions and let you revoke them across QRST Mail and QChat. Theme preferences stay on each device. Live updates use an authenticated connection carrying change counters; message content is fetched through the normal protected chat API.

Safety reports

We store block choices and the date/version of your QChat terms acceptance. If you report a received message, we share that selected message and your reason with the QRST owner for abuse review. Reports and enforcement records currently have no automatic expiry and may remain after account deletion. Only report relevant content; do not add unrelated sensitive information.

Who receives information

Recipients receive the messages and files you send them. Twilio processes phone verification. Resend processes external email delivery, receipt and attachments. Hosting and storage infrastructure provided through OpenAI Sites and Cloudflare processes application data. These services may process information outside your country. The owner console provides account operations and usage totals, not unrestricted browsing of private QChat conversation bodies. Authorized technical administration may require access to stored records for support, security or deletion.

The current QRST service does not sell personal information or include advertising trackers in its application code. This does not describe practices of external websites you choose to visit.

Optional password sign-in

Phone verification remains available. If you choose password sign-in, QRST stores a randomly salted scrypt password hash, not the password itself. Setting or changing a password requires a phone-verified session from the last five minutes and revokes older sessions. Password sign-in uses rate limits and does not send a text message. Password hashes are removed when account deletion is requested. We retain a password-change event without the password for security auditing.

Cookies and device storage

QRST uses authentication cookies. Keep me signed in defaults to 30 days for new sessions. If unchecked, the server session expires after 12 hours and the browser cookie is not persistent. Signing out revokes that session. Other devices remain signed in until signed out, expired, suspended or an account-deletion request closes access. Hosting and owner administration may use their own authentication cookies.

Retention and your choices

Active account content is stored until removed through available account controls or account deletion. Moving email to Trash alone is not permanent deletion. Expired verification challenge cleanup occurs during subsequent verification requests; security rate-limit records may remain after their enforcement window. You can request access, correction or deletion through support. We may need to verify account ownership.

Delete individual QChat messages or request deletion of selected data →

Request deletion of your account and associated data →

Safety reports, the specific messages reported by customers, and enforcement records may be retained after deletion for abuse review. These currently have no automatic expiry. Contact support for questions about this evidence.

What deletion removes

After the owner fulfills your request, QRST removes your phone number, profile names, sign-in sessions and matching verification records; your mailbox and drafts; QChat conversations involving your account; your points balance, reservations and private transfer notes; and uploaded files that are not part of another recipient’s mailbox.

What remains

Emails and attachments already delivered to other people remain in their mailboxes, including other QRST accounts and external email services. Their transfer history can remain. We cannot erase their copies or screenshots.

QRST reserves your old username and retains a disabled account identifier so nobody can claim your old email address or impersonate you. Deletion request timestamps, completion records, security/admin audit records, aggregate usage and delivery-event identifiers are retained without your phone number or profile names. These records currently have no automatic expiry. Files needed for a recipient’s delivered mailbox remain while that copy is stored.

Twilio, Resend and our hosting provider may retain service logs, backups or legally required records under their own policies. QRST does not claim that submitting this form immediately erases those records. Contact support about provider-held data or other privacy requests.

Timing and access

Submitting a verified request closes account access immediately. The QRST owner processes deletion manually; there is currently no guaranteed completion time. Save your request reference and contact support to check progress. Do not assume the request is finished until support confirms completion.

QChat contacts, groups and shared files

On the web and in earlier QRST Mail Android versions, contact matching uses phone numbers you enter or paste. QRST Android 0.4.0 also offers the system contact picker to select a phone number, without requesting broad address-book permission. Selected contact names stay on your device and are not uploaded. Contact results are cleared when you leave the People screen. Supported earlier QChat Android versions may also offer selected-contact lookup. Only numbers you explicitly choose to submit are sent over HTTPS to find QRST accounts that have opted into phone-number discovery, up to 100 numbers per request; submitted numbers are not stored as a contact list. Discovery and online/typing visibility default to off. Where supported, you can change them in QChat. Activity timestamps expire from display automatically; the latest timestamp is retained until replaced or account deletion. WhatsApp invitations open a draft in WhatsApp; you choose whether to send it and WhatsApp’s privacy terms apply.

Group invitations require acceptance before you can read or send group messages. Joining gives access to the group’s available history, including earlier messages, and members can see each other’s usernames. Leaving removes your access, but your messages remain for other members. Blocking direct contact does not remove either person from a shared group. Text edits are allowed for 15 minutes; deleting your message replaces it with a notice. Recipients may already have saved copies, and previously submitted abuse reports may retain the reported content for safety review.

Images, documents and audio sent through QChat are stored privately by QRST and served only to authorised conversation participants. Voice recording requires your microphone permission and an action to start recording. Recordings stay on your device until you choose Send; you can preview or discard them first. QRST Android 0.4.0 limits voice recording to two minutes and uses temporary private app storage for previews. Leaving the recording screen or putting the app in the background cancels an active recording and discards its temporary recording file; playback also stops. Uploads are limited to 10 MB each, 100 MB per sender and 1 GB across the service. Deleting a file message disables its QChat download, but does not immediately erase the stored file: it remains until account-deletion cleanup or manual support processing. After the owner fulfills whole-account deletion, the sender’s QChat files, discovery preferences, activity and device-notification registrations are removed; group messages sent by the deleted account are replaced with deletion notices. Recipients’ exported copies cannot be removed by QRST. See the selected-data deletion page for instructions and retention details.

QRST Android 0.4.0 and supported earlier QChat Android versions offer optional push notifications using Google Firebase Cloud Messaging. In QRST Android 0.4.0, Firebase automatic initialization is off until you enable alerts, and notification permission is requested after you opt in. When enabled, QRST stores a device registration token tied to your signed-in session and sends a generic new-message event to Google; the message body is not included. The app checks your current account before displaying the alert. Delivery depends on Google Play services, device settings and connectivity. Analytics is not enabled for this integration. Signing out clears the app's alerts and ends that session's access. Earlier QRST Mail Android 0.3.x versions do not include native push notifications. Web alerts require notification permission and the QChat page to remain open; they are not background Web Push.

Supported combined QRST Android updates can also alert you to incoming email after you explicitly enable mail alerts. Earlier chat-only registrations do not automatically opt into email alerts. QRST sends only a generic mail event through Firebase, without the subject, sender, recipient address or message body. The app checks your signed-in account and unread inbox before showing an alert. Notification delivery is best effort and is separate from successful email delivery.

Google Play review workspace

Authorised reviewers can use a separate password-protected workspace containing synthetic messages and an automated review companion. It cannot access customer accounts, mail or conversations. Review sign-in uses a server-held password hash and a separate secure session cookie. Review sessions last up to 12 hours. Signing out or deleting the review workspace removes its synthetic messages and reports; expired workspace cleanup runs on subsequent review sign-ins. Reviewers should not enter real personal information into this workspace.

Changes and questions

This page will be updated when QRST’s processing changes. For questions or privacy requests, email caspianstrike@gmail.com. Do not send passwords or verification codes.