Privacy Policy

1. Data controller

The controller of personal data related to accounts and use of Feedlinter is Bartłomiej Spyrka Anbis, NIP 6372204742, REGON 380734176, Dworska 22, 32-300 Niesułowice, Poland. For privacy matters, email support@feedlinter.com.

2. Data we process

• Account data: email address, user ID, session IDs, and hashes of single-use login tokens. Feedlinter uses email links and does not store a user password.
• Service data: domain and XML source URLs, selected rules, refresh history, diagnostics, subscription references, and plan status.
• Technical data: IP address, browser information, request time, and logs needed for operation, diagnostics, and abuse prevention.
• Payment data: we receive information needed to confirm and administer your plan; we do not store full card details. The payment operator’s processing details are presented at checkout.
• Feed data: usually public commercial product information such as titles, prices, SKUs, and links. A public file may nevertheless contain personal data. If it does, data protection law applies; the customer is responsible for the lawfulness and scope of data supplied in the source.

3. Purposes and legal bases

• Account creation, authentication, feed auditing and processing, and provision of proxy URLs — performance of a contract or pre-contract steps (Article 6(1)(b) GDPR).
• Accounting and tax duties — compliance with a legal obligation where it applies to the controller (Article 6(1)(c) GDPR).
• Security, abuse prevention, diagnostics, support, and legal claims — legitimate interests (Article 6(1)(f) GDPR).

4. Recipients and infrastructure providers

Providers supporting the Service may access data to the extent needed for their work. We use Amazon Web Services (AWS EMEA SARL and relevant AWS entities) for backend processing, DynamoDB storage, and messages sent through Amazon SES, and Cloudflare, Inc. for CDN, traffic protection, proxy delivery, and R2 file storage.

Purchase-related data is shared with the payment operator identified at checkout. Messages sent to support are handled by the provider of our support mailbox. A public output feed URL can be accessed by platforms to which you submit that URL.

5. Transfers outside the EEA

Infrastructure providers may process some data outside the European Economic Area. Where required, transfers rely on an appropriate GDPR Chapter V mechanism, in particular an adequacy decision under the EU–US Data Privacy Framework for currently certified recipients, or European Commission Standard Contractual Clauses with any required supplementary safeguards.

You can ask about the mechanism used for a particular provider at support@feedlinter.com.

6. Retention

We keep account and configuration data while you use the Service and afterward for as long as needed for settlement, legal claims, and legal duties. A single-use login link is valid for 15 minutes, and a session may remain valid for up to 30 days; expired technical records may be deleted later.

We keep technical and diagnostic data for the period necessary for security and Service operation under the configuration and policies of the relevant provider. Accounting data may be retained longer where law requires it.

7. Your rights and account deletion

You may request access, rectification, erasure, restriction, or portability of your data and object to processing where the GDPR provides these rights. You may also complain to the Polish supervisory authority, the President of the Personal Data Protection Office (UODO).

To exercise your rights or request deletion of your account and related data from active systems, email support@feedlinter.com from the address associated with your account. We may verify your identity. We will respond without undue delay, generally within one month; for complex requests the deadline may be extended as the GDPR permits. We cannot erase data that law requires us to retain or that is necessary for legal claims.

8. Cookies and browser storage

We use an essential session cookie to keep you signed in and a cookie to remember your dashboard language. Your browser may temporarily store the ID of an audit in session storage so you can return to its result. You can manage browser data in its settings; disabling essential cookies may prevent sign-in.