We built this site to learn from, not to learn about you. There are no accounts, analytics, ad trackers, or cookies.
Two outside services still handle some information: GitHub serves the pages, and Formspree delivers messages from the contact form. The useful version is below; open the details only if you want them.
SYSTEM-LEVEL PRIVACY
What we do—and do not do
Our first privacy control is simply not collecting the data. That is much more useful than asking you to click through a banner.
- No analytics, advertising pixels, behavioural profiles, or cross-site tracking.
- No account system and no database of website visitors.
- Only three contact fields: name, email address, and message.
- No sale, rental, or advertising use of contact data.
- We plan to replace Formspree with an EU-resident form handler.
The only services involved
Opening a website always tells its host something about the connection. Sending us a message also gives the form service whatever you type. Those are the only two data paths on this site.
Select a service to see exactly what it may receive, what we do about it, and what you can do if you want to reveal less.
01GitHub Pages
Static website hosting · Select for the details
GitHub Pages
Static website hosting · Select for the details
- What may reach it
- IP address is logged for security. Ordinary request metadata may include time, requested path, browser user-agent, and referring origin.
- What we do
- We publish static files only, set no analytics cookies, load no tracker, and send a no-referrer policy for outbound navigation. We do not receive GitHub’s raw visitor logs.
- What you can do
- A trusted VPN or Tor can mask your network IP from the destination. A privacy-oriented browser can reduce user-agent and fingerprint uniqueness.
PROVIDER-PUBLISHED ASSURANCE
02Formspree
Contact-form processing and delivery · Select for the details
Formspree
Contact-form processing and delivery · Select for the details
- What may reach it
- Name, email address, message, and request metadata needed to process and protect the submission, which may include IP address, user-agent, and referrer.
- What we do
- We request only the fields needed to reply. We do not add marketing fields or mailing-list consent. Migration to an EU-resident handler is planned; until then, Formspree remains the active processor.
- What you can do
- Use an email alias if you do not want to disclose your primary address. Use a pseudonym where your legal name is not needed, and omit sensitive details from the message.
PROVIDER-PUBLISHED ASSURANCE
- GDPR / transfersFormspree states that it acts as a processor and relies on EU Standard Contractual Clauses.
- CCPAFormspree states that it supports California rights to know, delete, opt out, and receive non-discriminatory treatment.
- SOC 2 Type IIFormspree states that an independent auditor has assessed its controls against the AICPA Trust Services Criteria.
Why we use it
If you write to us, we use your message and reply address to read it and respond. That is it. We rely on legitimate interests to run this basic contact channel.
Your message does not put you on a mailing list. We do not profile you, advertise to you, or make automated decisions about you.
Where it goes
GitHub and Formspree are US-based, so some data may be processed outside the European Economic Area. Both publish contractual safeguards for European data transfers, and GitHub also publishes participation in the EU–US Data Privacy Framework.
Paperwork is not the same thing as EU-only processing. We therefore keep collection small and plan to move the contact form to an EU-resident provider.
How long we keep it
We keep correspondence while it is useful for the conversation, an ongoing relationship, or a legal obligation. We remove messages that no longer have a reason to be there.
Formspree may retain submissions in its dashboard and backups under its own service controls. Until a precise account-level deletion schedule has been confirmed, we do not promise a fixed number of days. You may ask us to delete your submission and we will remove the copies under our control and initiate any processor-side deletion available to us.
GitHub controls retention of its security logs. GitHub states that retention depends on the collection purpose and legal obligations.
Cookies and tracking
There is no cookie banner because we do not set cookies. We also do not use local-storage identifiers, analytics, advertising, session replay, or fingerprinting code.
Links to external websites are separate services with their own privacy practices. Our no-referrer policy is intended to avoid sending those sites the address of the Equilibria page you came from.
Your rights
You can ask what we hold about you, ask us to correct or delete it, restrict how we use it, or object. GDPR rights depend on the circumstances and sometimes have legal limits.
Email us below. We may need enough information to confirm the request is really yours. You can also complain to Sweden’s data-protection authority, IMY.
If this changes
If we add a service, collect something new, or change why data is used, we will update this page. The date at the top tells you which version you are reading.
Privacy tools
These independent tools can make normally invisible browser and network disclosures easier to understand. They are external services, so review their own policies before using them.
See your browser fingerprint
EFF’s Cover Your Tracks explains how browser configuration can make a browser recognisable even without cookies.
Open Cover Your Tracks ↗Check network and browser leaks
Mullvad’s Connection Check displays the public IP, DNS, WebRTC, and other signals visible from your connection.
Open Connection Check ↗Use an email alias
An alias can receive replies without revealing your primary mailbox and can be disabled if it is later abused.
Learn about aliases ↗Privacy contact
For a privacy question or rights request, email contact@eq-network.org.
You may also complain to the Swedish Authority for Privacy Protection (IMY).