Kinreader
Privacy Policy
Effective September 8, 2026
This policy explains how Kinreader handles information when you use kinreader.com and app.kinreader.com. “Kinreader,” “we,” and “us” mean the Kinreader service. Questions or privacy requests can be sent to tam@repurgo.com.
Information you provide
When you create a listening item, we receive the URL, text, or file you submit. We may extract the readable text and related page details such as a title, author, or image. We create narration audio and word timing data so the reader can play and highlight the item.
If you create an account, we receive the account information needed to sign you in, including your email address, name if supplied, authentication identifiers, and session information. You may sign in with email or Google. A Google sign-in also involves the information Google supplies to complete that sign-in.
If you contact us, we receive the information in your message. If you start a paid subscription, Stripe collects the payment information used for Checkout. Kinreader receives subscription and customer information needed to provide and manage the plan; we do not see your full payment-card number.
Browser extension
The Kinreader extension reads the article or selected text in your active tab when you ask it to. It shows a local preview, then transfers the text, title, author, cleaned source URL, capture time, and capture details to the signed-in Kinreader app after you confirm. The app saves a private copy to the account you choose. The extension does not request or copy publisher cookies, passwords, form values, or publisher page storage.
Pending captures and the chosen account ID stay in extension session storage. They expire for retrieval after 30 minutes and are removed after a successful save acknowledgement, cancellation, browser exit, or the next access after expiry. The app stores temporary transfer details and a save receipt in its tab session storage, without the article body.
Saving a clip does not generate audio or send its source URL to extraction providers. If you choose Listen, Soniox processes the saved text to create narration. Convex and Cloudflare store and deliver the private text and audio. Clip text and audio do not have public sharing links.
Information created by use
We process information needed to run the service, such as saved items, listening position and progress, chosen voice and reader settings, subscription status, and service or security records. Hosting and security services may also receive technical request information such as IP address, browser details, and request data. The app stores some information in your browser, including your local library, settings, a browser-specific identifier used to apply service limits, and temporary context used during an upgrade. You can remove browser-stored information through your browser settings, though that can remove saved local progress.
When you share an item, the recipient can use the link you send to open that item. Share links may carry the source URL or information needed to display the shared item. Do not share a link if you do not want the recipient to access that material.
How we use information
We use information to provide the reader, extract and prepare submitted material, generate and deliver narration, maintain your library and progress, authenticate accounts, process subscriptions, respond to requests, prevent misuse, and keep the service operating. We may also use information where needed to comply with law or resolve disputes.
Submitted material is processed to provide the feature you ask for. Please do not submit material you are not allowed to access, use, or share.
Service providers and disclosures
We use providers that process information for their role in the service. Our service providers include:
- Cloudflare, which supports hosting, request processing, content delivery, audio delivery, and document processing.
- Convex, which supports the application backend, database, and stored audio.
- Soniox, which processes submitted text to create narration and timing data.
- Monid and Jina Reader, which may receive a submitted source URL when they help extract readable material from a page.
- FxTwitter, which may receive a submitted X post URL to retrieve post material.
- Stripe, which processes subscription Checkout and customer billing management.
- Google, if you choose Google sign-in, and Google Fonts, which this site loads for its typography.
- AutoSend, which delivers sign-in and service emails.
These providers may process information under their own terms and privacy notices. We may also disclose information when reasonably necessary to protect the service, respond to a valid legal request, or address fraud, security, or a dispute.
Retention and your choices
Deleting a saved browser clip removes its text and library entry and starts cleanup of its generated audio. Audio file cleanup runs in the background. We retain billing and service records that do not contain the deleted article text, and a non-content deletion marker prevents old audio jobs from restoring deleted files. Deletion cannot remove copies you already downloaded or material kept by the original publisher.
We keep information for as long as reasonably needed to provide the service, operate and secure it, meet legal obligations, and resolve disputes. The period can vary by the information and the request. You may ask about access to, correction of, or deletion of personal information by emailing tam@repurgo.com. We will consider and handle requests under applicable law, subject to information we need to retain for legitimate operational, legal, or security reasons.
Depending on where you live, you may have additional privacy rights. You may also raise a concern with the privacy regulator in your place of residence where that right applies.
Security, children, and changes
We use reasonable safeguards designed to protect information, but no online service can promise complete security. Kinreader is not directed to children. If you believe a child has provided personal information, contact us at tam@repurgo.com.
We may update this policy as the service changes. We will post the updated version here and revise its effective date.