Log inCreate account

Neek

Data Processing Agreement

The contract under Article 28 GDPR between a project that runs its newsletter under its own name (white-label) and Neek, which processes its subscribers' data on its behalf.

Who agrees to what

This agreement is between you, the person or organisation that runs a project on Neek and turns on white-label for its newsletter (the controller), and Neek's operator (the processor). It is a contract under Article 28 of the General Data Protection Regulation (GDPR) and adds to the Terms of Service. You accept it in your project's settings; Neek records who accepted it, when, and which version.

What Neek processes for you

Neek processes your subscribers' personal data only to run your project's newsletter and subscriber pages: taking sign-ups and their confirmation, sending your newsletter and its service mails, signing subscribers in on your project's address, keeping their settings, serving their personal feed, and handling unsubscribes, bounces, and complaints.

The people concerned are those who subscribe to your project's newsletter. The data is their email address; the language, timezone, and frequency of their subscription; when they signed up, confirmed, and were last sent mail; their sign-in sessions on your project's address with IP address and browser; the hashes of their sign-in links, codes, and personal feed address; an activity log of their sign-ins and changes; and whether a mail to them bounced or was reported as spam.

The processing lasts as long as white-label is on for your project and ends as described under "When it ends".

Your instructions

Neek processes this data only on your documented instructions. Your instructions are this agreement, your project's settings, and what you and your subscribers do in the product. Neek tells you if it believes an instruction breaks data protection law, and tells you before it must process the data for another reason because the law requires it, unless the law forbids telling you.

You are responsible for having a legal basis for your newsletter, for your own imprint and privacy policy, whose addresses you give Neek and which Neek links from your subscriber pages and mails, and for telling your subscribers that Neek processes their data for you.

Confidentiality and security

Everyone who can access the data for Neek is bound to confidentiality. Neek protects the data with the measures described in its Privacy Policy and keeps them up to date, among them: encrypted connections, hashed sign-in links, codes, feed addresses, and session tokens, encrypted backups, access limited to the people who operate Neek, sign-in and sign-up rate limits, and sessions that work only on the address they were started on.

Other processors

You agree that Neek uses the processors named under "Who processes data for Neek" in its Privacy Policy for this processing too: for hosting and backups, for delivering mail, and for storing and delivering media. Neek binds each of them to data protection duties that match this agreement and stays responsible to you for what they do. Neek announces a new or replaced processor in its Privacy Policy at least 30 days before using it for your subscribers' data; if you object for a data protection reason, you can turn white-label off or end your project before then.

Neek keeps this data in the European Union. Where a processor works outside it, Neek makes sure a transfer mechanism of the GDPR applies, as its Privacy Policy describes.

Helping you

Subscribers can see, change, and delete their own data on your project's address. If a subscriber sends Neek a request about their data, Neek passes it to you and does not answer it itself, unless you tell it to. Neek helps you answer requests, assess the impact of the processing, and talk to supervisory authorities, as far as the data it holds allows.

Neek tells you without undue delay, and where it can within 48 hours, after it learns of a personal data breach that affects your subscribers' data, with what it knows about what happened, whom it affects, and what it has done about it.

Audits

Neek gives you the information you need to show that this agreement is kept. Once a year, or after a breach, you can ask for a written answer to reasonable questions about the processing, or audit it yourself or through an auditor bound to confidentiality, with 30 days' notice, in a way that doesn't put other customers' data or Neek's operation at risk.

When it ends

The agreement ends when you turn white-label off, delete your project, or your account is deleted. You can export your subscriber list before then. After it ends, Neek handles your subscribers' data as its Privacy Policy describes for newsletters: subscriptions end with the project, and an address without any subscription left is erased. Backups that still hold the data are overwritten within their retention period.

Changes

If this agreement changes in substance, it gets a new version, and Neek asks you to accept it in your project's settings. Until you do, the version you accepted stays in force; white-label stays on only with the current version accepted.

Last updated: November 14, 2026

STAGING v0.14.20