Privacy policy

What Glideshow keeps. When you sign in with GitHub: your GitHub user id, username and name. When you sign in with Google: your Google account id, name and email address. These go into a signed cookie in your browser (your session, for up to 90 days), not into a database of users. For someone who keeps decks here, Glideshow also remembers which GitHub repo holds them and their recently opened decks. Signing in with GitHub also gives Glideshow a GitHub token, good for 8 hours, which it uses only to list the repos you install it on while you set up; it's deleted once you've chosen one, or when it expires.

Your decks. Decks live where their owner keeps them: in a GitHub repo, which Glideshow reads and writes through its GitHub App, only in the repos the owner installed it on; or in a Glideshow folder in the owner's Google Drive, where Glideshow has Google's drive.file access: it can see and change only the files it created, nothing else in your Drive. To save while you're away, it keeps a Google access token for that, which you can withdraw anytime at myaccount.google.com/permissions. Unsaved changes wait briefly on Glideshow's servers (Cloudflare) and are then written to your repo or Drive. Decks made without an account (Start a deck) stay in your browser's own storage on your device and never reach Glideshow's servers; Glideshow sends only its own pages and code to your browser.

Sharing and comments. A deck's owner decides who can open it (anyone with the link, or the email addresses and GitHub usernames they list). If you comment on a shared deck, your comment, your name and your email address or GitHub username are saved with the deck in its owner's repo or Drive, where the owner (and anyone with access to it) can see them. Other people opening the deck see commenters' names only.

Reports. If you report a shared deck, Glideshow keeps the report with your IP address and, if you give it, your email address, so the person running Glideshow can review it; reports are deleted once dealt with.

What Glideshow doesn't do. No ads, no tracking or analytics cookies, no selling or sharing of your information, and no use of your decks or comments to train AI models. Search engines and AI crawlers are asked to stay out (robots.txt and noindex, noai headers).

Google user data. Glideshow's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements: it is used only to sign you in and to keep your decks in your Drive, never for ads, never sold, and never read by people except to keep the service secure or at your request.

Services used. Cloudflare hosts Glideshow and keeps routine request logs (including IP addresses), and Glideshow's own error logs, for a few days; GitHub holds the decks; Google and GitHub handle sign-in. Their own privacy policies apply to them.

Your choices. Sign out anytime; remove the Glideshow app from your GitHub account (Settings → Applications) to cut its access to your repos; ask a deck's owner to delete your comments, or delete them yourself. Questions or deletion requests: heyodogo@gmail.com.