Your records are not our database.

Owmii is local-first. Your daily business records stay on your device or in your own connected cloud account. Owmii stores the minimum data needed for licensing, device access, support, checkout delivery and waitlist handling.

Information Owmii may collect

purchase and license status from Paddle webhooks
activation, claim and device records
Drive account binding identifiers when you connect Drive
support messages and waitlist submissions
technical logs needed to protect and debug the service

Information Owmii does not store as daily records

client or guest lists
appointments, bookings, tasks and notes
business payments, expenses and reports
uploaded workspace documents and logos
Google Drive workspace backups

Why data is used

activate and validate licenses
enforce device and Drive account limits
send activation and support e-mails
process refunds, revocations and support requests
prioritize waitlisted workspaces

Google user data

How Owmii uses Google Drive data.

Google Drive connection is optional. Owmii asks for Google access only when you choose to connect Drive for cloud backup or multi-device sync. Owmii requests the minimum scopes needed for that feature: openid, userinfo.email and drive.file.

Data accessed

your primary Google account e-mail address
a Google account identifier used to bind the Drive account to your Owmii license
metadata for Owmii workspace files, such as file id, file name and modified time
the contents of Owmii workspace files that you create, open or sync with Owmii, including workspace backup files, sync logs and restore files

How it is used

to create, read, update and delete only Owmii workspace files used by the app
to sync the same Owmii workspace across your approved owner devices
to restore your workspace from your own Drive backups when you choose to do so
to make sure a license is not accidentally connected to multiple unrelated Drive accounts

How it is stored

your business records remain on your device and, if enabled, inside your Google Drive
Owmii stores a limited Drive binding record, such as a hashed Google account identifier, to protect the license and device sync flow
Owmii does not store Google OAuth access tokens or refresh tokens on its servers
a masked e-mail may be stored locally on your device so you can see which Drive account is connected

Limited use commitment.

Owmii does not sell Google user data, use it for advertising, use it to determine creditworthiness, or use it to train generalized AI or machine learning models. Owmii support does not read your Google Drive files unless you intentionally provide a specific export, screenshot or file to support for troubleshooting.

Control and deletion.

You can disconnect or revoke Google access from your Google Account permissions. You can delete Owmii files directly from your Google Drive. You can also contact [email protected] to ask Owmii to remove license-side Drive binding records.

Service	Role
Paddle	Merchant of record, checkout, invoice, tax and payment handling for direct website purchases.
Supabase	Owmii license, device, claim, webhook and waitlist backend data.
Cloudflare	Public API routing, DNS, security and delivery infrastructure.
Resend	Transactional e-mail delivery when activation and support e-mails are enabled.
Google Drive	Optional user-controlled cloud sync and backup. Owmii uses limited Drive access only for Owmii workspace files you create, open or sync with Owmii.

Retention and deletion.

License and purchase records may be kept as long as needed for activation, support, fraud prevention, accounting, refund handling and legal obligations. Waitlist data can be removed on request.

Your choices.

You can use Owmii locally first, choose whether to connect Google Drive and contact support about license or waitlist records. Deleting local workspace records is controlled from your device and backups.

Want the data model in plain English?

Read the data ownership page for a practical explanation of what lives where.

View data ownership

Last updated June 23, 2026. Contact [email protected] for privacy, license, waitlist or support-data questions.