Legal

Privacy policy

Last updated: 30 October 2026

This policy covers the website privacyfence.eu and the download service at downloads.privacyfence.eu and the sign-in relay at oauth.privacyfence.eu, and nothing else.

Who is responsible, and for what

Andras Takacs, Budapest, Hungary. Email: [email protected]. PrivacyFence is a non-commercial open-source project run by a private person; there is no company behind it and no data protection officer.

That responsibility covers only what this website and the download service do with data about their visitors, as described below: hosting, download counts, analytics (only with your consent) and email you send us.

The PrivacyFence software is not covered

We do not operate the PrivacyFence software for you and never receive the data it processes. You, or your organization, install and run it on your own computer or your own server. It sends nothing to the project: no emails, files, messages, approvals, audit records, usage statistics or crash reports. There is one exception: an organization server that uses PrivacyFence's built-in apps registers its host name with the sign-in relay and sends its sign-in redirects through it, and a single-user install on its own computer sends them through it without registering, as described below. Apart from that, its only connections are to the AI assistant and the services you connect it to (such as Google, Slack, Salesforce, Atlassian, Telegram, Grist or your Peek server, and in an organization deployment your identity provider), in an organization deployment with push notifications turned on to the browser vendor's push service (Apple, Google, Mozilla or Microsoft), which receives only an encrypted, fixed-size notice that approvals are waiting, and to GitHub's public API to check for a newer release.

Whoever runs the software, you or your organization, is therefore responsible for the personal data it processes. The same holds for the AI assistant you connect it to, which is governed by that assistant's provider's own terms and privacy policy. The software is provided under the Apache License 2.0, "as is", without warranty of any kind; see the license for the full terms.

In short

• The site works without cookies. Nothing is stored on your device until you make a choice in the cookie banner, and only your choice itself is stored.
• Google Analytics runs only if you click Accept. If you decline, or ignore the banner, no request goes to Google.
• Downloads are counted by version, platform and day only: no IP address, cookie or browser details.
• The site is hosted on GitHub Pages behind Cloudflare. Both process your IP address to deliver the pages.

Hosting: GitHub Pages and Cloudflare

The pages are served by GitHub Pages (GitHub, Inc.) through Cloudflare (Cloudflare, Inc.), which acts as a content delivery network and protects the site against attacks. To deliver a page, both receive the technical data every web request carries: your IP address, the requested address, the time, and your browser's request headers (such as its user agent and language). GitHub logs visitor IP addresses for security purposes. Neither is given anything else by this site, and Cloudflare's own web analytics are switched off for it.

Legal basis: legitimate interest in delivering a secure website (Art. 6(1)(f) GDPR). Both companies may process data in the United States; both are certified under the EU–US Data Privacy Framework. See the GitHub privacy statement and the Cloudflare privacy policy.

Downloads and download counts

Installers are served by downloads.privacyfence.eu, a small service run on Cloudflare (Workers, R2 storage and a D1 database). The download and release history pages also ask it for the list of current releases, and the homepage and download page for the total number of downloads. When you download an installer, it adds one to a counter, and that counter is all it stores:

No IP address, user agent, cookie, fingerprint or any other identifier is stored with the count, so the counts cannot be linked to you. Cloudflare processes the request itself as described under hosting. Legal basis: legitimate interest in knowing how often the software is downloaded (Art. 6(1)(f) GDPR).

Sign-in relay (oauth.privacyfence.eu)

PrivacyFence ships OAuth apps of its own for Google, Slack, Salesforce, Atlassian and Miro. A provider sends the sign-in redirect only to a fixed address, so the redirect for these apps goes to oauth.privacyfence.eu, a small service run on Cloudflare (a Worker and a Durable Object). The relay forwards the redirect to the PrivacyFence server that started the sign-in, and only to a server that proved in advance that it controls its own host name; a single-user install on its own computer, which uses a local address, needs no registration. It is used only by organization servers and single-user installs that use the built-in apps. An organization's own apps never touch it, and desktop (local) installs do not use it. How the maintainers run the relay is described in the relay documentation.

• The redirect it forwards carries a one-time authorization code and the server's host name. It never sees a token, mail or file content. The relay processes the IP address of the request in transit.
• Servers using the built-in Google sign-in also send their sign-in redirects through the relay. The relay sees a one-time code and the signing-in account's Google Workspace domain (hd), checks it against the sign-in domains the server proved in DNS, and stores those domains with the server's registration.
• It stores each registered server's host name, its registration and renewal dates and its proven sign-in domains. This list is visible only to the PrivacyFence maintainers.
• To limit abuse it also keeps the requesting IP address next to each registration attempt for one hour, and a per-address count of new servers for the current day (UTC). Both are deleted automatically.
• It writes no logs.
• When a new server registers, or a server changes its sign-in domains, it emails the maintainers the host name, the IP address and the country of the request. The email is sent through PrivacyFence's Google Workspace mail, where Google is the processor, and is kept in that mailbox for up to 12 months.

Legal basis: legitimate interest in operating and securing the service (Art. 6(1)(f) GDPR). Cloudflare is the processor, as for the download service. The terms for the relay are at Relay terms.

Google user data in the PrivacyFence app

This section covers the Google connectors of PrivacyFence's built-in Google app.

What it accesses

Gmail, Drive, Calendar, Contacts, Tasks and Apps Script, only after the person signs in and consents. Each scope is used for what the connector pages describe.

Where it goes

• Tokens and data stay on the person's computer or their organization's server, never on PrivacyFence's.
• Content reaches the AI assistant the person connected only when they approve it on a card, or when a rule they set allows it, after the local personal-data check.
• The sign-in relay sees a one-time sign-in code, never mail or file content.

What never happens

No ads, no sale of data, no human reading, and no use to train AI models by PrivacyFence. What the AI assistant does with content it is given is governed by that assistant's own terms.

Revoking access

Disconnect Google on the /connect page of your PrivacyFence, or remove access at myaccount.google.com/permissions.

PrivacyFence's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Google Analytics (only with your consent)

If you click Accept in the cookie banner, the site loads Google Analytics 4 to see how many people visit, which pages they read and where they came from. Until you accept, the Google Analytics code is not loaded at all and no request goes to Google.

Once you accept, Google Analytics collects:

• the pages you view, the page that referred you, and the time of your visit;
• your browser, operating system, device type, screen size and language;
• your approximate location (country and city), which Google derives from your IP address. Google Analytics 4 does not store IP addresses;
• interactions on the page: scrolling, clicks on links to other sites, file downloads, and which platform's download button you click;
• the section of the site a page belongs to (for example, download or documentation).

It sets two cookies on privacyfence.eu:

The property is set up to collect as little as possible: data is kept for 2 months; Google Signals, advertising personalization and data sharing with Google are switched off; and no user ID or other personal identifier is sent.

Google Ireland Limited processes the data on our behalf. Data may be transferred to Google LLC in the United States, which is certified under the EU–US Data Privacy Framework. See Google's privacy policy and how Google uses data from its business products.

Legal basis: your consent (Art. 6(1)(a) GDPR, and Art. 5(3) of the ePrivacy Directive for the cookies). You can withdraw it at any time: choose Cookie settings at the bottom of any page and click Decline. That stops Google Analytics on this site and deletes its cookies. Withdrawing does not affect what was collected before.

Your cookie choice

Your answer to the banner is kept in your browser's local storage under the name pf-analytics-consent, so the banner does not reappear on every page. It is never sent anywhere and stays until you change it or clear your browser's site data.

When you contact us

If you email [email protected], your address and message are used to answer you and kept only as long as the conversation needs. Legal basis: legitimate interest in answering (Art. 6(1)(f) GDPR). Issues and discussions on GitHub are covered by GitHub's own privacy statement.

Your rights

You have the right to access, correct and delete your personal data, to restrict or object to its processing, and to data portability, as far as the GDPR provides. Write to [email protected]. For the counters and the analytics data we hold nothing that identifies you, so we usually cannot find your data in them.

You can also complain to a data protection authority. In Hungary that is the Nemzeti Adatvédelmi és Információszabadság Hatóság (NAIH), Falk Miksa utca 9–11, 1055 Budapest.

Changes

This policy changes when the site changes. Its full history is public in the project's repository.