Privacy Policy

1. Who We Are

This policy applies to CommStack (the “Service”), operated by OMII Agency (“we,” “us,” “our”). CommStack helps people who meet in person stay in touch: you capture a contact at an event (by photographing a business card, scanning a QR code, dictating a voice note, or typing), CommStack saves them to your address book, and drafts a short follow-up message that you review and send from your own email account.

CommStack never reads your mailbox. The only email permission the Service requests is the ability to send a message you have reviewed, from your own address. We cannot see, search, or process your inbox, and we do not ask for permission to.

2. Two Kinds of People, Two Roles

Users are people with a CommStack account. For account data (your profile, settings, billing), we are the data controller.

Contactsare people a user captures — they have not signed up for anything. For contact records, the user who captured them is the controller and CommStack processes that data solely on the user’s instruction: storing it, writing it to the user’s own address book, and drafting the user’s follow-up message. We never use contact data for advertising, never sell or share it, and never contact a captured person ourselves.

If you have been captured as a contact and want the record corrected or removed, email privacy@omii.agency — we will forward the request to the user who holds the record and confirm the outcome to you within 30 days.

3. What We Collect

For users: name, email address, password hash or Google sign-in identity, profile details you add to your digital card (title, company, photo, links), your message-style preferences including example messages you provide verbatim, billing status, and a security log of account actions (sign-ins, connections, deletions).

For each captured contact: the details captured — typically name, phone, email, title, company, website, a photo of them or their business card if you take one, where and when you met, and any notes or a spoken recap you record about the conversation.

Inferred data:when a contact’s email is on a company domain, CommStack may infer their company name and website from the domain. Inferences are stored with the contact and deleted with it.

Sent messages: when you send a follow-up through CommStack, we keep a log of the message so you can see what you sent. Message bodies are automatically erased after 90 days (see Retention); the fact that a message was sent is retained for your history.

Voice capture:dictation and conversation recaps use your browser’s built-in speech recognition (on Chrome this is Google’s speech service; on Safari, Apple’s). CommStack receives only the resulting text — we never receive or store the audio.

4. Google User Data

If you connect a Google account, CommStack requests exactly three scopes, each tied to one visible feature:

• gmail.send — to deliver the follow-up message you reviewed and tapped send on, from your own address. Send-only: CommStack cannot read any email.
• contacts — to write the person you captured into your own Google Contacts. Google offers no write-only contacts scope; although the granted scope technically permits reading, CommStack does not read, list, or import your contact list — the only operation performed is creating the contact you captured.
• calendar.readonly — to name the event where you met someone, by checking your calendar for an event overlapping the capture time. Read at capture time only; no calendar data is stored beyond the event name you confirm.

CommStack’s use of Google user data complies with the Google API Services User Data Policy, including the Limited Use requirements: Google user data is used only to provide the features above, is never used for advertising, is never sold, is never used to train AI models, and is not read by humans except with your explicit consent, for security, or to comply with law.

Nothing read from Google is sent to our AI provider. The AI drafting step receives the contact record and your own notes — never your email, contact list, or calendar contents.

5. Microsoft Account Data

Connecting a Microsoft account requests the equivalent permissions: send mail as you (Mail.Send), write captured contacts to your Outlook contacts (Contacts.ReadWrite — used for creation only), read your calendar to name events (Calendars.Read), and basic sign-in identity. The same Limited-Use commitments apply.

Disconnecting in Settings removes CommStack’s stored credentials immediately. To also clear the consent record from your Microsoft account, visit account.live.com/consent/Manage.

6. AI Processing

Three features use Anthropic’s Claude models: reading a photographed business card into text, deriving your writing-style profile from example messages you provide, and drafting your follow-up message. What is sent: the card image (for reading), your examples (for style), and the contact’s captured details plus your own notes and recap (for drafting). Business-card images are processed for reading and are not stored by us as images unless you attach a photo to the contact. Our agreement with Anthropic does not permit training on this data.

Every AI-drafted message is a draft: nothing sends without your explicit review and tap.

7. Storage & Security

Data is stored with Supabase (database, authentication, file storage) and served from Vercel. All data is encrypted at rest by our infrastructure providers and in transit via TLS. In addition, the OAuth credentials for your connected Google/Microsoft account are encrypted a second time at the application layer (AES-256-GCM) — a database leak alone cannot expose a usable credential to your mailbox or contacts.

Access to every record is enforced row-by-row at the database layer: a user’s session can only ever read or modify that user’s own rows.

Application logs and error tracking exclude message bodies, notes, and contact details. No system is perfectly secure; if a breach affects your data we will notify you without undue delay.

8. Retention & Deletion

• Sent-message bodies: erased automatically 90 days after sending — or sooner if you delete the contact, which also removes its message history.
• Deleted contacts: kept in your trash for 30 days (so an accidental swipe is recoverable), then permanently erased along with their photo.
• Security log: 90 days.
• Account deletion:immediate and irreversible, self-serve in Settings → Account. It erases your profile, contacts and their photos, events, message history, style profile and examples, and public card; cancels any active subscription; revokes CommStack’s Google access; and deletes stored Microsoft credentials.
• Disconnecting a provider (Settings → Integrations) immediately deletes the stored credential; for Google we also revoke the grant with Google.

These schedules are enforced by automated jobs, not manual process.

9. Subprocessors

We share data only with the processors required to run the Service: Supabase (database, auth, storage), Vercel (hosting and request logs), Anthropic (AI processing, §6), Stripe (billing — we never see full card numbers), Sentry(error monitoring, with message content and contact details excluded), and your browser’s speech provider (Google or Apple) if you use voice capture. We do not sell or share personal information within the meaning of the CCPA, and we do not use it for cross-context behavioral advertising.

10. Your Rights

You can access and correct your data in the app, disconnect providers, and delete your account entirely — all self-serve. Captured contacts can request correction or erasure via privacy@omii.agency (§2). Depending on where you live you may have additional statutory rights (access, portability, objection); write to the same address and we will respond within 30 days.

11. Changes & Contact

Material changes to this policy will be posted here with an updated date. Questions:privacy@omii.agency.