Privacy Policy

1. Who is responsible for your data

WebBites is operated by Elias Ruiz Monserrat ([NIF — to be filled in]), [street, postcode, city] — Spain. We are the data controller for the processing described here. You can reach us at contact@webbites.io — a person reads it, and it is also the address for any request about your data.

We are a small operation based in Spain, so the GDPR (Regulation (EU) 2016/679) and the Spanish LOPDGDD apply to everything below. We are not required to appoint a Data Protection Officer and have not appointed one; write to the address above instead.

This policy covers the website and web app at https://www.webbites.io, the WebBites apps for iPhone, iPad, Mac, Apple Vision Pro, Apple TV and Apple Watch, the share and Safari extensions, the browser extension, and the public API.

2. Using WebBites without giving us anything

The native apps work signed out. In that mode there is a local library on your device: bites, collections, tags and your view preferences are kept in the app's own storage, and none of it reaches our servers. There is no account, so there is nothing for us to hold.

Two things are worth being precise about, because "offline" is a word people stretch:

• Saving a link fetches that link. When you save a page, your device asks that website for its title, description and image, exactly as your browser would. That request goes to the site you chose to save, not to us, and it carries whatever a normal web request carries (your IP address, for instance). If you want none of that either, save while offline or turn on Airplane Mode: the bite is stored with what you typed.
• Where the thinking happens is a setting. Search and the read-it-for-me step at save time can run on-device (Apple's own models, nothing leaves the device) or in the cloud (see §5). Pick on-device in Settings → Intelligence and your content is not sent anywhere for that either.

The exception, stated plainly: the apps send crash and performance reports (a stack trace, the OS version, the device model — no bookmark contents) to our own error-tracking server, which we run ourselves on our own infrastructure. It is not a third-party analytics product and there is no advertising identifier involved. We do not run any usage analytics inside the native apps.

The web app is the other case: it is an account product and needs our servers to do anything at all.

3. What we collect when you do have an account

Account data

Your email address, your username or display name, a password hash (never the password itself), your language and app preferences, and the dates your account was created and last used. If you sign in with Apple and choose to hide your email, we get Apple's private relay address and that is all we ever have.

Your content

Everything you save and everything the service derives from it so it can be found again: URLs, titles, descriptions, notes, annotations, tags, boards and collections, highlights, drawings, uploaded files and PDFs, screenshots and images, extracted article text, RSS feeds you follow, and AI-generated summaries, tags and search embeddings.

Technical and usage data

IP address, browser or device type and OS version, and server logs of the requests your client makes (endpoint, timestamp, response status). We use these to keep the service up, debug it and stop abuse — not to build a profile of you.

Billing data

If you subscribe, we store your plan, its status and renewal date, and the customer or transaction identifier from the payment provider. We never see or store your card number. Card details go straight to Stripe (on the web and Mac) or to Apple (for in-app purchases), who are the ones processing the payment.

Things you send us

Support emails, feedback and feature requests posted in the app, and anything you choose to include in them.

4. Why we process it, and on what legal basis

We do not deliberately collect special-category data (health, beliefs, biometrics and the rest). You can of course save a page about anything you like; we treat the contents of your library as private either way and do not analyse it beyond what is needed to show, enrich and search it for you.

5. AI features

With an account, WebBites can summarise a page, suggest tags, answer questions about your library and build the embeddings that make semantic search work. To do that, the relevant text — the page content, your query, and the metadata around it — is sent to our AI providers, OpenAI and Anthropic, over their business APIs.

• They act as our processors, under their API terms: content sent through those APIs is not used to train their models.
• We send what the feature needs, not your whole library.
• In the native apps you can switch search and save-time enrichment to Apple's on-device models instead, and then nothing is sent for those features at all.

There is no automated decision-making that produces legal effects for you, and no profiling in the art. 22 sense.

6. Cookies and analytics on the website

• Strictly necessary. A session cookie that keeps you signed in, and local storage entries holding your preferences and your cookie choice. These cannot be switched off without breaking sign-in, and they need no consent.
• Our own website statistics. We run a self-hosted Plausible instance on our own infrastructure. It sets no cookies, does not fingerprint you, stores no personal data and never leaves our servers: it counts page views and referrers in aggregate.
• Microsoft Clarity. Only with your consent. Until you accept the banner it runs in Microsoft's no-consent mode, storing nothing on your device; if you accept, it records how the pages are used (clicks, scrolls, a replay of the session) so we can find what is broken. Decline, or clear the choice, and it records nothing. Microsoft is a controller for the data it holds under its own privacy statement.

To change your answer, visit the site with ?resetConset appended to the URL and the banner comes back.

7. Who else sees your data

We do not sell your data and we do not share it for advertising. We use these processors and providers to run the service:

When you save a link, our servers fetch that page to build the preview, and may ask the relevant public service (for example a film, music or game database) for metadata about it. Those requests contain the URL you saved, never your identity.

We will also disclose data where the law requires it — a valid order from a competent authority — and, if WebBites were ever sold or merged, to the acquirer, who would be bound by this policy until it told you otherwise.

8. Transfers outside the EEA

Your library itself stays in the EU: the database, your files and images, and the search index all live on servers we rent and administer ourselves in Europe. The transfers below are limited to the specific features named above.

Some of the providers above are in the United States. Those transfers rely on the European Commission's Standard Contractual Clauses, or on the provider's certification under the EU–US Data Privacy Framework where it has one, together with the supplementary measures (encryption in transit, access controls, data minimisation) that we apply on our side. You can ask us for the details of the mechanism used for any given provider.

9. How long we keep it

• Your library and account: for as long as your account exists.
• After you delete your account: your content is deleted from our live systems immediately, and disappears from encrypted backups as those roll over, within 30 days.
• Server and security logs: up to 90 days.
• Crash and error reports: up to 90 days.
• Invoices and payment records: six years, because Spanish commercial and tax law requires it (art. 30 Código de Comercio; Ley General Tributaria).
• Support emails: up to two years, so we have the thread if you write again.

10. How we protect it

Everything travels over TLS. Passwords are hashed, never stored in a readable form. Access to production systems is limited to the people who operate the service and protected by strong authentication. Backups are encrypted. Your session token lives in your device's Keychain on Apple platforms.

No system is perfectly secure, and we will not pretend otherwise. If a breach ever affects your personal data and poses a risk to you, we will notify the Spanish supervisory authority within 72 hours and tell you directly where the law requires it.

11. Your rights

You can, at any time:

• Access your data, and get a copy of it.
• Correct anything inaccurate — most of it you can edit yourself in the app.
• Delete your account and everything in it: Settings → Delete account, no email to us required.
• Export your library in a portable format, from Settings → Export, whenever you like.
• Restrict or object to processing based on our legitimate interests.
• Withdraw consent (for analytics or marketing email) without affecting what was done before you withdrew it.

Write to contact@webbites.io and we will answer within one month. We may ask you to confirm the email address on the account before acting, to be sure we are not handing your library to someone else.

If you think we have got this wrong, you can complain to the Spanish Data Protection Agency — Agencia Española de Protección de Datos, C/ Jorge Juan 6, 28001 Madrid, www.aepd.es — or to the supervisory authority where you live. We would rather you told us first, but it is your right either way.

12. Children

WebBites is not directed at children. You need to be at least 14 to use it with an account, which is the age of digital consent in Spain (art. 7 LOPDGDD); where you live sets a higher age, that age applies. If we learn we are holding an account belonging to a child below that age, we delete it.

13. Changes to this policy

When we change something material we will update the date at the top and, if it affects how your data is handled, tell you in the app or by email before it takes effect. The current version is always at https://www.webbites.io/privacy.