1. Overview
Pomoria is designed to work without a required account. Core timer data is stored locally in your browser by default. If you choose to sign in, cloud sync and premium subscription features may use external services described below.
2. Data We Store Locally
Timer sequences, templates, timer state, task labels, app settings, language preference, audio settings, and history logs may be stored in your browser using LocalStorage and IndexedDB.
Local audio files selected by you are processed in the browser. Pomoria does not upload local audio files to our servers.
Custom theme background images may be uploaded for Premium accounts so they can sync across devices. Pomoria keeps these images in the existing Cloudflare R2 asset storage used for Premium media, with user-scoped object keys.
3. Optional Account and Cloud Sync
Login is optional. If you sign in, Pomoria uses Clerk for authentication and account management. When cloud sync is enabled, timer templates, sequence settings, selected active template ID, and activity history may be sent to our Cloudflare Worker API and stored in Cloudflare D1 so that they can sync across your devices.
We do not intentionally store local audio file contents in cloud sync. Cloud sync is intended for structured timer and activity data.
4. Google Account Data
If you choose to sign in with Google through Clerk, Pomoria may receive or use basic Google account information made available through Clerk, such as your email address, display name, profile image, and authentication identifiers. Pomoria uses this information only to authenticate you, display your account profile, associate cloud sync data with your account, provide subscription access, and support account-related requests.
Pomoria does not sell Google user data, use it for advertising, or share it except with service providers needed to operate the app, such as Clerk for authentication and Cloudflare for hosting and optional sync storage. Our use of Google user data is limited to the purposes disclosed in this Privacy Policy and is intended to comply with Google's Limited Use requirements.
5. Premium Billing
Pomoria Premium uses Clerk Billing for subscription management. Clerk Billing may use Stripe as the payment processor. We do not store credit card numbers. Subscription status is read from Clerk Billing so the app can unlock premium features.
6. Third-Party Services
- Clerk: Used for authentication, user management, subscription status, and billing UI. Clerk, Inc. privacy contact: privacy@clerk.dev.
- Stripe: May be used through Clerk Billing for payment processing.
- Cloudflare: Used to host the app, run backend Worker APIs, and store optional sync data in D1.
- YouTube and Spotify: If you configure media links, embedded players may load from those providers and are governed by their own terms and privacy policies.
7. Cookies and Browser Storage
Pomoria does not use advertising cookies. Clerk may use cookies or browser storage necessary for authentication and session management. Pomoria uses browser storage to remember timer state and preferences.
8. Sharing
If you use share features, sequence data may be encoded into a share URL or sent to a connected room/session. Do not include sensitive personal information in task names, sequence names, or shared room content.
9. Your Choices
- You can use the app without logging in.
- You can clear local browser data to remove locally stored timer data.
- You can sign out to stop account-based sync from the current browser.
- You can cancel Premium from the account or billing management screen when available.
10. Contact
For privacy, billing, disclosure, or deletion requests, contact us through:
https://pomoria.app