How Saver handles your data

Saver is built to help people understand their money without making data collection feel mysterious. This policy explains what we collect, what we do not collect today, and how you can control your account data.

Last updated: May 13, 2026

1. Information we collect

We collect the information needed to create your account, personalize the setup flow, and show your dashboard. This can include your name, email address, authentication provider, money mode, available money, saving goal details, and transactions you add inside Saver.

We may also receive basic technical information from our hosting, authentication, and email providers, such as browser data, timestamps, error logs, delivery status, and security events.

2. Information we do not collect today

Saver currently does not read your raw SMS messages, call logs, phone contacts, Gmail inbox, bank login credentials, UPI PIN, card PIN, or payment app passwords.

If a future version adds SMS or statement import, that feature should be optional, permission-based, and explained before you enable it.

3. How we use your information

To create and secure your Saver account.
To remember onboarding progress and personalize dashboard values.
To send account emails such as confirmation and password reset messages.
To detect bugs, improve reliability, and protect against abuse.
To respond when you contact us for help.

4. Where your data is processed

Saver uses trusted service providers to run the product. Supabase provides authentication and database storage. Vercel hosts the website. Resend sends account emails. Google may process data when you choose Google sign-in.

These providers process data under their own security practices and policies. We only use them for product operation, authentication, storage, delivery, and reliability.

5. Your choices

You can choose not to provide optional setup details, sign out at any time, reset your password, or ask us to help delete or export account data that belongs to you.

If you use Google sign-in, you can also manage Saver's access from your Google Account settings.

6. Security and retention

We use HTTPS, Supabase authentication, database access policies, and service-provider safeguards to protect account data. No online service can promise perfect security, so you should use a strong password and keep access to your email account safe.

We keep account data while your account is active or while it is needed to operate the service, handle security, or meet legal obligations. Prototype transaction data may be stored locally in your browser until the app moves that data fully into the database.

7. Future SMS or import features

If Saver adds SMS parsing, bank statement import, or another automated source in the future, the app should ask for clear permission first. The goal should be to save structured transaction details, not unnecessary raw messages or unrelated personal content.

8. Changes to this policy

We may update this policy as Saver changes. When the update is meaningful, we should update the date above and make the new version easy to find.

9. Contact

For privacy questions, account deletion, or data export requests, contact hello@savers.dev.