Privacy and data access policy

DTF Privacy & Data Protocols

Status: working draft. This is a living set of protocols, written while DTF's systems and processes are being set up. It is not yet a published privacy notice. Before publication it needs review by someone qualified in EU/Dutch data protection law and adoption by the Council of Stewards. Items marked to confirm are assumptions, not settled facts.

Why these protocols exist

The Democratic Tech Fund exists to build alternatives to extractive platforms. How we handle our own members' data has to show that alternative in practice, not only describe it.

We commit to four things:

  1. Secure, minimal holding. We collect only what a specific task needs, keep it only as long as that task needs it, and protect it well.

  2. No sale, disclosure only with consent. Members' data is never sold, rented or traded. It is shared with others only when the member has said yes to that specific sharing.

  3. Intentional collective sharing. Where members choose to pool data, we make that sharing deliberate, bounded and reversible.

  4. Working against surveillance and concentration. Our tools and choices refuse tracking, scraping and the build-up of data power, and help communities see and shape their own relationships.

Each commitment below becomes a protocol: concrete rules we can check ourselves against. Where we fall short, we say so in the open questions at the end.

Scope and responsibility

These protocols cover personal data of DTF members (individual Fund Fellows and member organisations' contact people), donors, Council and driving-team members, and participants in DTF calls and workshops.

Who is responsible. The Free Knowledge Institute (FKI), as DTF's fund custodian and a Dutch foundation, is proposed as data controller. That places DTF under the GDPR and the Dutch implementation act (UAVG), with the Autoriteit Persoonsgegevens as lead supervisor.

Third-party services. Each service that touches member data gets a clear role and, where it processes data for us, a processing agreement (GDPR Art. 28):

Service

What it holds

Proposed role

Rauthy SSO (login.democratictech.fund), self-hosted on Co-op Cloud

Login, email, display name

Our system; hosting provider is a processor

Join form and website (democratictech.fund)

Membership details submitted

Our system

OpenCollective

Contribution and payment records

To confirm: separate controller or processor

DTF Goteo crowdfunding platform

Backer accounts and pledges

To confirm: separate controller or processor

meet.coop

Call participation, any recordings

Processor

Legal bases. Membership administration rests on the membership agreement. Donation records rest on legal obligation (ANBI and fiscal record-keeping). Everything optional, such as newsletters, public listing or data sharing, rests on consent. We avoid relying on "legitimate interest" as a catch-all.

Protocol 1 — Secure, minimal holding

We hold the least data that lets DTF function, in as few places as possible, for as short a time as possible.

Rules

  1. Purpose first. No field is added to a form or database without a written reason in the data inventory below.

  2. Optional means optional. Only fields the task truly needs are required. Everything else is blank by default.

  3. Pseudonymous where possible. Members can take part in Funding Circle votes and discussions under a display name. Legal names are needed only where the law or payment processing requires them.

  4. One home per dataset. Each kind of data lives in one system. No spreadsheet copies, no exports to personal drives.

  5. Delete on schedule. Each dataset has a retention period. An annual data review checks that deletion happens.

  6. No sensitive categories. We do not ask for health, ethnicity, religion, political or similar data. If it is sent to us unasked, we delete it.

Data inventory (draft — to be completed as systems go live)

Data

Why we hold it

Where

Kept for

Email, display name, password hash

Login and member contact

Rauthy SSO

Membership + 3 months

Organisation name, contact person, city

Member administration, Funding Circle allocation

Member database

Membership + 3 months

Contribution amount and date

Fiscal records, Phase 1 vote weighting

OpenCollective / FKI accounts

Fiscal retention period (to confirm, likely 7 years)

Funding Circle votes and allocations

Running the validation round

Voting system

Aggregate result kept; individual votes deleted after the round closes and appeals end

Newsletter subscription

Sending updates

Mailing list

Until unsubscribed

Call recordings

Only when all present agree

meet.coop

90 days unless published with consent

Website visits

Not collected per person

—

—

Protocol 2 — Never sold, disclosed only with consent

Members' data is not a revenue stream, a bargaining chip or a favour to partners. It leaves DTF only when the member has agreed to that specific disclosure.

Rules

  1. No sale, rent, trade or swap of personal data, to anyone, under any arrangement. This includes "data partnerships" and list exchanges with allied organisations.

  2. Consent is specific. Each request names who will receive the data, which data, for what purpose and for how long. One yes does not cover a different recipient or purpose.

  3. Consent is easy to refuse and to withdraw. Saying no carries no penalty on membership or voting rights. Withdrawal works from the member's account or by one email.

  4. Consent is recorded. We log who agreed to what and when, so we can show it and honour withdrawals.

  5. Processors are not recipients. Services that process data on our behalf (hosting, mail) do so under a written agreement, for our purposes only, and are listed publicly.

  6. Legal demands. If a court or authority compels disclosure, we check its legal basis, disclose the minimum, tell the affected member unless the law forbids it, and count such requests in an annual transparency note.

  7. Matching partners get aggregates. Municipalities and foundations that match funds receive project-level and aggregate figures, not backer or member lists, unless backers opt in.

  8. Donor recognition is opt-in. Names and amounts are private by default. Public thanks happen only when the donor asks for it.

Protocol 3 — Secure, intentional collective sharing

Privacy is not only about withholding. A federation needs members to find each other, pool knowledge and act together. We support that sharing on purpose, with clear limits, rather than letting it happen by default.

Visibility circles. Every piece of member information carries one of four visibility levels, chosen by the member:

Level

Who can see it

Default for

Private

The member and named DTF administrators

Contact details, contribution amounts

Circle

Members of the same circle of work, working group or Funding Circle or city node

Display name, participation in votes

Federation

All DTF members

Nothing by default

Public

Anyone

Nothing by default; funded projects' public information

Rules

  1. Members set their own level per item, and can change it at any time. Raising visibility is always the member's own act.

  2. Pooled datasets need a sharing agreement. When members or circles combine data (for a joint report, an impact study, a shared map), a short written agreement states the purpose, who holds the pool, who can access it, how long it lasts and how it ends.

  3. Aggregate before you share. Where a question can be answered with counts or summaries, we share those, not records.

  4. Purpose- and time-bound. Shared access expires. Renewal is a fresh decision, not an automatic rollover.

  5. Visible access. Members can see which circles or partners have access to data about them, and when it was last used.

  6. Open formats, federated by design. Shared data uses open, documented formats and protocols so that it can move between cooperative platforms without a central broker.

Protocol 4 — Against surveillance, scraping and data concentration

This protocol has two sides: refusing practices that extract and concentrate data, and building members' own capacity to understand and steer their relationships.

Refusing extraction

  1. No third-party tracking. No advertising pixels, no third-party analytics, no social-media widgets that report visitors back to platforms. Any statistics are cookieless, aggregate and self-hosted.

  2. No leaky embeds. Video, fonts and maps are self-hosted or served from cooperative infrastructure (e.g. PeerTube), so a page view does not inform a third party.

  3. Cooperative, EU-based hosting. Member data runs on Co-op Cloud and comparable cooperative or commons-based providers, under EU jurisdiction. No member data on BigTech clouds.

  4. Resisting scraping. We block known AI and data-harvesting crawlers, rate-limit bulk access, and do not publish member directories in harvestable form. Our terms forbid scraping and model training on our content.

  5. No AI training on member data. Member data is not used to train or fine-tune AI models, ours or anyone's, without explicit collective agreement.

  6. No central honeypot. Data stays with the circle or node it belongs to wherever practical. We prefer federation over one large database, even where central storage would be easier.

  7. Leaving is easy. Members can export everything we hold about them in open formats, and delete their account in one step.

Building community capability

  1. Relationship view. Each member can see their own web of ties within DTF: circles joined, projects backed, partners connected. They can adjust visibility per relationship and take that map with them.

  2. Collective data review. Once a year, members are invited to a data assembly: what DTF holds, who accessed it, what changed, and what to stop collecting.

  3. Shared literacy. Funding Circles and community calls include practical sessions on data rights, consent and secure tools, so members can apply the same practices in their own organisations.

  4. Funded projects carry it forward. Projects funded by DTF commit to equivalent protocols under the Five Pillar Framework, so the practice spreads through the federation, not only within it.

Protocol 5 — Access control and security practice

Only named people with a current role can reach member data, and only the parts their role needs.

Access

  1. Least privilege. Access is granted per role (administrator, circle coordinator, treasurer), not per person's seniority. Roles and their holders are listed in an access register.

  2. Named accounts only. No shared logins. Every administrative action is tied to a person.

  3. Strong login. Multi-factor authentication is required for every account with access to member data. Credentials live in a shared, encrypted password manager.

  4. Review and offboarding. The access register is reviewed every six months and whenever the Council or driving team changes. Access ends within a week of a role ending.

Security baseline

  1. Encryption in transit (TLS) everywhere and at rest for databases and backups.

  2. Encrypted backups, with a restore test at least once a year.

  3. Timely security updates on all self-hosted services.

  4. Devices used for DTF administration have disk encryption and screen lock.

When something goes wrong

  1. Anyone who suspects a breach reports it at once to the privacy contact. No blame for reporting.

  2. Contain, assess and record the incident.

  3. Where it poses a risk to people, notify the Autoriteit Persoonsgegevens within 72 hours (GDPR Art. 33).

  4. Where the risk is high, inform affected members promptly and plainly, with what they can do.

  5. Publish a short post-mortem to members: what happened, what we changed.

Members' rights

Every member can, free of charge:

  • see what we hold about them and get a copy (access, portability)

  • correct what is wrong (rectification)

  • have their data deleted, except records we must keep by law (erasure)

  • limit or object to a use of their data (restriction, objection)

  • withdraw any consent at any time, without affecting what happened before

  • complain to a data protection authority: the Autoriteit Persoonsgegevens, or the authority in their own EU country

We answer requests within one month, as the GDPR requires, and aim for much faster. Most of these actions should be possible directly from the member's account, without having to ask.

Contact: privacy contact address to be set (see open questions).

Open questions for the Council and driving team

  • ☐ Confirm FKI as controller, and whether any processing with the co-founders is joint controllership

  • ☐ Clarify the roles of OpenCollective and the Goteo platform, and how their own privacy terms fit these protocols

  • ☐ List every hosting provider and service, and sign processing agreements where needed

  • ☐ Confirm retention periods, especially the fiscal period for ANBI donation records

  • ☐ Set up a dedicated privacy contact address and decide who answers it

  • ☐ Decide whether to run any website statistics at all, and if so which self-hosted tool

  • ☐ Agree a recording policy for community calls and Council meetings

  • ☐ Decide who holds administrator access at launch and create the access register

  • ☐ Draft the sharing-agreement template for pooled data (Protocol 3)

  • ☐ Scope the member relationship view (Protocol 4) with the website and SSO build

  • ☐ Legal review by someone qualified in GDPR before publication

  • ☐ Derive a short public privacy notice from these protocols, in English, Dutch, Spanish and Catalan