Privacy Notice
Last updated: 2024-07-30
Your privacy is important to us. WebInk provides a Chrome extension and web tools at webink.app that convert web pages and HTML into clean Markdown. This notice describes what we collect, why we collect it, and the choices you have when you use our website, API, and browser extension.
1. Information we collect
We collect information only when it is needed to operate WebInk, improve the product, or fulfill a transaction you initiate. Depending on how you use WebInk, this may include:
- Extension and conversion activity: When you convert a page, processing generally happens in your browser for the extension workflow. We do not need to store the full text of every page you clip unless you explicitly use a server-side feature (for example, the URL-to-Markdown tool or API), in which case we process the URL or content you submit to return Markdown.
- Account information: If you sign in on the website, we receive basic profile and authentication data through our identity provider (Clerk) and may store account-related records in our application database (Supabase) to sync subscription status with the extension.
- Payment information: Paid plans are processed by our payment partner (Paddle). We receive order and subscription status, not full card numbers stored on our servers.
- Usage and diagnostics: We may collect aggregated analytics on website traffic and error logs to keep services reliable and secure.
2. How we use your information
We use collected information to:
- Provide, maintain, and improve the extension, tools, and API
- Authenticate users and manage subscriptions
- Process payments and send transactional messages
- Respond to support requests and product feedback
- Detect abuse, fraud, and security incidents
3. Sharing and processors
We do not sell your personal information. We share data with service providers that help us run WebInk (hosting, authentication, payments, and analytics) under contracts that require them to protect your data and use it only to deliver services to us.
4. Data retention
We retain information for as long as your account is active or as needed to provide the service, comply with legal obligations, resolve disputes, and enforce our agreements. Server-side conversion logs, if any, are kept only for operational periods required to run and secure the service.
5. Your rights
Depending on your location, you may have rights to access, correct, delete, or export personal data we hold about you. To exercise these rights, email xianger94@gmail.com. We will respond within a reasonable time.
6. Changes
We may update this Privacy Notice from time to time. We will post the revised notice on this page and update the "Last updated" date. Continued use of WebInk after changes become effective means you accept the updated notice.
What this means in practice
The notice above is the policy. The notes below describe what the current code does with a page, an account, and a payment. They are not a replacement for the notice, and they do not add a right, a duty, or a limit.
Extension capture stays in the browser
Converting, editing, copying, and downloading from the side panel happen on the machine where Chrome is running. The content script clones the document, keeps the article with Defuddle, and converts that HTML with the extension’s Turndown rules. That path does not post the article to WebInk. Send to AI is a separate handoff: the extension opens the assistant’s site with the prompt in the address, or copies the prompt to the clipboard for you to paste.
When text does leave the browser
Translate and AI Fix run only after you click them. Translate sends the article Markdown and the language you picked. AI Fix sends the text currently in the panel. Both reach a WebInk server procedure, which calls an OpenAI-compatible model — the model id in the code is gpt-5-nano — and streams the result back. Those procedures do not insert the submitted text into the subscription table.
Submitting a public URL on the URL tool, on a tool’s URL mode, or through the developer API makes the server fetch that address. The fetch allows http and https only, blocks names that resolve to loopback, private, or link-local addresses, times out at 15 seconds, and stops at 10 MB. The handler writes the URL to the server log and returns Markdown. It does not insert the article into the subscription database.
Accounts, payments, and diagnostics
Website sign-in is Clerk. The header shows Clerk’s sign-in button, and Clerk’s account button once you are signed in. Paddle handles checkout. Its webhook stores a subscription row with a user id, an email, the Paddle subscription id, a price id, a status, and the current period. That table has no column for a card number.
The website initializes Google Analytics 4 with the configured measurement id and sends a page view that includes the path and the document title on each view. Sentry is initialized for the browser, the server, and the edge runtime, with the trace sample rate set to 1. An unknown URL also sends Sentry a warning that includes the path. The API is mounted with Vercel’s Node adapter, and social preview images are rendered with Vercel’s image library.
Extension storage, and how to ask
Template text, prompt text, and the platform list use Chrome’s local extension storage. TOC options, Markdown style, Prettier, the theme, the selected template, editor mode, the active side-panel tab, the translation language, the selected AI platform, and whether the send panel is expanded use Chrome’s sync storage area. Chrome can copy the sync group to the user’s other browsers when Chrome Sync is on. Removing WebInk from chrome://extensions removes that profile’s extension storage.
To ask for access, correction, deletion, or export, use the email in section 5. The contact page points at the same address and lists what helps us find the right record. This note does not set a retention period. Retention is the section in the notice above.