Privacy Policy

1. Data we process

1.1. Account data: name, e-mail address and password, the latter stored only as a hash, never in clear text.

1.2. Product usage data: the feeds you subscribe to, folders and lists, articles read and saved, saved pages and preferences for language, theme and layout. These are the content of the service: without them there is no reader.

1.3. Your archive content: the notes you write and the files that accompany them, including those received by synchronisation with your devices. We store and display this content for you; we do not read it, we do not index it for third parties and we do not use it to train models.

1.4. Technical data: access logs (date, time and IP address), used for security, abuse prevention and rate limiting.

1.5. Moderation data: when you report content, we record who reported it, what was reported and why, in order to review the request and to deter abuse of the channel itself. Administrative removal actions leave a trail of metadata — what was removed, when and on what basis — with no copy of the content.

1.6. Payment and tax data: when you purchase a paid plan, the payment provider collects and processes the data necessary for the transaction. We receive and store the data indispensable to identifying the subscriber and issuing the tax documents required by law, as set out in the applicable Annex.

2. Purposes

2.1. To provide the service — to synchronise and display your feeds and your archive —, to keep your account secure, to send transactional messages (address verification, password reset) and to improve the product.

2.2. To comply with legal, accounting and tax obligations, and to respond to orders from a competent authority.

2.3. We do not sell personal data.

3. Legal bases

3.1. We process data on the basis of performance of the contract, legitimate interest in security and abuse prevention, compliance with a legal or regulatory obligation and, where applicable, consent, which may be withdrawn at any time.

4. Cookies and local storage

4.1. We use a session cookie (httpOnly) to keep you signed in and the browser’s local storage for preferences such as the theme.

4.2. If other purposes are adopted — including advertising — they will be described in this policy and, where the law so requires, made subject to your prior consent, with the option to refuse.

5. Sharing with processors

5.1. To operate, FeedSink uses contracted providers for hosting, transactional e-mail, payment processing and backups. Those providers process data on our behalf, under contract, and some are located outside your country; in those cases the international transfer follows the safeguards required by the applicable law.

5.2. Your archive content is stored in a contracted object storage service, in an account separate from the one holding our backups — a separation adopted so that a measure concerning content does not reach the service’s backup.

5.3. Otherwise, personal data is shared only where required by law or to exercise rights in legal proceedings.

6. Retention periods

6.1. Archive content — notes and files: retained while the subscription is active and for thirty (30) days after it ends, when it is permanently deleted, together with backups, in the regular disposal cycle. Early deletion may be requested at any time.

6.2. Content made dormant by a plan change: retained for at least three (3) months, as set out in clause 6 of the Terms of Use.

6.3. Account data and payment records: retained, after deletion of the content, for as long as necessary to comply with legal, accounting and tax obligations and to exercise rights in legal proceedings.

6.4. Access logs: for the period stated in the applicable Annex, under confidentiality; that period runs regardless of the end of the subscription.

6.5. Material under a preservation order: held for the period required by the authority, in a separate environment and under confidentiality, and destroyed at the end of it. Preservation prevails over the periods above.

6.6. Pending accounts never confirmed: deleted within seven (7) days.

7. Your rights

7.1. Depending on where you live, you have the right to confirmation of processing, access, correction, anonymisation, restriction or erasure, portability, information about sharing, and withdrawal of consent. The Annex applicable to you states the statute and the competent authority. To exercise these rights, write to the contact address below — we reply as soon as possible and at no cost.

7.2. The right to erasure is limited by the retention duties and preservation orders described in this policy. Where we cannot erase something you asked us to erase, we tell you the basis and the applicable period.

8. The browser extension

8.1. The FeedSink extension saves to your account the pages, posts and channel messages you choose to save. When you trigger a save, the extension sends FeedSink the address, visible content and, if you have selected a passage, the selected text. On social integrations you enable, it reads displayed posts locally only to place save buttons; nothing is sent to FeedSink until you click one of those buttons. It does not capture browsing history or track you across sites.

8.2. The extension does not use credentials of its own: it reuses the session you already have on the FeedSink site. Signing out of the site disables the extension.

8.3. The permissions requested are the minimum necessary: temporary access to the page when you trigger the extension, communication exclusively with https://feedsink.com and, only when you enable a specific social integration in Settings, optional access to that site to display save buttons. Every integration starts off and its permission can be revoked. The published version does not add buttons to YouTube or WhatsApp and does not work in one-to-one conversations; on Telegram, it may work in public or private channels and in groups. The data sent follows this same policy.

8.4. The extension keeps only your chosen preferences in the browser's synced storage, the short-lived access token in session storage, and a small local list of recently saved addresses to prevent duplicates. Page content and browsing history are not kept in the extension's storage.

8.5. The use and transfer of information received by the extension comply with the Chrome Web Store User Data Policy, including its Limited Use requirements: they are restricted to the visible functionality of saving content to your own account, are not sold, are not used for advertising, credit or unrelated purposes, and are not read by humans except when necessary for security, legal compliance or support requested by you.

9. Security

9.1. We apply technical and administrative measures to protect data: encrypted traffic, passwords stored as hashes, access control and logging of administrative operations. No system is immune to incidents; in the event of a material security incident we notify the data subjects and the competent authority as required by law.

10. Changes to this policy

10.1. This policy may be updated; the date shown at the beginning identifies the version in force. Material changes are announced in the product and, where required, by e-mail.