← Policy index

Data practices · Last updated June 8, 2026

Data practices

OgaTailor is built around a simple promise: your workshop records should survive a bad network day and a good payday. That means local storage first, optional cloud shoulders second, and no spreadsheet cosplay in between. Here’s how that shows up under the hood, in human words.

Local-first storage

Everything you enter — customers, measurements, draft orders — lands in an on-device database first. You can work in airplane mode. Nothing has to touch our servers until you use a feature that explicitly needs the network (cloud backup, multi-device sync, authentication against your account, and similar).

Sync & conflicts

When cloud features are on, the app periodically pushes local changes and pulls updates from the API. We timestamp changes so the server can spot disagreements between devices. If two edits collide, we resolve conservatively: we don’t pretend “last writer wins” is always fair for tailoring histories. Expect transparent handling in-product where it matters, and server logs that help us debug without stalking your clients.

IDs & phone numbers

Internal identifiers are opaque UUIDs — stable, sync-friendly, not guessable serials. Phone numbers can be stored if you choose, but they’re not the spine of the system. Treat any phone field as optional bookkeeping you’re responsible for collecting lawfully.

Subprocessors & categories

Depending on features you enable, data may transit through or rest with:

  • Infrastructure & API hosting — servers that run our PHP backend and MySQL datastore.
  • Push notifications — Firebase Cloud Messaging (or successor) for device tokens and delivery metadata.
  • Authentication — Google Sign-In when you choose that path; Google processes tokens according to their policies.
  • Error & diagnostics (if enabled) — crash or logging tooling limited to technical traces.

We sign data-processing terms where available and review vendors on a schedule rather than “set and forget”. Replace hostnames here with your production vendor list when contracts are final.

Exports & PDFs

Paid tiers may let you generate CSV summaries, printable measurement sheets, or invoices. Those files are created on your device or streamed through your session; they’re yours to share. Once you hand a PDF to a customer over WhatsApp, that copy is outside our control — same as paper.

Google Sign-In

If you log in with Google, we receive profile basics (name, email, subject identifier) to match your workspace. We don’t gain access to your Gmail, Drive, or search history. You can revoke app access from your Google account settings at any time; features tied to that login will stop until you reconnect or migrate.

Also read: Privacy Policy · Camera & photos · Microphone & voice