Skip to content
TrySlides

Privacy Policy

Last updated: October 10, 2026

Prelaunch review draft. This notice describes the application's current data flows. Legal identification, retention schedules, and production-provider settings still require review before public launch.

1. Scope and contact

TrySlides is an independent presentation software project developed in the United States. This notice covers its website, editor, accounts, cloud synchronization, and shared presentations. It does not replace the notices that apply when you independently use Google, Polar, or another provider.

For privacy questions or requests, email support@tryslides.com.

2. Information used by the service

Account and profile information

Google sign-in through Supabase provides account identifiers, an email address, verification status, and available profile information such as your name and profile-picture URL. Authentication records include account creation and sign-in information. TrySlides also stores your application display name and username, which you can edit in Settings.

The application's sign-in flow does not ask for your Google password or request access to your Gmail messages, contacts, or Google Drive files.

Presentations and synchronization

The browser stores presentation titles, slides, text, images, drawings, editing history, and pending operations in account-scoped IndexedDB storage. For cloud-synchronized documents, TrySlides sends document content, required assets, revision and operation records, and synchronization identifiers to its servers. Storage usage and pending upload reservations are associated with your account.

New presentations attempt cloud synchronization automatically. Documents already marked local-only, including local imports and recovery copies, are not silently uploaded in bulk. If an upload is blocked or pending, a complete cloud copy may not exist.

When multi-device presence is active, private Supabase channels exchange session identifiers, the active slide or Step, selected element identifiers, and cursor position between sessions of the same account. This is separate from making a presentation available to another account through a share link.

Shared-link access and download records

When sharing is enabled, the service stores link settings, an optional recipient email, expiration and download permissions, and browser-visitor registrations. An opaque signed cookie recognizes a returning visitor; a general link does not require a Google account merely to view it. Restricted links and downloads have additional authentication requirements.

Shared downloads produce audit records containing the authenticated account identifier, link and presentation identifiers, revision, format, time, and authorization or delivery outcome. These records are available to the presentation owner. They record a request or delivery attempt, not proof that someone saved a file to disk. The audit endpoint exposes account identifiers, not a downloader's Google password or payment details.

Billing information

Opening checkout sends your account identifier, email, and selected language to Polar. TrySlides retains customer and subscription identifiers, subscription status, billing-period dates, cancellation status, and event-processing records to apply the correct account allowance.

Payment details are entered in Polar's checkout, not in a TrySlides card form. This integration does not store full payment-card numbers or card security codes in the TrySlides application database. Polar explains its payment-data handling in its Privacy Policy.

Support and technical information

If you contact support, the information you send can include your email, message, and any attachments you choose to provide. Send only what is needed for the request; never send passwords, access tokens, or full payment-card data.

The presentation-load diagnostic endpoint accepts only a fixed event name, error code, and error category. It does not accept slide text, document contents, account identifiers, or arbitrary error messages in that diagnostic payload. Hosting, authentication, and payment infrastructure can separately process connection information such as IP addresses, request times, and browser details. This notice does not claim that infrastructure logs contain no personal data.

3. Why the information is used

Information is processed to authenticate you, show your profile, save and restore your work, synchronize your devices, deliver the content you choose to share, apply storage and access limits, manage subscriptions, diagnose failures, and respond to support requests.

Local-only describes the storage of a presentation; it does not make use of the website anonymous or disable account, hosting, or diagnostic requests. The current application does not integrate advertising pixels or a third-party product-analytics SDK. Its editing flow does not send your slides to an AI model. These statements concern TrySlides itself, not the independent practices of Google, Polar, or other services you visit.

4. Cookies and browser storage

TrySlides uses browser storage for functional purposes:

  • Authentication cookies maintain and renew your sign-in session.
  • Locale and interface preferences can remember language, theme, or layout.
  • IndexedDB stores presentations, assets, history, and pending work on your device.
  • A shared-viewer cookie recognizes an admitted browser and helps enforce visitor limits when you open a hosted link.

You can manage cookies and site data in your browser. Blocking required cookies can prevent sign-in or shared-link access. Clearing site data can permanently remove unsynchronized presentations. Signing out leaves the local presentation database in place so that the same account can reopen its work later.

5. Service providers and people you share with

The configured service relies on these providers for the relevant features:

Their notices explain their own processing; they do not replace our responsibility for information managed through TrySlides. Production configuration and provider agreements must be reviewed before launch. This notice does not promise that every copy is stored only in the United States or in any particular country.

People who can open your share links receive the presentation content authorized by those links. General links can be forwarded. Revoking access cannot remove screenshots, displayed content, or previously downloaded copies. Presentation owners can access the download records described above.

6. Retention and deletion

Different information has different storage behavior:

  • Browser data: remains on the device until removed through the application, cleared in browser settings, or evicted by the browser. Signing out does not erase it, and we cannot remotely erase independent exported files.
  • Cloud documents and assets: server-confirmed deletion or withdrawal removes the active cloud document. Asset cleanup must preserve files still referenced by other presentations or pending operations. Lifecycle and retry-prevention records can remain after the active document is removed.
  • Shared-download audit records: the implemented access rule makes them available to owners for 90 days. Scheduled cleanup removes expired active database rows in batches; this is not immediate erasure from provider backups.
  • Account, billing, support, infrastructure logs, and backups: final retention and deletion schedules have not yet been established for launch. They are not covered by the 90-day download-audit rule. Contact support about the information associated with your account.

Canceling a subscription does not automatically erase presentations or close your account. Removing a cloud copy does not erase local copies on your other devices or files held by recipients. No universal immediate-deletion or fixed-day backup-erasure promise is made by this draft.

7. Your controls and requests

You can edit your display name and username, export your presentations, delete individual presentations, stop cloud synchronization, and revoke share links where those features are available. Subscription renewal is managed separately through the Polar billing portal.

To request access to personal information, correction, deletion, account closure, or a copy of account data, write to support@tryslides.com. There is currently no self-service account-deletion control. We may need to verify your relationship to the account before acting on a request. Do not send identity documents unless a necessary, appropriate verification method has first been agreed.

The rights and response requirements that apply depend on your location and applicable law. Nothing in this draft removes rights you have under that law. An editable presentation export is not necessarily a complete export of all personal information held by the service or its providers.

8. Security and shared devices

The application uses server-side account checks, owner-scoped database access, private asset storage, and authorization checks for shared deliveries. These measures do not guarantee absolute security or constitute end-to-end encryption. Cloud content is processed by the service and its infrastructure providers.

Local account separation is an application boundary, not encryption of the browser's database. Someone with access to your browser profile, device, or developer tools may be able to inspect local data. Use a trusted device and keep backups before clearing browser storage.

9. Children's information

The current release has no child-account, school-administration, or parental-consent workflow. Eligibility rules for minors and any handling of children's information require review before public launch. If you believe a child has provided personal information, contact support without including additional sensitive details in the initial message.

10. Updates and related terms

The date at the top identifies this version. Changes to features, providers, or data practices must be reflected in this notice; additional notice or consent may be required by applicable law. See the Terms of Service for local-storage limitations, subscriptions, sharing, and support.