Guruling

Privacy policy

In effect from

Guruling keeps the transcripts of YouTube videos for the people who ask for them. This page says what it stores about you, why, who else handles it, and how to have it removed.

Who runs Guruling

Guruling is a small, free service. We, its operator, are responsible for the personal data described here. Write to mail.interval@gmail.com about anything in this policy.

What we collect

  • Your Google account basics. When you sign in with Google we receive your email address, your name and the link to your profile picture. Supabase Auth keeps them with your account, with the times you signed in. For sign-in security it also keeps the IP address and browser of each session (in its session list and audit log), and the nightly database backups (kept 14 days) include them.
  • What you create. Your gurulings, the sources you add (channel, playlist and video links) and the video lists Guruling fetches for them (titles, descriptions, lengths, dates, which videos you hid).
  • Transcripts. The text of a video’s captions, fetched from YouTube by our server when you ask for it. See “Shared transcripts” below.
  • Usage counts. A record of each transcription, source added, source check and feedback message sent, with its time, so the hourly limits work.
  • What you tell us. The feedback messages you send, with the page you sent each one from, and the gurulings for which you asked to hear when talking opens. If you asked, we may send you one email at your Google address when talking opens.
  • Product analytics. Our own, with no cookies and no third-party scripts: a visit to the front page, starting to sign in, signing up, adding a source, a completed transcript, a .zip download, asking to hear when talking opens, sending feedback. Each event keeps its time, the page, the site that linked to it (its domain only) and any campaign tags in the link. To count visitors without knowing who they are, the server hashes your IP address and browser details together with a secret and the day’s date. The IP address and the browser details are never stored with the events. The hash changes every day, and without our secret it can’t be turned back into your IP address. When you are signed in, events are linked to your account.
  • Error reports. When something breaks, a report goes to Sentry: what failed, and technical details of the request, such as the page address, your browser and operating system, and possibly your IP address.
  • Server logs. The server and our providers keep ordinary technical logs (IP address, time, the address requested) to keep Guruling running and secure.

Why, and on what basis

  • To run the service you signed up for: your account, gurulings, sources, transcripts and the .zip download. The basis is our agreement with you, the Terms of use.
  • To keep it fair and safe: the hourly limits, preventing abuse, server logs and backups. The basis is our legitimate interest in running a reliable service.
  • To understand what people want from Guruling: analytics, feedback and interest in talking to a guruling. The basis is our legitimate interest; the data is kept small, and you can object.
  • To find and fix errors: error reports. The basis is our legitimate interest.

We don’t sell your data or use it for advertising.

Who else handles it

  • Supabase stores the database and runs sign-in.
  • DigitalOcean hosts the server that runs Guruling, its logs and the daily database backups.
  • Google signs you in with your Google account.
  • Webshare is the proxy network our server uses to reach YouTube. Those requests carry only video, playlist and channel addresses, never anything about you.
  • Sentry receives the error reports.
  • YouTube serves the video thumbnails straight to your browser, so YouTube sees your IP address when a video list is shown.

Some of these providers process data outside your country, including in the United States. They do so under their own data processing terms, which include the EU Standard Contractual Clauses where those apply.

Shared transcripts

A transcript is the text of a video’s public captions. Guruling stores it once per video and language, and everyone who adds that video reads the same text. It carries nothing about who fetched it, and it stays when your account is deleted: it is the video’s text, not your data. Your gurulings, sources and lists are yours alone; other users never see them.

How long we keep it

  • Your account and everything you created: until you delete the account.
  • Deleting it (Delete account on your Profile page) removes your account, gurulings, sources, video lists, usage counts and any request to hear when talking opens, all at once.
  • Feedback and analytics events are kept after that, without the link to your account.
  • Analytics events are deleted after 13 months.
  • Daily database backups are kept for 14 days, so deleted data is gone from them within 14 days.
  • Server logs and error reports are kept for a short time, then deleted.

Your rights

You can ask to see the data we hold about you, to correct it, to delete it, or to get it in a portable form. You can object to the processing we base on legitimate interest, such as analytics. And you can complain to a data protection authority, for example the one where you live or work.

Much of this you can do yourself: Download as .zip gives you your transcripts, and Delete account on your Profile page removes everything tied to you. For the rest, write to mail.interval@gmail.com. We answer within one month.

Cookies

Guruling sets only the cookies that keep you signed in (Supabase’s session cookies). They are strictly necessary. There are no advertising or tracking cookies. Your browser’s local storage also keeps your theme choice and the state of your transcription queue on your device.

Children

Guruling is not meant for anyone under 16. If you are under 16, please don’t create an account; if we learn that a child has one, we delete it.

Changes to this policy

When this policy changes, the new version appears on this page with a new date. If a change matters for how your data is used, we’ll say so in the app before it applies.