Privacy Policy

1. Who this is about

Slidr is operated by Michael Chen, an individual. This policy explains what data Slidr collects when you use the app or connect an AI agent to it, why, and how to have it removed. Questions go to support@michaelchen.me.

2. What we collect, and why

• Google account identity. When you sign in with Google, we store your Google account ID, email address, display name, and profile picture. This is how sign-in works — it's how we recognize you on your next visit and how an agent you've authorized is tied to your decks.
• Deck content. The slides, text, and layout you or your agent create — including full edit history — is stored so the deck exists and can be edited, presented, and exported.
• Uploaded and imported images. Images you paste, upload, or ask your agent to import (including images found via stock-photo search) are stored as part of your deck.
• Usage counters. We keep a running count of how many decks you own, which is what enforces the plan limit (see /pricing/). We also keep a daily count of some expensive operations — slide screenshot renders, and calls the app makes to our payment provider on your behalf. Those counts are not plan limits and are not billed to you: they exist only to stop a runaway loop from degrading the service, and they reset each day. None of these counters is used for anything else.

We don't collect payment card details ourselves — see "Payments," below.

3. Who we share it with

We use a small number of processors to run the service. We don't sell your personal data, and we don't run advertising.

• Cloudflare — hosts the application and stores your data: deck content and edit state (Durable Objects), account and usage records (D1), and uploaded images (R2 object storage). Slide screenshots are rendered using Cloudflare's headless Browser Rendering. As our host, Cloudflare also necessarily processes request metadata — including your IP address — for every request the service handles, the same way any host does.
• Google — provides sign-in (OAuth). Google issues the identity claims described above; we don't receive your Google password.
• Pexels — powers in-app stock-image search. If you or your agent search for a stock photo, the search text is sent to Pexels to return results.
• Paddle — processes payments and acts as merchant of record for the Pro plan (see /pricing/). Checkout runs through Paddle's own hosted overlay: Paddle collects your payment details directly, calculates and remits applicable sales tax/VAT, and is the party you're billed by — we never see or store your card number. We hold a Paddle-issued customer and subscription identifier and your subscription status so the app can tell what plan you're on; that's the only billing data we keep ourselves.

On AI providers: Slidr does not currently send your deck or slide content to Anthropic or any other AI provider. An in-app AI assistant panel exists in the code but is disabled for every account — the feature is dark and its endpoint refuses all requests. If that ever changes, this policy will be updated first, and Anthropic (or whichever provider is used) will be added to this list before the feature is turned on for anyone.

4. Cookies

We set three cookies, and all three are strictly necessary — none are used for tracking, analytics, or advertising, and we don't run any analytics or advertising scripts on this site.slidr_session keeps you signed in. slidr_oauth_state and slidr_return exist only during a Google sign-in redirect — they prevent a forged callback and send you back to the page you started from — and expire within ten minutes whether or not sign-in completes.

5. Sharing your decks

Decks are private by default. If you mint a share link for a deck, that link becomes readable by anyone who has the URL — it is unlisted, not access-controlled, though we mark shared pages so search engines don't index them. Minting and revoking a share link is entirely your choice, made from the editor or dashboard; revoking it immediately stops the share link itself from resolving. That revocation does not reach individual image URLs from the deck — those are separate, unauthenticated URLs, and anyone who already copied one (from that deck or any other) can keep loading it after you revoke the share link, the same way it keeps working after you delete the deck (see "Retention and deletion," below).

6. Retention and deletion

We keep your account and deck data for as long as your account exists, so the service keeps working. Here's what actually happens when you delete things:

• Deleting a deck removes it from your dashboard and permanently wipes its editable content immediately. Images that were attached to that deck are not guaranteed to be erased at the same moment — cleaning up the underlying image storage for a deleted deck is a known gap we haven't closed yet. Nothing in the app links to those images anymore once the deck is gone. But if someone already has a direct image URL — copied from the page, saved, or shared elsewhere — that URL is not tied to the deck's existence: it will keep working and keep serving the file until we purge it from storage, which today is not on the same timeline as the deck's own deletion.
• Deleting your account. There's no self-serve "delete my account" button yet. Email support@michaelchen.me and we'll delete your decks, images, and identity record by hand.

7. No sale, no advertising

We do not sell, rent, or trade your personal data. We do not use it for advertising, and we do not build advertising profiles from it.

8. Your rights

You can ask us what data we hold about you, ask us to correct it, or ask us to delete it, by emailing support@michaelchen.me. This policy is governed by the laws of Taiwan, including the Personal Data Protection Act. If you are in a jurisdiction whose data-protection law gives you additional rights, we will honour those rights as well — write to the same address.

9. Changes to this policy

We may update this policy as the service changes. The "last updated" date above reflects the latest revision.