Privacy Policy

E-Swatch (“we”, “our”, “us”) is a web-based analog clock with optional paid features. This page explains what data we collect when you use it.

Last updated: July 27, 2026

1. What we collect

Depending on how you use E-Swatch, we collect the following categories of data:

1.1 Account data (optional, only if you sign in)

If you choose to sign in with Google, we receive from Google:

• Your Google account ID
• Your name (as configured in your Google profile)
• Your email address
• Your profile picture URL (if available)

We use this data only to authenticate you and show your account in the UI. We do not post on your behalf, do not read your email, and do not access any other Google services.

1.2 Local preferences (always)

The clock and your settings (theme, mode, schedules, custom theme colors) are stored in your browser’s localStorage by default. This data never leaves your device unless you sign in and create cloud-synced schedules.

1.3 Cloud-synced schedules (only if you sign in and add schedules)

If you are signed in, your schedule entries (time, repeat rule, label, action type, enabled flag) are saved to our database so they can be restored on any device you sign in on.

1.4 Payment data (only if you buy Pro)

Payments are processed by Creem, a third-party Merchant of Record. We do not see or store your full card number, CVV, or bank details. Creem shares with us only:

• A purchase identifier
• The plan you bought (Monthly or Annual)
• The email used at checkout (to grant Pro access to your account if it matches)
• The subscription status (active, cancelled, expired)

Creem’s handling of payment data is governed by their own privacy policy, available at creem.io.

2. How we use the data

We do not sell, rent, or trade your personal data. We do not use it for advertising or marketing automation.

3. Third parties we share data with

• Google — authentication (see Google’s privacy policy at policies.google.com/privacy)
• Creem — payment processing and merchant of record (see creem.io)
• Cloudflare — hosting, edge network, and D1 database (see cloudflare.com/privacypolicy)
• Sumsub — identity verification for merchant onboarding (only our founder’s data, not yours)

4. Cookies and similar technologies

E-Swatch uses exactly one cookie, session, which holds a signed token that authenticates you. It is:

• httpOnly (not accessible to JavaScript)
• Secure (sent only over HTTPS)
• SameSite=None (so it works across subdomains)
• 30-day expiry, refreshed on each sign-in

We do not use advertising cookies, analytics cookies, or third-party tracking pixels.

5. Data retention

• Account record: kept while your account is active. Deleted within 30 days of account deletion.
• Schedule entries: kept while your account is active. Deleted with your account.
• Purchase records: kept for 7 years for tax and accounting compliance.
• Server logs: kept for 30 days, then aggregated or deleted.

6. Your rights

You can at any time:

• Sign out (clears the session cookie)
• Delete your account (removes your account record and schedules)
• Request a copy of the data we hold about you
• Ask us to correct inaccurate data

To exercise any of these, contact us at the address below. We respond within 30 days.

7. Children

E-Swatch is not directed at children under 13. We do not knowingly collect data from children. If you believe a child has signed in, contact us and we will delete the account.

8. Security

Data is transmitted over HTTPS only. The session cookie is signed with HMAC-SHA256. Database access is restricted to authenticated server-side functions. We do not log or store any passwords (sign-in is delegated to Google).

No system is perfectly secure. If you discover a vulnerability, please email us so we can fix it before public disclosure.

9. International transfers

Our servers are operated by Cloudflare on a global edge network. Data may be processed in the United States, the European Union, or other regions where Cloudflare maintains points of presence. By using E-Swatch you understand your data may be transferred to and processed in these regions.

10. Changes to this policy

We may update this policy. Changes take effect when posted on this page with a new “Last updated” date. For material changes we will, where reasonable, notify signed-in users by email.

11. Contact