Privacy notice

1. Controller

No data protection officer has been appointed. Data protection requests go to the address above.

2. Which data is processed

Account data

Email address, display name and the settings you choose yourself: language, time zone, jurisdiction. At registration Pevidy suggests the language and time zone from your browser’s settings (a language chosen on the page comes first); the account starts with them, and you change both in Settings. So that they last until you confirm your email address, the two values go to the sign-in service Supabase as account data and stay stored there (section 4).

Sign-in and sessions

Session identifiers, the time of last use and — where the browser sends it — a device name. They let you see your open sessions and end them, and let Pevidy recognise an ended session as ended. The Pevidy team sees them in account management (section 8).
For every new session Pevidy also stores the kind of device and the program as the browser states them (for example “iPhone · Safari”), and the approximate location: the city the IP address of the sign-in belongs to. Pevidy works the city out on its own server with a location database (DB-IP IP to City Lite, IP Geolocation by DB-IP, licence CC BY 4.0). The IP address is used for this once, not stored and not passed on to anyone. It lets you tell in the settings which session runs on which device, and spot a session that is not yours. Only you see the city; the Pevidy team does not.

Your documents

The files you upload, their text, the fields read from them (names, dates, amounts, deadlines) and the kind of document Pevidy reads each one as. These documents may contain special categories of personal data under Art. 9 GDPR — an accident report contains health data, an employment contract may contain details of trade union membership. You decide which documents you upload.

Matters

What Pevidy derives from your documents: cases, deadlines, missing proof and the folders that come out of them.

Email

Messages sent to your Pevidy address, with attachments, replies you write from there, and the notifications and the daily digest Pevidy sends you.

Notifications and calendar

Your choice of how Pevidy notifies you, whether your address is blocked for notification emails and why, reports on the delivery of those emails and — if you create one — your calendar feed (section 9).

Sendings to third parties

Recipients you name for a case or that Pevidy finds word for word in your documents, with the place they are in, every sending you have Pevidy transmit, with its proof of sending, and every hand-over to a law firm with your consent and its proof (section 10).

Questions about your documents

The questions you ask Pevidy about your documents.

Logs

A record of what happened in your account — who changed what, and when. It exists so that every statement Pevidy makes can be traced back. In addition, the log of AI calls (section 5).

Acceptances

Which version of the terms you accepted, and when (section 7).

Messages to the team

What you write to the team through “Something wrong?”, the page you were on, the identifier of the case or document you had open, your account’s language, the version of the app and the team’s answer (section 8).

3. What for, and on which basis

Providing the service

Reading documents, sorting them, recognising deadlines, answering questions, putting folders together, also with the help of an AI provider (section 5). Art. 6(1)(b) GDPR — without this processing there is no service.

Special categories in your documents

Where a document contains data under Art. 9(1) GDPR, the processing rests on your explicit consent under Art. 9(2)(a) GDPR, which you give by uploading that document. You can withdraw it at any time by deleting the document; processing until the withdrawal remains lawful.

Structure learning

Learning how new kinds of document are built and making them readable for everyone (section 6). Art. 6(1)(b) GDPR — the terms describe it as part of the service; in addition Art. 6(1)(f) GDPR, the legitimate interest in making kinds of document readable for everyone.

Account, sign-in, security

Signing in, managing sessions with their device and approximate location, preventing abuse, the logs and the record of your acceptance of the terms. Art. 6(1)(b) and (f) GDPR — the legitimate interest is a service that cannot be taken over or changed unnoticed (which includes spotting a session that is not yours by its device and location), and a record of which terms you accepted.

Notifications and calendar

Emails about deadlines and about steps in your matters, the daily digest and the calendar feed (section 9). Art. 6(1)(b) GDPR; you choose in the settings which emails you get. Handling bounces and complaints about these emails: Art. 6(1)(f) GDPR.

Sending to third parties

Transmitting a sending you confirm to its recipient and keeping the proof of sending (section 10). Art. 6(1)(b) GDPR; for data under Art. 9(1) GDPR your explicit consent under Art. 9(2)(a) GDPR, which you give by confirming exactly that sending.

Handing a case to a law firm

Transmitting the papers of a case to the law firm you chose and keeping the proof of your consent (section 10). Art. 6(1)(a) GDPR; for data under Art. 9(1) GDPR Art. 9(2)(a) GDPR — your explicit consent to exactly that hand-over, which you can withdraw at any time with effect for the future. Pevidy keeps the proof of the hand-over after a withdrawal too, to be able to show the consent and the transmission: Art. 6(1)(c) GDPR in conjunction with Art. 5(2) and Art. 7(1) GDPR; where it contains data under Art. 9(1) GDPR, Art. 9(2)(f) GDPR.

4. Who else sees your data

Pevidy does not sell data and does not pass it on for advertising. To provide the service, these processors work with us under Art. 28 GDPR:

Where a processor is based outside the EU, the transfer rests on the European Commission’s standard contractual clauses under Art. 46(2)(c) GDPR.

If you have a sending transmitted to a third party, its recipient — your insurer, for example — gets the email and the attachments you confirmed (section 10). The recipient is not a processor of Pevidy; it processes them in its own responsibility. The same applies to a law firm you hand a case to (section 10).

5. AI providers

Pevidy uses language models from OpenAI (GPT-4.1 and text-embedding-3-small) to read documents and emails, recognise details in them, answer questions about your documents and write sentences. Sentences a language model wrote are marked “Written by Pevidy with AI” in the product; the mark leads here.

What is transmitted

What each task needs: the text of your documents and emails, your questions and, when Pevidy searches publicly available sources for a matter, their text. For requests to read and to write, Pevidy asks OpenAI not to store the response for later retrieval. How long OpenAI itself keeps transmitted data is governed by the contract with OpenAI. So that answers and texts are in your language, the model is also told your account's language (German or English). For the cover letter of a folder it is told the language of your case’s country instead: German, as long as Pevidy only knows cases from Germany, Austria and Switzerland. No model writes the email with which Pevidy transmits a sending (section 10).

Sentences about a case, a step and a document

Pevidy writes one or two sentences about your case, about the step that is due and about a document with AI. For them the model is shown only facts the page shows anyway: the name of the case as you wrote it yourself (not when it contains an IBAN, an email address, an address, a phone or reference number or a title such as “Mr” or “Mrs”), the state of the case or document, whose turn it is, the names of missing proof, how many of the required proofs are already there, as a count, deadlines as a day with their kind, amounts, once they are settled, the kind of step, reasons as neutral labels, the kind of document, with its country version, the date of the document and how many details were read. Never: text and excerpts of your documents, addresses, IBANs, reference numbers, names of other people from your documents and emails, email addresses and free values of learned fields other than dates and amounts. The sentences are stored with the facts they rest on, with your account, and deleted with it. Where a sentence does not pass the checks, a fixed sentence without AI stands in its place.

What Pevidy keeps about it

A log of every call without contents: task, provider, model, number of tokens processed, duration, outcome, cost and checksums of input and output. No document text, no question, no answer. The log is deleted thirteen months after the call; if you delete your account, the link to your account is removed with the deletion.

Basis and transfer

Art. 6(1)(b) GDPR, and for special categories in your documents Art. 9(2)(a) GDPR (section 3). OpenAI is based in the USA; the transfer rests on the standard contractual clauses (section 4).

Without AI

If OpenAI cannot be reached or AI is switched off, Pevidy writes nothing with AI. The marked places then show fixed texts or nothing.

6. Structure learning

When Pevidy does not yet know a kind of document, it can learn how that kind is built from your document and make that structure available to everyone who uses Pevidy. The terms describe this as part of the service; there is no opt-out.

What is learned and shared

The structure: a key and a name for the kind of document, the names, types and presence of its fields, variants, and the names in German and English.

What is never shared

Contents: no text, no values, no names, no amounts, no reference numbers, no cases, no decisions. Before a structure can apply to others, Pevidy checks it automatically for signs of personal data (such as email addresses, telephone numbers, account numbers, postal addresses, amounts, running text). If the check finds something, the structure does not apply to others. The check does not recognise every conceivable detail.

Who sees it

Once a structure applies to everyone, other accounts can recognise documents of that kind and read them with the same structure. The Pevidy team reviews new kinds of document afterwards and sees only the structure and numbers, no documents.

How long

The structure is not content of your documents and remains after an account is deleted: a structure that applies to everyone because other people’s documents may use it; a structure that applies only to you as well, without being available to any account afterwards. It then refers to a deleted account without name or email address. What comes from your document, such as passages quoted in a proposal, is deleted with the document and with your account.

Basis

Art. 6(1)(b) GDPR and in addition Art. 6(1)(f) GDPR (section 3). Your right to object under Art. 21 GDPR is not affected.

7. Acceptances

When you accept the terms, Pevidy stores your account, the version, the time, the language you read them in and a checksum of the text. The entries are only ever added to, never changed, and they are deleted with your account. That you accepted is also recorded in your account’s history and remains like the other logs (section 11). Your consent to a hand-over to a law firm is recorded with the hand-over (section 10).

8. Team

Members of the Pevidy team sign in to the administration area with a second factor as well, a time-based one-time code (TOTP). Supabase manages the secret key for it; Pevidy only stores whether a factor is set up, since when, when it was last confirmed, the factor’s identifier at the provider and whether, when and by whom it was reset. This is deleted with the team member’s account. It does not apply to accounts without a team role.

In the administration area the team sees only structures and numbers for kinds of document, for reviews and for costs. In account management it sees for an account: the email address, the display name and the account’s internal identifier; the account status and the account’s kind (standard, test or demo); the plan with its plan version; when the account was created, confirmed, suspended, requested for deletion, deleted and finally removed, together with the state of a deletion with the end of its period and whether the account can still be restored or finally removed; the use of the plan’s features (used, limit, remaining and when counting starts again); the number, kinds and state of its documents (not their contents); the storage used per area with the number of files; the number of active and ended sessions and the latest sessions with device name, last use and whether they have ended; when the account was last active; the latest events in the account’s history (who triggered them, kind, time, reason and a technical process identifier) and failed processing (which process, a category of error, an error message without content from your documents and the process identifier). In the list of accounts it searches by email address, display name or identifier and filters by account status, kind and plan. It uses this to help with faults, misuse and requests about the account.

If you write to the team through “Something wrong?”, team members with the administration or support role read your text, the address you sign in with, your account’s language, kind and status, and the page you were on. Of the case or document you had open they see only its structure: the state of the case and whose turn it is, the kind of document, how far it has been read and the number of pages — never a title, a file name, a value or a document’s text. Every opening of your message is logged in your account’s history. The answer is in the app under “Your messages to us” and also comes by email from support@pevidy.io to the address you sign in with — regardless of your notification settings, but never to a blocked address. Replies to that email do not arrive. So write only what the team needs in order to help. Art. 6(1)(b) GDPR — you are asking for help with the service. How long the messages are kept is in section 11.

9. Notifications, digest and calendar

Pevidy lets you know when there is something to do in one of your matters: in the app always, by email the way you choose in the settings. The emails go only to the email address you sign in with.

Which emails

Three groups: deadlines; steps where it is your turn (such as missing proof, a change in a case or a step you put off until later); and everything else (processing, export, account). For each group you choose: straight away by email, in the daily digest in the morning, or only in the app. There is at most one digest a day, and only when there is something to report.

What they say

No content from your documents and matters: no name, no amount, no reference number, no document title. An email says that there is something and takes you into the app with a link; the digest contains only numbers and a link. No advertising, and nothing that measures whether you open an email or click a link.

Default and legal basis

If you have not chosen anything, you get deadlines straight away by email and everything else in the daily digest; if you had already chosen, your choice stays. Pevidy does not send anything from before this default applied. If an immediate email falls into the quiet hours you can set, it comes in the next digest. Pevidy sends notices about a fault that affects your account regardless of your choice. Art. 6(1)(b) GDPR — reminding you of deadlines and of steps in your matters is part of the service. You can set any group to only in the app at any time.

Sender

The emails come from no-reply@notify.pevidy.io, an address of its own used only for emails from Pevidy to you. They are signed so that your mailbox can tell they really come from Pevidy. Replies to this address are not read. Where an email expressly allows a reply (such as a request for missing proof), your reply goes to your own Pevidy address.

Unsubscribing

Every notification and every digest contains a link to unsubscribe, and your email program can show its own button for it. The link applies only to your account and the group of the email. If you confirm on the page it opens, or use your email program’s button, you get emails of that group only in the app. Merely opening the link changes nothing.

Bounces and complaints

Every email carries its own return address. If an email does not arrive, for example because the address no longer exists, or if your mailbox provider reports that you marked it as unwanted, Pevidy learns about it that way. Only the kind of report, a status code, the time and a checksum (so that the same report counts once) are stored, linked to the email concerned and your account — never the report itself; the entry is deleted after ninety days. After a permanent failure, repeated temporary failures or a complaint, Pevidy sends no more notification emails and no more fault notices to that address; the app stays as it is. The settings tell you why, and if you switch the emails back on there, the block is lifted. Reports about emails from other senders are discarded without storing anything from them. The Pevidy team sees only numbers, no addresses. Art. 6(1)(f) GDPR — the legitimate interest in not sending emails to addresses that do not accept or do not want them, and in keeping delivery reliable.

Calendar feed

If you create a calendar feed in the settings, you get a private address your calendar can subscribe to. The feed contains your open submission deadlines, expected answers and the days on which a step you put off is due again, as all-day events from thirty days back to twelve months ahead: with a general title without names, amounts or other content, a reminder the day before and a link to the case in Pevidy. The link contains an identifier of the case, no content. Pevidy stores only a checksum of the address, never the address itself; you see it once when you create it. It also stores when the feed was created and last fetched. Against too many requests, Pevidy counts them per feed and IP address within a short window, both only as a checksum. Art. 6(1)(b) GDPR — you create the feed yourself.

Who fetches the feed

Not your device, but the calendar service you subscribe with — such as Google, Apple or Microsoft — regularly, from its own servers. The events and links are then also held by that service and subject to its terms; Pevidy has no influence on that. Anyone who knows the address sees the events. That is why you can replace it with a new one or revoke it at any time; the old one stops working at once.

10. Sending to third parties

If you have Pevidy transmit a sending (terms, section “Sending to third parties”), an email goes from your Pevidy address to the recipient you saw in the preview and confirmed by typing their address — for example the folder of a claim to your insurer. Nothing goes out without your confirmation.

What is transmitted

A German email with a fixed text: subject, greeting, details with a source (your name from your account, the policy number or a booking number from your papers), and the closing line “Transmitted with Pevidy on behalf of …” with your name. With it the folder with its cover letter, as PDF; you can open it in the preview. It may contain special categories under Art. 9 GDPR, such as health data in a claim, and it states what your folder states, such as your contact details. No model writes the text of the email; a language model drafted the cover letter in the folder (section 5).

Who gets it

Exactly one recipient per sending, without copies. The address comes from a document of your case that names it word for word, or from you — never from a search, an AI answer or the sender of a message that came in. The email goes through Pevidy’s own mail server. The Pevidy team sees only numbers about sendings, never addresses, texts or attachments.

Basis

Art. 6(1)(b) GDPR — you instruct the transmission with your confirmation. Where a sending contains data under Art. 9(1) GDPR, the transmission rests on your explicit consent under Art. 9(2)(a) GDPR, which you give by confirming exactly that sending. Handling bounces and complaints: Art. 6(1)(f) GDPR.

Proof of sending

For every sending Pevidy records what you confirmed: the recipient and where the address came from (document, page and a short excerpt, or “entered by you”), the sender, subject, text, the name, size and checksum of each attachment, the Message-ID and when Pevidy’s mail server accepted the email. “Sent” means accepted, not delivered. You can view and download the proof at your case, also while sending through Pevidy is switched off; it is part of your data export. How long it is kept is in section 11.

Bounces, complaints and replies

If a mail server reports that it cannot deliver a sending, the report lands in your post like any other email. Pevidy matches it to the sending by its Message-ID. If the address is unknown, or a sending to the same address repeatedly cannot be delivered, Pevidy tells you and blocks the address for your account until you enter it as the recipient again, at most as long as Pevidy keeps the proof of that sending. If a recipient reports a sending as unwanted, Pevidy counts it and notifies the team at once, without content. Stored are the kind of report, a status code, the time and a checksum (so that the same report counts once), linked to the sending and your account — the entry never holds the report itself; the entry is deleted after ninety days. A bounce is also noted on the sending, for as long as its proof of sending is kept. Replies to a sending go to your Pevidy address; when they refer to the sending, they appear with your case.

Handing a case to a law firm

If Pevidy’s register of law firms names a law firm for the country of your case, you can have the case reviewed by it (terms, section “Handing a case to a law firm”). This is a sending as above, with these differences: the law firm’s address comes from the register of law firms, which only the Pevidy team keeps, not from your papers. Pevidy recommends no law firm; all law firms of a country are listed in alphabetical order, with none preselected. What is transmitted is a hand-over sheet (your name, your Pevidy address for the reply, the title and state of the case, the deadlines with their day and place in the document, and the list of files) and the files you select: documents of the case and, if there is a current folder for a claim, that folder. No model writes the text of the email or the hand-over sheet. The law firm is not a processor of Pevidy; it processes the papers in its own responsibility.

Basis of the hand-over

Your consent under Art. 6(1)(a) GDPR and, where the papers contain data under Art. 9(1) GDPR, under Art. 9(2)(a) GDPR. Before the hand-over you read the consent text, tick a box and type the law firm’s address; without that nothing goes out. You can withdraw the consent at any time with effect for the future, on the hand-over’s page, also before you have agreed to new terms of use. After that Pevidy transmits nothing more from this hand-over; a transmission already under way may still reach the law firm. Pevidy cannot delete what is already with the law firm; for that you turn to the law firm. The hand-over does not stop any deadline.

Proof of the hand-over

For every hand-over Pevidy records: the version of the consent text and its checksum, the language, the time of your consent, the law firm with its country, name and address at that time, the name, size and checksum of each file, a checksum over everything you confirmed, and the sending with its proof of sending. You can download the proof on the hand-over’s page; it is part of your data export and remains after a withdrawal (section 11). Replies from the law firm go to your Pevidy address; when they refer to the hand-over, Pevidy shows them with your case. Such a reply does not change the state of your case and is not an answer of the other side; the same holds for any other mail from the law firm’s address. If the law firm’s address is unknown or repeatedly cannot be delivered to, Pevidy tells you and blocks the address for your account, at most as long as Pevidy keeps the proof of sending of that hand-over (three years after the sending); the Pevidy team then checks the entry in the register. The Pevidy team sees only numbers per country and state about hand-overs.

11. How long

Account data, documents and matters

As long as your account exists. If you delete it, the deletion can be undone for thirty days; after that the data is removed.

Sessions

As long as your account exists. A session is valid until you sign out, end it or it expires; after that it is kept as ended (device and program, approximate location as a city, last use, time it ended) so that it cannot become valid again, and it is deleted with the account. The IP address the city is worked out from is not stored. You can see open sessions in the settings and end them one by one or per device.

Your account's logs

As long as the account exists, because every statement Pevidy makes has to stay traceable. After the account is deleted, records of what happened in it may remain; document and email contents are not part of them.

Log of AI calls (without contents)

Thirteen months from the call; after that the entry is deleted. If you delete your account, the link to your account is removed with the deletion.

Acceptances of the terms

As long as your account exists; they are deleted with the account. That you accepted is also recorded in your account's history and remains like the other logs (see there).

Learned structure of kinds of document

No fixed period. It contains no contents of your documents and remains after an account is deleted; it then refers to a deleted account without name or email address (see structure learning).

Data exports

You can download the file for seven days after it is created, and not after that. It is deleted at the latest with your account.

Daily digest by email

Ninety days after the day of the digest; only the day, whether it was sent and the numbers are stored, no content. It is deleted with your account in any case.

Bounces and complaints about emails

Ninety days after it arrived. Stored are the kind, a status code, the time and a checksum (so that the same report counts once), linked to the email or sending concerned and to your account; the entry never holds the report itself. A block of your address for notification emails lasts until you switch the emails back on in the settings, and ends with your account at the latest.

Sendings to third parties and their proof of sending

Three years after Pevidy's mail server accepted the sending; a sending that was never accepted (draft, cancelled, failed or unclear) three years after its last change. A draft you never confirmed is also deleted as soon as you delete a document it names as evidence or attachment. Stored are the recipient and where the address came from, the sender, subject, text, the name, size and checksum of each attachment, the Message-ID and the times; the attachments themselves are your documents and stay as long as they exist. Everything is deleted with your account in any case.

Recipients of your cases

As long as your account exists; they are deleted with the account. If a sending to an address came back, the address stays blocked for your account until you enter it as the recipient again, at most as long as Pevidy keeps the proof of that sending (three years after the sending).

Hand-overs to a law firm and your consent

Three years after your consent; a hand-over you never consented to (draft or set aside) three years after its last change. A hand-over you never consented to is also deleted, together with its hand-over sheet, as soon as you delete a document it names. Stored are the occasion, the state, the law firm as of your consent, the version, checksum, language and time of the consent, the name, size and checksum of the files, the link to the sending and, where there are any, the reply and the withdrawal; a withdrawal changes nothing about that. The sending itself is kept as long as every sending to third parties. The hand-over sheet and the other files are files of your account. Everything is deleted with your account in any case.

Calendar feed

As long as it is valid. If you revoke or replace it, the entry is kept without a valid address for thirty more days and then deleted; it is deleted with your account in any case.

Messages to the team

Thirteen months after the team answered or closed it (whichever came later); an open message stays until it is finished. It is deleted with your account in any case.

Requests for early access to the beta

Until the invitation or the withdrawal, at most twelve months after the confirmation; deleted within two days after that. An unconfirmed request is deleted at the latest eight days after the last request.

Backups

The database is backed up nightly; fourteen daily and eight weekly copies are kept. Deleted data can therefore still be contained in a backup for up to eight weeks, from which it would only be restored in a disaster.

12. Your rights

You can ask at any time for:

• Access to what is stored (Art. 15 GDPR).
• Rectification of incorrect details (Art. 16 GDPR).
• Erasure (Art. 17 GDPR). In the settings under “Delete your account”; after that the deletion can be undone for 30 days, so that a mistake is not final.
• Restriction of processing (Art. 18 GDPR).
• Data portability (Art. 20 GDPR) — a machine-readable export of your data, also in the settings.
• Objection to processing based on legitimate interests (Art. 21 GDPR).
• Withdrawal of any consent, with effect for the future (Art. 7(3) GDPR).

You also have the right to lodge a complaint with a supervisory authority (Art. 77 GDPR). The data protection authority of the German state in which the controller is based is responsible.

13. Cookies and requests to other servers

Pevidy only stores in your browser what is needed to run it: the session cookie that keeps you signed in, two short-lived cookies for the duration of signing in (the purpose of the sign-in and a check value of the sign-in procedure), two cookies that remember how you set up the sidebar, an entry in local storage that remembers whether you hid the guide, and — only when you follow a team invitation — the invitation code in this tab’s storage until you are signed in. This is strictly necessary within the meaning of §25(2) no. 2 TDDDG and therefore needs no consent. There are no analytics, advertising or tracking cookies.

The public pages load nothing from another server: the fonts are part of the delivered package, there is no analytics script and no embedded content. Your browser only talks to pevidy.io.

One exception in the signed-in area: when you open a document to see the place Pevidy relies on, your browser loads the document viewer. Depending on the setting it comes from pevidy.tech, Pevidy’s own server for document tools, or from cdn.cloud.nutrient.io; in the second case your IP address is transmitted to Nutrient. The viewer from pevidy.tech only shows the document in your browser and sends it nowhere. That only happens at the moment you look at a document — not when you sign in and not on the public pages.

14. Automated decisions

Pevidy proposes and gives reasons; you decide. There is no decision based solely on automated processing within the meaning of Art. 22 GDPR: no case is filed, signed or sent without your approval. Where Pevidy read something from a document, it names the page it is on.

15. Early access to the private beta

On the start page you can ask for early access to the private beta of Pevidy. You do not need an account for it.

What is stored

Your email address, in lower case; if you choose to tell us, what you would love to have off your plate (from a fixed list) and how you heard about Pevidy (at most 200 characters); the language of the confirmation email; when you asked, confirmed or withdrew, and how many confirmation emails went to the address in the last seven days; of the two links in the email only a checksum, never the links themselves. No IP address, no device, no account.

What for

Only to invite you to the private beta. Your optional answers help us put the first group together. No advertising, no disclosure to third parties, no tracking: the emails contain neither tracking pixels nor tracked links.

Confirmation

After the request Pevidy sends an email with a link to the address (double opt-in), through Pevidy’s own mail server. Only once you confirm there are you on the list. The link works for seven days; without a confirmation the request is deleted at the latest eight days after the last request. The page never tells anyone whether an address is already on the list. Against abuse, Pevidy counts requests per IP address in a window of one hour, only as a checksum under a secret key of the server that is deleted two days after the last request, and sends at most three confirmation emails in seven days to one address.

Legal basis

Art. 6(1)(a) GDPR — your consent, which you give by confirming. The confirmation email itself and the protection of the form against abuse: Art. 6(1)(f) GDPR.

How long

Until your invitation or your withdrawal, at most twelve months after your confirmation; the deletion happens with the next daily run. After the invitation or the withdrawal the request is deleted within two days; until then the address gets no more email.

Withdrawal

At any time and without giving a reason, with the second link in the confirmation email, or with a message to the address in section 1 — then we delete the request at once. The withdrawal applies to the future (Art. 7(3) GDPR); your answers are removed at once.

Who sees it

Team members with the role Administration see only two numbers in the admin area (confirmed, unconfirmed). For the invitations, a person with that role exports the confirmed requests (address, language, your answers) with a tool on the server; every export is logged with its reason and the number of addresses, without the addresses.