Legal & Data Ethics

Privacy Policy

Last updated: 30 October 2026 · Effective date: 30 October 2026

1. Overview

Presentable (“we”, “our”, or “us”) provides an AI-assisted presentation workspace designed to help presenters structure clear stories, draft speaker notes, and create or update presentation decks in Google Slides. We are committed to transparency in our data practices and respecting your privacy.

This Privacy Policy explains how information is collected, used, disclosed, and secured when you use our web application at presentable.work.

2. Google User Data and Permissions

Presentable connects with Google APIs to allow you to import existing Google Slides decks or export newly generated presentations directly into your Google Drive. When you choose to connect your Google account, we request the following specific scope:

https://www.googleapis.com/auth/drive.file

What this means: We request per-file access only. Presentable can only view and modify Google Slides files that you explicitly select using the Google File Picker or presentations created directly by Presentable. We cannot see, browse, search, or read your entire Google Drive or any unrelated documents.

How we use Google user data:

  • To read slide element structures, headlines, and notes from presentations you select to assist in outline and note editing.
  • To write structural updates, generated titles, bullet points, and speaker notes back to your authorized Google Slides presentations.
  • To display slide previews within the Presentable workspace so you can review changes before presenting.
  • When you ask the slide assistant for help, to send that slide’s preview picture, its text, speaker notes and layout to our AI provider so it can suggest a change. Nothing in your deck changes until you review and apply the suggestion.

3. Google API Services User Data Policy (“Limited Use”)

Presentable’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.

  • We do not use Google user data to serve targeted advertisements.
  • We do not sell Google user data to data brokers, advertisers, or any third parties.
  • We do not allow human workers to read your private slide content unless you give us affirmative agreement for technical troubleshooting, it is required for security audits, or we are legally obligated to do so.
  • We do not use your Google user data to train or fine-tune generalized machine learning or artificial intelligence models.

4. Other Information We Collect

Account Information: When creating an account, we collect your email address and authentication credentials via Supabase Authentication.

Google Sign-In: If you sign in with Google, we receive your name, email address and profile picture from Google to create and identify your account. Signing in with Google does not give Presentable access to your Google Drive; that is the separate Google Slides connection described above.

Usage Records: When you use AI help, research, uploads, deck creation, slide thumbnails or editing actions such as applying or undoing a change, we record which feature you used and when, linked to your account. For AI provider calls, we also record the provider, model, token and search counts, outcome and a cost estimate using the price snapshot for that call. This cost record does not include your prompt or the AI’s reply. We use these records to enforce usage limits, understand feature use and estimate the cost of providing each feature. We remove usage records older than 90 days the next time you use one of these features, so if you stop using Presentable, your last records stay until you return or delete your account. We remove cost records older than 90 days whenever new AI costs are recorded.

Product Analytics: Product analytics are on by default after signing in. You can turn them off directly in the analytics notice. Your choice is saved to your account and applies when you sign in on another browser. You can change it under Usage analytics in Profile (also available from Settings). Turning analytics off stops collection and discards pending browser analytics; it does not delete events already sent. Essential credit balances, transactions and provider-cost records continue separately, excluding prompts, notes, slide content and AI replies. While analytics is enabled, we collect data about how you interact with Presentable, such as the features you use, time spent, technical errors, and any feedback you voluntarily submit. This helps us identify slow or confusing areas of the application.

What We Do Not Collect: We never record your screen, nor do we collect your name, email, notes, prompts, or slide content within our analytics events.

How Data Is Processed: Analytics events use a randomized attempt ID. While analytics is enabled, new attempts also carry a dedicated pseudonymous account reference so we can recognize the same account with analytics enabled across visits. This is not anonymous data: our server can derive the reference from your account. Measurement starts after sign-in unless you have opted out; a first measured visit is not your signup date, and older attempt-only events are not linked retroactively. Turning analytics off stops new collection here and saves your account preference for future visits. Other open browsers apply it when their account session refreshes. Signing out clears the active analytics attempt. Separately, when you use usage-limited features (such as AI assistance, web research, file uploads, or deck creation), a unique reference code is attached to the event. This allows our internal team to cross-reference usage and cost logs to troubleshoot issues or review feedback attached to your account.

Third-Party Providers: We send these metrics to PostHog (US Cloud) for review. Event data is retained in accordance with our operational needs and PostHog’s data storage policies. Your browser may also temporarily cache event data in your current tab to retry failed uploads.

User Inputs and Research Notes: Presentation outlines, speaker notes, and assignment briefs you submit to generate or refine slides.

Operational Logs: Technical error diagnostics and aggregated performance metrics needed to maintain service stability and prevent abuse.

5. Data Storage, Encryption, and Security

We take rigorous technical and administrative measures to protect your information:

  • Token Encryption: Google OAuth refresh tokens are encrypted at rest using AES-256-GCM before storage in our service-role-isolated database.
  • Transmission Security: All communications between your browser, our servers, and external APIs are encrypted in transit via Transport Layer Security (TLS/HTTPS).
  • Access Controls: Database tables holding user presentations enforce Row Level Security (RLS) policies so presenters can only access their own data. Project team members with owner access can look up one account at a time to run usage limits and help with support. The lookup shows the account’s email address, when it was created, how it signs in (for example email and password, or Google), when it last signed in, whether its email is confirmed, its feature use and its estimated AI provider costs. It does not show presentations, notes, prompts or slide text.

6. Data Retention, Revocation, and Deletion

You can disconnect Google, delete a team Library you own, or delete your Presentable account:

  • Disconnecting Google: Disconnect Google in Profile to remove the token stored by Presentable. We also attempt to revoke Presentable’s Google access. If Google cannot be reached, you can revoke that access yourself using the link below. Your Drive files and their sharing permissions stay unchanged.
  • Revoking Google Permissions: You can revoke Presentable’s access directly in your Google Account at https://myaccount.google.com/permissions.
  • Deleting a Team Library: In Library, open Manage Libraries, select a Library you own and choose Delete Library. After confirmation, the Library, its Collections, memberships and invitations are permanently removed. Resources return to their individual owners’ personal Libraries. Access inherited from the deleted Library ends; direct sharing of individual resources stays.
  • Account Deletion: In Profile, open Account security and choose Delete account. Enter the verification code emailed to your account’s address, then type DELETE to confirm. This permanently removes your account and the Presentable resources and uploads you own, including resources you shared with others. People lose access to those deleted resources. Any team Libraries you own are also deleted, while other owners’ resources are preserved as described above. Account deletion also disconnects Google. Your Google Drive files and their permissions stay unchanged.
  • What Deletion Does Not Remove: Edits you made in presentations other people own, retained notes history, and material they already captured or copied stay with their work. Contributions from your deleted account are attributed to Deleted user in retained notes history. Copies in backups, email-delivery records and our service providers’ logs follow those providers’ own retention. Analytics records already sent to PostHog, including their pseudonymous account reference, stay there; account deletion does not delete those events. Your usage and cost records are deleted with your account.

7. Third-Party Subprocessors

We work with reputable infrastructure partners to deliver our application:

  • Supabase: Cloud database, authentication, and encrypted storage.
  • Railway: Hosting for our web application and servers.
  • Cloudflare: Domain and network service for presentable.work. Requests to our website pass through Cloudflare on their way to our servers.
  • PostHog (US cloud): Product analytics, only when measurement is enabled. It never receives your name, email, raw account ID, notes or slide text. New attempts with analytics enabled carry a pseudonymous account reference, and some events also carry a cost reference that our team could link to your account, as described under Product Analytics above.
  • Google Cloud & Google Slides APIs: OAuth authentication and slide document sync.
  • AI Providers: Language models used only when you ask for AI help: to generate structured outlines, draft speaker notes, review slides and suggest slide edits. For slide edits, the AI provider receives a picture of the slide along with its text, notes and layout. Prompts are not stored for model training.

8. Changes to This Privacy Policy

We may periodically update this policy to reflect changes in our service or legal requirements. Material modifications will be reflected with an updated date at the top of this page.

9. Contact Us

If you have questions or concerns regarding this Privacy Policy or our data handling practices, please contact us at:

Presentable Team

Email: [email protected]