Privacy Policy

Omveta is a personal work-schedule and hours helper. You build templates, assign rotating schedules, apply day or period overrides, and can log actual worked hours against planned time. Totals such as overtime or missing hours are calculated in the app from what you enter.

According to the current architecture, your weekly patterns and templates, rotation and schedule configuration, day and period overrides, logged actual hours, optional notes, and related work-period preferences are stored locally in an app database on your phone. Omveta does not upload this schedule content to our servers.

Account sign-in tokens, if you use email sign-in, are kept in the device keychain or secure storage as provided by the operating system.

You can use Omveta without an account. If you sign in with email, we collect your email address to send one-time sign-in and account-deletion codes, and we create an opaque account identifier for your profile. We use this to manage your session and to associate lifetime access with your account so it can be restored after reinstall, where supported.

Lifetime access is a one-time purchase through Apple or Google. Omveta does not sell auto-renewing subscriptions.

To verify and maintain lifetime access, our servers may process and store purchase-related records such as product identifier, store transaction or purchase identifiers, purchase time, and refund or revocation status, together with related validation information from Apple or Google. Omveta does not receive or store your full card number or other payment-method credentials from Apple or Google - those stay with the store.

Lifetime status may also be mirrored in local app storage for offline display.

If you voluntarily submit feedback, a problem report, or a feature idea in the app, we receive the text and any optional contact details you enter. When you are signed in, we may associate that submission with your account identifier and email so we can follow up.

We use PostHog (product analytics hosted in the European Union) as a service provider to understand how the app is used - for example whether people create schedules, log hours, or complete a lifetime purchase. This helps us improve Omveta. It is not used for advertising, and we do not sell your personal information.

Before you sign in, analytics uses an anonymous identifier generated on the device. After sign-in, that activity may be linked to your opaque Omveta account identifier (not your email).

Analytics events contain coarse product metadata (such as feature type or provider). We do not send your schedule content, notes, exact hours or times, employer name, email, or payment credentials to PostHog. We configure the mobile analytics SDK so it does not perform IP-based GeoIP location enrichment for events. Session replay is not enabled.

We use Google Firebase Crashlytics as a service provider to collect crash reports and unexpected technical errors so we can fix bugs. This may include stack traces, device model, operating system version, app version, diagnostic logs tied to a crash, and Crashlytics or Firebase installation identifiers.

We do not attach your email, schedule data, notes, or purchase receipts to crash reports, and we do not set your Omveta account identifier on Crashlytics reports.

We use service providers that process data on our behalf, including PostHog (analytics), Google Firebase Crashlytics (crash reporting), our email/SMTP provider (one-time codes), and Apple or Google (in-app purchases and store verification). They process data to provide these services to Omveta, not to sell your schedule content.

Omveta does not serve third-party ads. We do not sell your schedule content.

Account, session, purchase-ledger, and account-linked support records are kept while your account exists and are removed when you delete your account, as described below.

When PostHog account-linked analytics deletion is configured on our servers, we request deletion of the PostHog person profile tied to your opaque account identifier and queue deletion of associated events. PostHog processes event deletion asynchronously.

Crashlytics retains crash and diagnostic data according to Google's Crashlytics retention practices (Google documents a rolling window measured in days for live Crashlytics data). We do not claim the ability to erase every historical crash report on demand.

Operational security logs on our hosting provider (for example request metadata used to operate the service) may be retained according to that provider's log retention.

You can permanently delete your Omveta account from Settings in the app, or from the public Delete Account page at https://omveta.com/account-deletion.

Deletion removes your Omveta account, sign-in sessions, one-time codes for that email, account-linked support submissions, and Omveta's server-side purchase association records for that account. On a connected device, account-associated local schedule and hours data is cleared. Offline devices are not erased until they reconnect.

A one-time Apple or Google purchase is not automatically refunded, and there is no recurring Omveta subscription to cancel. Apple or Google continue to control store purchase history for your store account. After you create a new Omveta account, Restore Purchases can re-link lifetime access when the store verifies the purchase.

Device trial timing and some device preferences may remain on the phone. Analytics or diagnostic records that cannot be fully erased immediately may remain with service providers until their deletion or retention processes complete.

For other account-related requests, use in-app support or email support@omveta.com.

If we later offer optional cloud backup or sync, it will be opt-in where possible, and we will update this notice with what is stored, where, and how to delete it.

We may update this policy as the app evolves. The Last updated line at the top will change when we do. Continuing to use the app after an update means you accept the revised policy.