ADS SECURITY / SECURE CHAT

ADS Secure chat privacy

Privacy notice, version November 13, 2026, revision 1. Advanced Data Support Inc. operates ADS Secure chat. Contact: advanceddsinc@gmail.com.

These notices cover ADS Secure chat when available in your version of ADS Security. Access may be limited during rollout. Publishing a policy does not open signup or announce a release date.

Who operates chat

Advanced Data Support Inc. operates ADS Secure chat and handles support, safety reports and deletion requests at advanceddsinc@gmail.com. Karlovic Systems LLC, owned by Advanced Data Support Inc., produces and publishes ADS Security. This notice covers ADS Secure chat when it is available in your installed version of ADS Security. Access can be limited before or during a rollout; publication of this notice does not open signup or announce a release date.

Account and connection information

Creating an account or signing in sends your username, chat password and connection information over HTTPS to ADS. Signup also requires an email address. ADS uses that address for verification and password recovery. The server stores account identifiers, a password hash, device and session records, and the information needed to operate and secure chat.

ADS hosts the chat service on a separate server environment under its control. Cloudflare provides DNS and the HTTPS tunnel connecting users to the service. Cloudflare terminates the HTTPS connection and can process account requests, passwords in transit, email addresses, verification or reset links, IP addresses, reports and other request metadata. End-to-end encrypted message contents remain encrypted as they pass through this infrastructure.

Premium account linking

Premium chat access also links a verified subscription to one chat account. ADS verifies the account through the chat service using the access token transiently; the linking service does not save or log that token. A random account-bound challenge expires after five minutes and is used once. The signed chat grant contains the chat account ID, a hash of the installation identifier, product/plan, challenge and purchase-token hashes (including an earlier token hash when a subscription is replaced), not payment-card details or a purchase amount. Paid chat grants last at most 15 minutes and never beyond the verified paid period; explicit approved complimentary-account access may last up to 72 hours. A protected service record binds a subscription and its replacements to one chat account across devices, preventing reuse for another account. Active server membership authorizes that account on its signed-in devices; each device still needs its own usable encryption identity and contact verification. Membership does not transfer message keys. The protected service record does not contain message text or the raw Play purchase token. Minimal purchase-hash/account bindings, earlier-token hashes and deletion-replay records may remain after account deletion while needed to enforce an entitlement, prevent purchase reuse or prevent a restored deleted account from returning. ADS reviews this security need with its operating records and removes information no longer needed; no automatic reassignment or universal 90-day expiry is promised for these minimal records. Whole-server backups can contain these records and follow the 30-day backup limit. A public restore must reconcile later deletions, account restrictions and purchase-account bindings before exposure.

Verification and recovery emails

Resend delivers requested verification and password-reset emails using the notify.advanceddatasupportinc.com sender domain. It processes the destination address, email content, authentication links and delivery information. These emails do not contain your chat password or message-decryption keys. Authentication email is not end-to-end encrypted. Resend’s published retention period for email content, metadata and delivery records is 30 days. ADS requests applicable provider-side deletion when handling a verified deletion request; it does not claim immediate removal from all provider systems. See Resend’s published retention information. Copies delivered to your mailbox are also subject to your email provider’s practices.

Chat does not send message-notification or marketing emails, or automatically copy authentication emails to another mailbox. Email delivery and repeated requests are limited. Resetting a password signs out existing chat sessions. It does not restore lost message keys or give a new sign-in access to old encrypted messages.

Password recovery and sign-in do not require payment. Replacing an account’s encryption identity requires active chat membership and a separate warning and confirmation: it can remove existing server key backups and recovery settings, and contacts and other devices must verify the new identity. An email password reset does not perform that replacement automatically.

Messages and information other people can see

ADS uses the Matrix SDK for end-to-end encrypted, one-to-one text conversations. The server handles encrypted message events, account and device identifiers, room membership and message timing. Encryption does not hide this metadata. Contacts receive the information needed to communicate with and verify you. Recipients can keep or share messages after receiving them.

The app stores its private encryption keys and encrypted message database on your phone. Public account and device keys support identity verification. Devices exchange message-decryption keys using encrypted protocols; this version has no automatic key backup or device-transfer feature. A separate Android Keystore key protects saved session details and the local store passphrase. ADS does not receive the contents of your separate password, autofill-profile or file vault through chat.

Contact verification uses separate protocol requests over HTTPS. These requests are visible to the service and include account and device identifiers, public verification values and timing. They do not contain your conversation text or private message-decryption keys. ADS keeps these requests separate from the encrypted text conversation.

Phone storage and controls

The app saves your chat session, pending signup or recovery information, and accepted policy versions in its encrypted chat vault. It does not save your chat password. Pending email verification may be resumed for up to one hour; cancellation, completion or local chat-data removal clears that pending record.

The disappearing-message feature also keeps encrypted records marking messages as already viewed on this phone. These contain message identifiers and keyed fingerprints, and are retained with the phone’s chat data, including preserved profiles after account recovery. The 90-day ordinary server-history setting does not expire these local records. Removing local chat data removes this viewing history too.

If you choose a new-device recovery or move from the older private test server, the app preserves the previous local chat profile and encrypted store separately while preparing the new sign-in. That preserved data is not a usable message backup and does not guarantee access to old conversations. Confirmed local chat-data removal or account deletion also removes these preserved profiles and attempts to remove their encrypted caches.

Chat locks when you leave it or after five minutes without activity. It syncs while unlocked. This version has no automatic message-key backup or device transfer. Password/profile exports do not include chat messages or keys. Clearing storage, uninstalling or losing device keys can permanently prevent access to old messages, even if you reset your account password.

Secure chat asks Android to block screenshots, screen recording and display on non-secure screens. This does not prevent someone from photographing the screen with another device or retaining information they have already read.

Safety reports and support

Blocking stores the ignored account in your server-side account settings. In ADS, blocked contacts’ saved conversations are hidden and cannot be opened for messaging. You can block and decline an invitation without joining. A conversation report sends the conversation identifier, reporting account, reported contact, report time and the explanation you choose to write. That explanation is readable by ADS; decrypted chat history is not attached automatically.

The support option opens an email draft for an invitation, blocked or former contact, or another concern. Contact and conversation identifiers are left out by default; you can choose to include the identifiers shown. Opening or canceling the draft sends nothing. If you choose to send it, your email provider and ADS’s Gmail support mailbox can read what you include. Credentials, encryption keys and chat history are not attached automatically. Chat locks when you leave ADS.

ADS checks support, safety reports, appeals and deletion requests daily. Review and follow-up are performed by the operator, not an automated moderation service. We handle verified account-and-associated-data deletion requests within 30 days after ownership is verified. A report does not establish wrongdoing or promise immediate restriction. ADS is not an emergency service.

We use this information to handle requests, investigate abuse and operate the service. ADS chat has no advertising or analytics SDK and does not sell chat data. Information may be disclosed when legally required.

Retention and account deletion

Account records and encrypted conversation events are stored to provide the service. Deleting the app does not delete them. The account-deletion page explains how to request deletion without access to the app.

The service has a 90-day target for ordinary message history, with scheduled cleanup while it is running. Required room state and protocol metadata can remain. You can send optional messages that disappear after viewing and remove your own messages for everyone. These controls do not remove every copy. Removal can be delayed while a phone or the service is offline. Copies already saved by recipients cannot be removed by ADS.

The server removal setting hides successfully removed message content from server responses immediately and lets background cleanup clear the stored original content without an additional grace period. Cleanup is scheduled and can be delayed by downtime or a backlog. Message identifiers and protocol metadata can remain. Phone caches and other copies need separate handling; this setting is not an immediate wipe of every copy.

Automatic removal after viewing requires the original sending sign-in and saved chat data to finish the removal request. Clearing that data or recovering with a new device identity can leave pending removals unfinished. Preserved old profiles protect viewing history on that phone, but this version does not automatically resume their pending acknowledgments or removals.

The 90-day message setting does not apply to every account record, safety report, log or backup. Support correspondence and the contents of closed safety cases are retained for up to 90 days after closure, unless a documented legal or security hold requires specific information for longer. We review holds and remove information no longer needed. Active cases are retained while needed for handling the issue. Verified deletion requests can require earlier removal of associated data; the normal case-retention period is not a reason to keep unnecessary personal information. Minimal action/deletion records may be retained to document a decision, prevent account reactivation or apply deletion after recovery; these are distinct from report bodies and email attachments. Successful account deactivation removes the password hash and local email association and revokes active sessions. Ordinary visible device access is removed, but the account identifier, public cross-signing key metadata and related hidden device records can remain; they are not active sign-in sessions. Deactivation with an erase request does not delete every public key, historical event or report. Contact ADS for associated-data deletion; see the deletion instructions and limits.

ADS keeps an encrypted server backup and a separate encrypted USB copy. Recovery from the server backup has been tested. Server backups include server-held account/configuration information and stored ciphertext, not the private message keys held only on phones. The operator’s backup procedure is weekly encrypted capture with backup copies retained for no more than 30 days from capture, including separate USB copies. These are manual tasks, not an installed automatic schedule. A missed backup can cause loss of later data; it does not extend the 30-day limit on an older copy. An older backup can contain information deleted since capture. Backups are unavailable for ordinary account use, and ADS must reconcile later deletion requests, account restrictions and purchase-account bindings before reopening a restored service to public access. The current restore helper remains restricted to disconnected recovery until that reconciliation is reviewed.

Other retained records

Service output logs currently use size-based rotation, not a fixed-day expiry. ADS reviews relevant logs and requests applicable processor-side deletion during verified deletion handling; specific security or legal records may be retained with a documented reason. Cloudflare processes connection and request information according to the service it provides and its own privacy terms; ADS does not assign a universal day limit to every Cloudflare record. Resend’s published email-record period is 30 days. ADS manually deletes expired support correspondence from its Gmail mailbox, including Trash; copies in another person’s mailbox are outside ADS’s control. Removing reports submitted by a deleted account is separate from reviewing reports about that account. The operator checks both. Service availability and signup limits are separate from these retention duties.

Questions and other ADS features

Secure chat conversations and Geo Spoofer are Premium features. Password and file vaults, autofill, call blocking and ADS Browser are free within technical and device limits, without a paid capacity tier. Existing chat account sign-in, recovery, deletion, local cleanup and support remain available without payment. A lapse does not delete saved data, and deleting chat does not cancel a Play subscription.

For access, correction, deletion or privacy questions, contact advanceddsinc@gmail.com. Never send a password, verification code or encryption key. The Android privacy policy covers the app’s other features. The chat features described here apply to versions that include ADS Secure chat. Availability may differ during rollout; local vaults and other ADS tools remain separate from the chat service.