Skip to content
Filljitsu

Privacy Policy

Last updated: October 12, 2026

This policy explains how I process personal data on the Filljitsu website and in the Filljitsu Chrome extension. I write in plain language, but in line with the GDPR (Regulation (EU) 2016/679).

§1Data controller

The controller of personal data is Bartłomiej Mazik, Katowice, Poland, e-mail: bartlomiej.mazik1@gmail.com ("I" or "the Controller").

For matters concerning personal data, write to bartlomiej.mazik1@gmail.com or use the contact form. I respond without undue delay, and within one month at the latest.

§2What data I process, why and on what legal basis

I process only the data needed for the service to work:

  • Account: e-mail address, a password hash (never the password itself), and, when you sign in with Google or GitHub, basic profile data from those services. Purpose: creating and maintaining the account. Legal basis: performance of a contract (Art. 6(1)(b) GDPR).
  • Settings and writing styles: the selected style, information about yourself entered in the dashboard, extension settings. Purpose: tailoring answers. Legal basis: performance of a contract.
  • Usage history: date, page domain, number of fields, mode, AI model, number of tokens and cost. I do not store form contents or generated answers. Purpose: plan limits, billing, abuse prevention. Legal basis: performance of a contract and my legitimate interest (Art. 6(1)(f) GDPR).
  • Library (PRO plan): text extracted in your browser from added files and notes, split into fragments, together with their vector representation. I do not store the original files. Purpose: answers in Context mode. Legal basis: performance of a contract.
  • Payments: billing data and payment history handled by Stripe. I do not see full card numbers. Purpose: billing and tax obligations. Legal basis: performance of a contract and a legal obligation (Art. 6(1)(c) GDPR).
  • Contact form: name, e-mail address, message content, browser information and a salted hash of your IP address (to limit spam, without storing the address itself). The message reaches me by e-mail via Resend. Purpose: answering your question. Legal basis: legitimate interest.
  • Uninstall survey: the selected reason and an optional comment, without account data, with an IP address hash to limit abuse. Legal basis: legitimate interest.
  • Technical logs of the server and the hosting provider (e.g. IP address, request time). Purpose: security and troubleshooting. Legal basis: legitimate interest.

§3Chrome extension

The extension only works after your action: clicking the icon or pressing the shortcut. It then reads the labels and types of the form fields on the current tab and the visible page text, from which it removes data that looks sensitive before sending.

The extension never reads or fills in fields with passwords, card numbers, CVV and one-time codes, or account numbers, never ticks consents and never submits forms. It does not collect browsing history.

In browser storage, the extension keeps the account connection token, settings and the last used mode. Signing out of the extension deletes the token.

§4Processing by artificial intelligence

Answers for fields are generated by AI models from external providers: Anthropic (Claude models), Google (Gemini models and embeddings) and TypeSafe (the Jev decision model, which picks options in checkboxes, radio buttons and lists). For the time needed to generate an answer, I pass them the field labels, the redacted page text, your style settings and, in Context mode, also the task note and matching library fragments.

The providers process this data on my behalf, under data processing agreements, through paid APIs whose terms exclude using the submitted data to train models.

I do not make decisions about you based solely on automated processing that would have legal effects. AI answers are suggestions that you review before submitting a form.

§5Data recipients and transfers outside the EEA

I use providers that process data on my behalf (processors):

  • Neon (database and sign-in, servers in Frankfurt, EU)
  • Vercel (website hosting)
  • Stripe (payments and invoices)
  • Anthropic, Google and TypeSafe (AI models, embeddings)
  • Resend (delivery of contact form messages)

Some of these providers are based in the USA. Data may be transferred outside the European Economic Area on the basis of a European Commission adequacy decision (the EU-US Data Privacy Framework) or standard contractual clauses approved by the Commission. You can obtain a copy of the safeguards on request.

I may also disclose data to public authorities where required by law.

§6How long I keep data

  • Account data, settings, styles and history: until the account is deleted.
  • Library files: until you delete them or delete your account.
  • Billing data: for the period required by tax law (usually 5 years from the end of the tax year).
  • Contact form messages: until the matter is closed, and then for 12 months in case of follow-up questions.
  • Technical logs: usually up to 30 days.

§7Your rights

You have the right to access your data, rectify it, erase it, restrict its processing, port it, and object to processing based on legitimate interest. You can delete your account and all related data yourself in the dashboard, on the Account tab.

You also have the right to lodge a complaint with the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, ul. Stawki 2, 00-193 Warsaw, Poland).

Providing data is voluntary, but you cannot create an account without an e-mail address, and you cannot buy the PRO plan without billing data.

§8Cookies and browser storage

I use only cookies and browser storage that are necessary for the website to work: sign-in, security and remembering the selected language. Consent is not required to store them (Article 399(3) of the Polish Electronic Communications Law and Article 5(3) of Directive 2002/58/EC). I do not use analytics, advertising or tracking cookies.

Details:

PurposeTypeRetention
Remembering the website languageNecessaryUntil the browser is closed
Keeping you signed inNecessaryUntil sign-out or session expiry
Faster session checksNecessary5 minutes
Secure sign-in with Google or GitHubNecessaryA few minutes, during sign-in
Remembering that the cookie notice was closed (browser storage)NecessaryUntil browser data is cleared

When paying, you go to Stripe's pages, which use their own cookies under Stripe's privacy policy.

You can delete or block cookies in your browser settings, but sign-in will stop working without them.

§9Security

I use encrypted connections (HTTPS), database encryption, a minimal scope of permissions, salted hashes instead of IP addresses, and the principle of not storing form contents. I store the extension token in the database only as a hash.

§10Age of users

The Service is intended for people aged 16 or over.

§11Changes to this policy

I will announce significant changes on the website or by e-mail. The current version is always available on this page.