Effective date: 24 October 2026
Seckin Yasar (“we”) operates Skip to the Point, the website at https://skiptothepoint.app, the browser extension, and the account that goes with them. Together, that is the Service. This Privacy Policy explains what personal data the Service collects, why it is used, and who receives it.
Use of the Service is also covered by the Terms of Service and the Refund Policy. If you are in Türkiye, the KVKK Aydınlatma Metni is the notice required by Turkish Personal Data Protection Law No. 6698.
Seckin Yasar is the controller of personal data held by the Service. Paddle is a separate controller of the personal data collected in checkout. We do not store your card number or other payment credentials.
1. What this Privacy Policy covers
This policy covers personal data we gather when you use the Service. Personal data means information that identifies or relates to a particular person, including information described as personal data under the GDPR and under KVKK.
This policy does not cover companies we do not control. Checkout is one of those cases. Paddle.com is the Merchant of Record for paid plans. Paddle collects the email address, the billing country, a postal code where that country requires it, and the payment method, inside a checkout frame that Paddle hosts. That payment data is governed by the Paddle Privacy Policy. The Paddle entity named on the receipt is the seller of record for that purchase.
2. Personal data we collect
The categories below are the personal data the Service collects. The account database is stored by Cloudflare. Payment card details are not in it.
Profile or contact data
Examples of personal data we collect
- Name
- Email address
- Whether the email address has been verified
- Profile image
Categories of third parties with whom we share this personal data
- The sign-in provider you choose (Google, GitHub, or Discord)
- Amazon SES, to deliver the sign-in code
- Paddle, the email address only, so checkout can open for that account
Authentication data
Examples of personal data we collect
- Session token
- The account identifier returned by Google, GitHub, or Discord
- OAuth access, refresh, and ID tokens, stored encrypted
- A one-time sign-in code, kept until it expires
- A hash of the code used to connect the extension
Categories of third parties with whom we share this personal data
- The sign-in provider you choose
- Amazon SES, for the sign-in code
- Better Auth, for the sign-in security check (visitor id, IP address, approximate location, browser, and user id)
Device and IP data
Examples of personal data we collect
- IP address of a session
- Browser of the session
- Browser name and version of an extension installation
- Operating system name and version
- Device type
- The most recent IP address seen for that installation
Categories of third parties with whom we share this personal data
- Cloudflare, which hosts the Service and sees the IP address of a request
Analysis data
Examples of personal data we collect
- YouTube video identifier
- The skip result
- The status of the analysis
Categories of third parties with whom we share this personal data
- OpenAI, which receives the transcript as timed cues in order to produce the skip result. We do not store the transcript text.
Plan and billing identifiers
Examples of personal data we collect
- Plan name and token balances
- Subscription status and the current billing period
- Paddle customer id, subscription id, and transaction id
Categories of third parties with whom we share this personal data
- Paddle, as the separate controller of checkout. We do not send Paddle a card number.
Web analytics
Examples of personal data we collect
- Pages viewed and the referring page
- Clicks, scrolling, and other interactions on a page
- Browser and device type
- Approximate location derived from the IP address
- A session recording of how a page was used, from Microsoft Clarity
Categories of third parties with whom we share this personal data
- Cloudflare Zaraz, which forwards the event to Google Analytics 4 and Microsoft Clarity
- Google, for Google Analytics 4
- Microsoft, for Clarity
- Cloudflare, for Cloudflare Web Analytics, which does not use a cookie
Correspondence
Examples of personal data we collect
- The content of an email you send us
- The email address you send it from
Categories of third parties with whom we share this personal data
- None. The message stays in the support inbox. It is not written to the account database.
Sources
- You, when you create an account, connect the extension, start an analysis, or email us.
- Automatically, from the website, the extension, and the cookies described below.
- Google, GitHub, or Discord, when you use that sign-in.
- Paddle, which returns billing identifiers after checkout. Paddle does not return your card number to us.
What we do not collect
- Card number, CVC, or the full billing address.
- A password. Sign-in is OAuth or a one-time code.
- The transcript text. It is sent to OpenAI and is not stored by us.
- We do not aim to process special category data, such as health, religion, biometrics, or political opinions. The identifier of a video you ask us to analyze can indirectly suggest information of that kind.
3. How we use personal data
- To create the account and keep the same person on that account.
- To analyze a transcript you ask us to analyze, and to show that analysis history on the account.
- To start, renew, or end a paid plan from the billing identifiers Paddle sends.
- To keep sessions secure and to limit abuse.
- To answer a message you send us.
- To understand how the website is used, through Google Analytics 4, Microsoft Clarity, and Cloudflare Web Analytics.
- To keep a record needed for a refund, a chargeback, or a legal claim.
We do not sell personal data, and we do not use it for advertising. We do not use the transcript to train a model of our own. We will not collect a new category of personal data, or use personal data for a materially different purpose, without posting a notice in this policy.
6. Security and retention
OAuth tokens are encrypted at rest. Access to an account depends on the signed-in session. No method of sending or storing data is perfectly secure.
- The account, the analysis history, and the billing identifiers stay while the account is open.
- A session lasts up to 7 days.
- A sign-in code lasts 5 minutes.
- An extension installation stays until you revoke it or it expires.
- Cloudflare Web Analytics keeps raw measurements for about 7 days, then a sampled aggregate for about 6 months. The beacon discards the IP address at the nearest Cloudflare data center.
- Microsoft Clarity keeps a session recording for 30 days. Click and heatmap aggregates are kept for 9 months.
- Google Analytics 4 is kept for the retention period set on that property. Google states that it does not store the IP address in Analytics reports.
- Amazon SES delivers the sign-in code. It does not keep a mailbox of that email. Sending and bounce logs stay with Amazon.
- Paddle keeps checkout and invoice records under the Paddle Privacy Policy.
After you ask us to delete the account, that data is deleted. A record still needed for a refund, a chargeback, or a legal claim is kept, and the rest is deleted.
7. Children
The Service is not directed at anyone under 18. We do not knowingly open an account for a person under 18. If we learn that we have, we delete it. Email support@skiptothepoint.app if you believe that has happened.
8. Your rights
You can ask what we hold, ask for a correction, ask for a copy, ask us to restrict or stop a use, or ask for the account and the analysis history tied to it to be deleted. Email the address in section 11. A privacy request is answered within 30 days. We may ask you to confirm that the request comes from the account holder.
For personal data held by the Service, the lawful bases are the contract (the account, the sign-in code, the analysis, and the paid plan), legitimate interest (security, abuse limits, and cookieless measurement of the site), and a legal obligation or the establishment of a right where a record must be kept for a refund, a chargeback, or a claim.
The skip result does not decide a legal right. If you are in the EEA, the United Kingdom, or Switzerland, you can also complain to your supervisory authority. A question about payment data that only Paddle holds should go to Paddle, under the Paddle Privacy Policy.
We do not sell personal data.
9. Türkiye and KVKK
If you are in Türkiye, Seckin Yasar is the veri sorumlusu for personal data held by the Service. The notice required by KVKK article 10 is the KVKK Aydınlatma Metni. It states the purposes, the legal bases, the parties who receive the data, transfers outside Türkiye, and the rights in KVKK article 11.
Those rights include learning whether we process your personal data, asking for a correction or deletion, learning who received it, objecting to a result that is produced solely by automated analysis and is against you, and claiming compensation where processing was unlawful. You can use them by emailing support@skiptothepoint.app. You can also complain to the Personal Data Protection Authority (Kişisel Verileri Koruma Kurulu).
10. Changes
We post changes on this page with a new effective date. The version on this page is the one in effect. If you keep using the Service after that date, the updated policy applies.
11. Contact
Seckin Yasar
support@skiptothepoint.app
A question about the Service, or a privacy request, goes to that address. A privacy request is answered within 30 days. A question about a charge, or a refund, goes to Paddle.