SaveMyChat Privacy Policy

Effective October 20, 2026. This policy is publicly accessible without signing in. About SaveMyChat · Terms of Service

1. Introduction

SaveMyChat is an independently operated Chrome extension and website for exporting WhatsApp chats and contacts and optionally saving selected conversations to a cloud archive. This policy explains what the extension and wa.dser.io access, collect, use, store and share. Contact the SaveMyChat operator at support@dser.io about privacy or your data.

2. Information We Collect

2.1 Local Export and Optional Cloud Archive

Local chat and contact exports are processed in your browser. Saving chats to the cloud is optional and starts only after you sign in and choose conversations to save. Cloud archives can be viewed and shared, but cannot be restored to WhatsApp. When you use cloud features, we store:

  • Your Google account identifier, verified email address, display name and profile picture URL for sign-in and account display
  • Selected conversation names, source account identifiers, messages, sender information, and attachments you choose to save
  • Save checkpoints, storage usage, device sessions, and sharing settings
  • Limited request information, including IP addresses used for abuse prevention and service operation

2.2 Local Data Storage

The extension stores preferences and the last known cloud account profile in Chrome storage. Browser sessions use Secure, HttpOnly cookies; the extension does not store your Google password. Its local IndexedDB database stores save tasks, pending message batches and message fingerprints so interrupted manual saves can resume:

  • Pending batches are cleared after successful submission
  • Removing a save task clears its local checkpoints and message fingerprints
  • Signing out ends the current cloud session and clears the cached cloud account profile; existing task metadata remains isolated to the original account

2.3 Google account data and permissions

Google sign-in requests only openid, email and profile. We verify Google's identity response and receive a stable Google account ID, verified email, display name and profile picture URL. The ID links you to your SaveMyChat account; your email identifies the account in the interface and supports account ownership checks; your name and picture are used for account display. These profile fields are stored in the account database. We do not request access to Gmail, Google Drive, Google Contacts, calendars or other Google content, and we never receive your Google password.

3. How We Use Information

We use cloud data to authenticate your account, save the conversations you select, display messages and attachments, enforce storage allocations and operate sharing protected by a share code. Saving is started by your manual action; login alone does not upload chats. People with a share link and its code can access the selected conversation until you revoke the link or delete the conversation. Live shares also expose content you save later. Sharing may display the archive owner's name and email so recipients can identify the source. Attachment access depends on the permission you choose.

Google user data is used only for sign-in, account display, access control and account support. We do not sell or rent Google user data, use it for advertising or profiling, or use it to train general-purpose AI models. SaveMyChat does not generate images or videos and does not use Google APIs to generate non-consensual intimate imagery. Our use and transfer of Google user data follows the Google API Services User Data Policy, including its Limited Use requirements.

The extension uses Aptabase for feature usage, error and installation events. Those events are not intended to contain message bodies, attachments or Google account profile fields. Hosting and security systems may process IP addresses and request metadata to operate the service and prevent abuse.

4. Data Security

The cloud service uses the following protections:

  • Cloud communication uses HTTPS; conversation data is held in private Cloudflare storage
  • Message and attachment requests require account authorization or a valid share session
  • Sharing passwords are stored as salted derived values, and repeated incorrect attempts are limited
  • To let you retrieve your own share codes, a separate encrypted copy is retained using a server-held encryption key
  • We do not upload WhatsApp login credentials. Cloud storage uses server-side access control and is not end-to-end encrypted against the service operator

5. Third-Party Services

The Extension may interact with third-party services in the following limited ways:

  • Chrome Web Store: The Extension is distributed through the Chrome Web Store, which has its own privacy policies
  • WhatsApp Web: The Extension interacts with WhatsApp Web to access chat data, but this interaction is limited to your local browser
  • Google: Provides optional account sign-in. We request basic identity information and do not request Google Drive access
  • Cloudflare: Hosts the cloud website, APIs, account metadata, messages, attachments, and background processing
  • Aptabase: Receives extension usage events for product analytics

Cloudflare processes hosted account data and archives on our behalf. Google handles the sign-in process under its own privacy policy. Google user data is not sold to third parties; access is limited to providing the features described here, your explicit sharing choices, service operation and legally required disclosures. We do not send chat bodies or Google profile fields to Aptabase as analytics properties.

6. Children's Privacy

The Extension is not intended for use by children under the age of 13. We do not knowingly collect any information from children under 13. If you are a parent or guardian and believe your child has used the Extension, please contact us at support@dser.io.

7. Changes to This Privacy Policy

We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page.

You are advised to review this Privacy Policy periodically for any changes. Changes to this Privacy Policy are effective when they are posted on this page.

8. Your Rights

You can pause an active save or remove its local task in the extension, revoke links and delete conversations in the cloud management page. Removing a local task does not delete its cloud archive. Deleting a cloud conversation immediately blocks access and revokes its shares; message indexes and physical objects are removed asynchronously by maintenance jobs. Attachments still referenced by another retained conversation or version remain until those references are removed. Revocation cannot erase copies already downloaded by recipients.

Retention: Cloud archives and their stored versions remain until you delete the conversation or request account deletion. Your Google-linked profile remains while you have a SaveMyChat account. Access sessions last up to 15 minutes and refresh sessions up to 30 days, subject to renewal and sign-out. Temporary authorization flows and unfinished uploads expire and are cleaned up by background maintenance. Signing out does not delete archives.

Access, correction and account deletion: Email support@dser.io from your account email address to request a copy, correction or deletion of your account profile and associated cloud archives. We may verify ownership before acting. You can also remove SaveMyChat's Google connection from your Google Account connections. Revoking Google access does not itself delete data already saved with SaveMyChat; delete cloud conversations or request account deletion separately.

9. Contact Us

If you have any questions about this Privacy Policy, please contact us at:

10. Effective Date

This Privacy Policy is effective as of October 20, 2026.