Privacy Policy

Who we are

Stacking Clients LLC (dba Oratr) operates Oratr, a workspace for hosts who present a deck, join attendance to the slide-change log, and improve the deck afterward. Questions about this policy: privacy@oratr.io.

What we collect

Depending on how you use Oratr, we may store:

• Account details from sign-in: email address, name, and a provider account identifier.
• Workspace content you create: decks, slides, notes, session logs, attendance, and improvement proposals.
• Optional meeting-platform data you connect (Zoom is described below; Microsoft Teams and Google Meet work the same way if you connect them).
• Optional AI credentials if you bring your own AI, stored encrypted.
• Technical logs needed to run the service (for example authentication events and webhook deliveries).

Sign-in

You can sign in with a one-time email code or with Google. Email codes are sent as transactional mail. Google sign-in is handled by Supabase Auth; we receive the email, name, and account identifier Google provides so we can create and recognize your workspace. We do not get your Google password.

Google API Services User Data Policy (Limited Use)

Oratr's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

In practice that means:

• Google user data is used only to sign you in and, if you connect Google Meet, to read conference records and participant join/leave times so we can compute slide drop-off.
• We do not use Google user data for advertising.
• We do not sell Google user data.
• We do not use Google user data to train generalized artificial-intelligence or machine-learning models.
• We do not transfer Google user data to other apps except to provide or improve these user-facing features, to comply with law, or as part of a merger or acquisition with notice.
• Humans at our organization do not read Google user data unless you ask us to, we must for security or abuse investigation, or the law requires it.

If you connect Google Meet, the scopes are openid, email, and meetings.space.readonly. We do not request Gmail, Drive, or Calendar contents.

Zoom data

Connecting Zoom is optional. The Zoom app is user-level and read-only. We do not start meetings, send chat, or change your Zoom settings.

What we access. With your consent we request: your Zoom user profile; lists and details of your meetings and webinars; and past meeting and webinar participants (who joined and when they joined or left).

Why. We join that attendance with the presenter slide-change log so you can see which slides lost the room. Participant records are used for that workspace analytics purpose only.

How we store it. Zoom OAuth tokens are encrypted at rest. Meeting and webinar identifiers, titles and times we need, and participant join/leave records are stored in your Oratr workspace in Supabase.

How to disconnect. In Zoom, open your account’s connected apps (or the Zoom App Marketplace listing) and remove Oratr. That revokes our access from Zoom’s side.

How to delete. Email privacy@oratr.io and ask us to delete Zoom data. We will delete stored Zoom tokens, imported meeting and webinar metadata, and participant records tied to your workspace.

Decks, sessions, and attendance

Slide content, presenter events, CSV attendance you upload, and improvement proposals live in your workspace so the product can show drop-off and apply only the edits you approve. You can also connect Microsoft Teams for the same attendance purpose if you choose to.

Bring your own AI

You can bring your own AI in two ways: paste your own provider API keys (OpenAI, Anthropic, Google, or xAI), or connect Claude or ChatGPT through our MCP connector using your existing subscription with those products. We do not sell or meter AI usage.

API keys you paste are stored encrypted (envelope encryption) and used only to call that provider from your workspace. On the Claude / ChatGPT connector path we do not take an API key; the model runs in that product, and we store only the structured proposals you choose to keep until you approve or reject each change.

Email, storage, and payments

Transactional email (sign-in codes and similar account messages) is sent through Resend. Account, deck, session, connector, and related workspace data is stored in Supabase (Auth and Postgres) with row-level security. If you subscribe, Stripe processes payment information; we do not store full card numbers.

Sharing

We share data with the processors above only to run the service you asked for. We do not sell personal information. We may disclose data if required by law or to protect the service and its users.

Retention and deletion

We keep workspace data while your account is active. To delete your account and stored data, email privacy@oratr.io. We will delete account records, decks, session data, connector tokens, imported attendance, and encrypted API keys we hold. Processors such as Supabase, Resend, Stripe, Zoom, and Google may retain logs or billing records as their own terms require. Backup copies may lag for a short period before they expire.

Your choices

• Sign out at any time from the app.
• Disconnect a meeting platform from that platform’s connected-apps settings.
• Remove pasted API keys in Settings.
• Email us to export or delete workspace data.

Children

Oratr is for professional hosts, not for children under 16. We do not knowingly collect data from children.

Changes

If we change this policy in a material way, we will update the effective date on this page. Continued use after a change means you accept the updated policy.

Contact

Privacy requests: privacy@oratr.io. Operator: Stacking Clients LLC (dba Oratr).