Privacy Policy

This is Evorrah’s Privacy Policy. Our cookie policy is the Cookies & local storage section below, and how long we keep each kind of information is set out under Data retention. Our Terms & Conditions — which are also our service agreement, and which contain our cancellation and refund policies — are at evorrah.com/terms. If you are a host, the Data Processing Terms set out how we handle your guests’ details on your behalf.

Who we are

Evorrah is a bespoke event design studio, operated by INNOVATECHBRAZIL LLC, a Delaware limited liability company with its principal office at 40 SW 13th St, Suite 204, Miami, FL 33130, USA, doing business as Evorrah. Our website is evorrah.com. For all privacy-related inquiries contact hello@evorrah.com.

Our data protection officer. Under Brazil’s data protection law (the LGPD) we name a person in charge of data protection, called the encarregado: Bryan Buch, who can be reached at hello@evorrah.com — write “Data protection” in the subject line and it reaches him directly.

Who decides what happens to your data

Data protection law asks who decides why and how information is used. For Evorrah the answer depends on whose information it is.

• Our clients, visitors and inquirers. For your own account, your payment, your answers in Your Vision, the inquiries you send us, our own emails to clients and this website, Evorrah decides, so Evorrah is the controller.
• A host’s guests. When a host adds guests, or guests answer the host’s invitation, the host decides who is invited and why. We keep and use those details on the host’s behalf and on the host’s instructions, only to run that host’s event — the operator under the LGPD, the processor under European law. Our Data Processing Terms are the agreement with the host that says so.
• What we do with guests’ details for our own reasons. A few things we do for ourselves: keeping the service secure, keeping the record of a guest’s consent or of their request to stop being contacted, answering a guest who writes to us directly, and the “By Evorrah” tap and the new-client count described below. For those, Evorrah is the controller.

What we promise guests, whoever the host is. Some hosts are private people planning a family occasion. Whatever the law asks of them, every protection on this page applies to their guests’ details: they are used only for that host’s event, never sold, never used for Evorrah’s own marketing, and you can always write to us directly about them.

Why we are allowed to use it

Every use of personal data needs a legal reason — a lawful basis. These are ours. References are to Brazil’s LGPD and, where it applies, the European GDPR.

What data we collect and why

We collect the data we need to deliver your design suite, run the guest side of your event and communicate with you about your project:

• Name & partner name — used to personalize your designs and address emails.
• Email address — used to create and access your private portal, and send order and delivery notifications.
• Your free runbook request — if you ask us to email you the runbook from our free planning page, we keep your email address and the answers it was built from (the kind of event, the date, the place and the guest count). We send you the link you asked for, then two short notes over the next week: one about what Evorrah would take off your hands, one inviting you to a free call. Then nothing more. Each note has a one-click unsubscribe, and the notes stop if you book a call or become a client. What you write as your vision on that page stays in your browser and is never sent to us.
• Phone number — collected optionally; used to contact you about your project when it is urgent, and for the test message you can send to your own phone from your portal. If you accepted advertising cookies, a one-way hash of it may be sent with your purchase, as described under How we use your data.
• Event details — event type, date, venue, and name used to produce your bespoke design suite and, when we write to you about Evorrah, to make that message about your own event.
• Your Vision answers — color palette preferences, style descriptions, moodboards, inspiration images, and notes submitted through your portal. This forms the creative brief for your project.
• RSVP guest list data — when you use the guest-list and RSVP features, we collect on your behalf the details you or your guests provide, which can include: guests’ names and plus-one names, household members (including children’s names, where you add them), email addresses and phone numbers, postal addresses (for mailed pieces), attendance status, dietary needs and allergies, accessibility needs, transport needs, personal messages left in the guestbook, and the photos and videos guests add to the event album (location data is removed from photos by our upload page before they leave the guest’s phone, and from videos on our server). You are the data controller for your guests’ data and confirm you are authorized to share it; we process it solely to produce your guest list, personalized pieces, seating plan, and RSVP tracking — never for marketing to your guests.
• The “By Evorrah” mark. If you tap the small “By Evorrah” mark on an event page, we note the tap, which event it was on, and — if you came from the personal link we sent you — that it was you. Nothing else: no message, no device identifier, nothing passed to anyone else. We keep it for 90 days, only our own team can see it, your host never does, it is never a reason to contact you, and it is deleted whenever the rest of your guest details are.
• When an invitation is opened. When a guest opens their invitation, or a piece made for them, we note that it was opened, so the host can see it arrived. We keep that note for 90 days.
• Whether a guest later becomes a client. We keep a one-way, scrambled code made from each guest’s email address — a fingerprint, not the address itself. If someone later becomes an Evorrah client with the same email address, the two codes match, and we count that an invitation led to a new client. It is only a count for our own team: it is never a reason to contact you, your host never sees it, and it is deleted whenever the rest of your guest details are.
• Payment data — all payments are processed by Stripe. We never see or store your full card number or banking credentials. We store only the Stripe customer ID and payment status.
• IP addresses — logged for security purposes (rate limiting, fraud prevention). Not used for profiling or marketing.
• Portal session token — a cryptographic token stored in your browser’s local storage to keep you logged in. Rotated on password reset.

How we use your data

• Deliver and personalize your design suite
• Send transactional emails (order confirmation, portal access, design delivery)
• Process and record payment via Stripe
• Maintain your private portal and project history
• Improve how we design and run events, as described just below
• Protect the platform from abuse and unauthorized access
• Comply with legal obligations

What we learn from our work. To improve how we design and run events, we study three things our clients give us: the design choices they make, the changes they ask for in a revision round, and their feedback. They stay inside Evorrah and the services that work for us: we do not publish them, show them to another client or sell them. What we have learned in general, in a form that does not name a client or an event, may be kept after an account is deleted. We never use guests’ details for this. If you would rather your event were left out, tell us at hello@evorrah.com; nothing about your service changes. Our Terms say the same.

We never sell your personal data, and we do not share it for any purpose other than those listed above and the advertising measurement described next.

We do use advertising and analytics services to understand how people find us and whether our ads work: Google Analytics 4, Google Ads and the Meta (Facebook/Instagram) pixel. These set identifiers in your browser and, when you make a purchase, we may send Google and Meta a one-way cryptographic hash of your email address and phone number so they can confirm the sale came from an ad. Meta also receives your IP address and your browser’s user-agent, which it uses to recognize the same visit. A hash cannot be reversed back into your details, and we never send these companies your name, address, event details or design work. All of that is off by default and only runs if you accept cookies on the banner — decline, and no advertising or analytics identifier is set at all.

One thing does not depend on that choice, and we would rather say so than leave it out. If you arrive from a Google ad, the click identifier travels in the web address itself, so we still hold it whether or not you accepted cookies. When a purchase completes, a nightly job reports the amount to Google Ads against that click identifier. It carries no name, no email address and no phone number — a figure and a click. Nothing equivalent is sent to Meta or anyone else when you decline.

Your People: guest lists kept between events

Many hosts, and every organization (a university, a foundation, a firm, a membership body), invite many of the same people again and again. So that they do not rebuild a guest list and ask the same questions for every occasion, Evorrah can keep a standing list of people on their account. We call it Your People. If you are a guest of someone who uses it, this section is about you.

What it holds. For each person the host or organization adds: their name and how to address them, how to reach them (email, phone, postal address, language), who they come with, what an event needs to know (dietary requirements, accessibility needs, whether they are an adult or a child), the host’s own notes and labels, when each detail was last confirmed, and which of that host’s past events they were invited to, answered and attended.

Where it comes from. Only from the host or organization (a list they add, or the guest list of one of their earlier events that they choose to keep) and from the guests themselves, when they answer an invitation. We never buy, rent, scrape or add information about anyone from anywhere else.

Sensitive details. A dietary requirement can reveal a religion or a health condition, an accessibility need can reveal a disability, and an age band can identify a child. The host decides whether to ask for them and guests decide whether to give them. We hold them for one reason: an event cannot be run safely or with respect without them. We use them only to run that host’s events, share them only with the people running that event, and never use them to decide anything about you. An allergy or dietary answer a guest gives is saved only with their tick: see Allergies, dietary needs and accessibility.

What it is used for, and what it never is. Sending that host’s invitations and reminders, building their guest lists and seating, and showing them who replied and who came. A person on one host’s list is never used for another host’s events, for Evorrah’s own marketing, for advertising, or to build a profile that is sold or passed on. The list never sends anything by itself; a host chooses who to invite to each event.

Who decides. The host or organization decides who is on their list and why. In data-protection terms they are the controller, and Evorrah keeps the list on their behalf and only for the purposes above, as their processor. By adding people, a host confirms they are entitled to hold those details and to keep them between events.

Removing someone. When a host removes a person, that person disappears from their list and from every future invitation straight away; their past events keep the guest’s name so that old seating plans and records stay accurate. If a host records that someone has died, that person is never suggested for an invitation again. The list is part of the host’s client record, so it is kept and deleted with it: see Client records under Data retention. When a client record is erased, its People list is deleted with it.

If you are on someone’s list. Everything under Your rights applies to you. The quickest route is usually to ask the host or organization, because they decide who is on their list. You can also write to hello@evorrah.com with the subject line “Privacy Request”: we will answer within 7 days, and if the request is for the host to act on, we will tell them and tell you that we have.

Where it is kept. With the rest of our data, in the database listed under Third-party processors, which is hosted in the United States. If you are writing from the EU, the UK or Brazil, that means your information is stored outside your country.

Allergies, dietary needs and accessibility

An allergy or a medical diet is information about someone’s health, and the law protects it more strictly than a name or an address. So is an accessibility need, and a dietary choice can reveal a religious belief.

• Allergies and dietary needs you give on your reply. When you tell your host about an allergy or a dietary need on your reply page, a box appears beneath it: “I agree that my host and Evorrah use this to plan my meal.” We save the answer only if you tick it. If you do not, nothing new is saved and your reply still goes through. One tick covers the whole reply, including the people in your household you are answering for. We keep a record of the tick, which version of the wording you saw and when.
• What it is used for. Planning your meal and keeping you safe at the event: your host and the people they appoint to run the catering and seating see it. Nothing else — never to decide anything about you, and never for any other event or host.
• Accessibility needs. If you tell your host about one, it is used only to make the event accessible to you — at the door, in the seating and in what the venue is told. Giving it is up to you, and you can change or remove it from your personal link while replies are open.
• What your host enters. A host may note a guest’s dietary or accessibility need themselves, from what that guest has told them. That is the host’s information about their own guest, held on their behalf; you can ask the host, or us, to correct or remove it.
• Changing your mind. You can remove an allergy or dietary answer from your personal link, or write to us, at any time. Taking it back does not undo what was done with it before.

Text messages (SMS)

If you are a client, we write to you by email; the one text we send a client is the test message you can send to your own phone from your portal. If you are a guest at an event we are running the guest list for, the host may send you messages about that event: an invitation link, an RSVP reminder, a change of time or place, or travel and arrival details.

• How you come to receive them. Clients give a mobile number when they book or in their portal. Guests are added by their host, who is responsible for having a reason to contact them. We do not buy phone numbers and we never send marketing texts to a number we were given for an event.
• How often. There is no recurring campaign. Message frequency varies with your event — typically a handful of messages across the weeks around it, and none once it has passed.
• The full messaging disclosure — sender identity, what a guest receives, how consent is obtained and how to stop it — is set out on our Text Messages page.
• How to opt out. Reply STOP to any message to opt out. That number is opted out immediately; we will send one confirmation and nothing after it. Reply START to opt back in. Every message we send carries this instruction. You can also email us and we will remove the number by hand.
• Help. Reply HELP, or write to hello@evorrah.com.
• Cost. We do not charge for messages. Message and data rates may apply from your own mobile carrier, and delivery depends on your carrier — we cannot guarantee it.
• What we keep. The number, the message we sent, when it was sent, whether the carrier accepted it, and whether you opted out. We keep opt-outs indefinitely, because forgetting one would mean texting someone who asked us not to.
• Who sees it. Your number and the message pass through Twilio, our messaging carrier (listed below). Nobody else. We never sell or share phone numbers, and we never pass them to advertisers. Mobile phone numbers and SMS consent are never shared with third parties or affiliates for marketing or promotional purposes.

WhatsApp

Where a host’s event sends messages on WhatsApp, we write to a guest there only after the guest has said yes themselves: by ticking “Send me updates about this event on WhatsApp at this number. I can reply STOP at any time.” on their own reply page, or by sending us START on WhatsApp. A host cannot switch it on for a guest. A guest who has not said yes gets email or a text message instead. Taking the tick off, or replying STOP, ends it. The message and the number pass through Twilio and WhatsApp, which is run by Meta.

Emails, and whether they were opened

Our emails are sent through Resend. They carry a small image that tells us whether an email was opened, so that we know an invitation or a reminder reached you before we send another, and do not chase someone who has already read it. We do not track which links you click: the links in our emails go straight to where they say. Whether an email was opened is kept with the record of the emails we sent, for the period under Data retention. Most email programs let you block images, and then nothing is reported.

Third-party processors

• Twilio (twilio.com) — SMS delivery. Receives the recipient’s phone number and the message text in order to deliver it, and returns whether the carrier accepted it. Twilio’s privacy policy applies.
• Stripe (stripe.com) — payment processing. Card details are entered on Stripe’s own pages and never reach us.
• Supabase (supabase.com) — secure database and file storage hosted on AWS in the US.
• Resend (resend.com) — transactional email delivery.
• Anthropic / Claude (anthropic.com) — AI assistance inside Evorrah’s workflow. What you write in Your Vision is sent to this service: to check your brief for gaps before you submit it, to help Evorrah develop your creative direction, and to draft copy for Evorrah and its marketing. If we write to you about Evorrah, that draft is personalized with your first name, the occasion you asked us about, your event name and your plan — never your email address or phone number. Under Anthropic’s commercial terms, data sent through their API is not used to train their models. We never send your payment details, and every design that reaches you is reviewed by a person. The notes you write when you ask for a change to a design are sent to it, to help us plan the change. When you ask us to read a supplier’s proposal or contract, that file is sent to it, to pull out the prices, dates and terms. We keep a record of what was sent to this service and what it answered for 90 days. Some details about your guests are sent to this service too, for three jobs. To suggest who should sit together, it receives the names on the event’s guest list along with the note being read — the seating notes, story and special requests in your brief, a seating note typed into the seating tool, or the note a guest leaves with their RSVP. To read a guest’s reply to one of our texts or emails — whether they are coming, not coming, or asking something — it receives that reply, the guest’s name and the names of the other guests on the same event; a short plain answer such as “yes”, “no” or “stop” is read without it. On a Fully Handled event day, to draft our reply to a message you send us during the event-day window, it receives your message and the event’s own records: each guest’s name, reply, table, household, plus-one, dietary note and whether they have arrived. Guests’ phone numbers and email addresses are not attached to any of them.
• Image generation services — Recraft (recraft.ai), fal.ai and Google Gemini — used by Evorrah to originate artwork elements such as motifs, textures and backgrounds. They receive the design prompt and any wording that is to appear on the artwork itself (for example your names and event details). They never receive your contact details, payment information or guest list.
• Google reCAPTCHA v3 (google.com) — bot detection on public forms. Our checkout, sign-in, contact and chat forms are checked by it. On pages that carry it, it loads when the page opens, so it receives your IP address and browser signals whether or not you accept cookies — it is what stops the forms being flooded. It receives nothing you typed. Google’s privacy policy applies.
• Google Fonts — typography. Google may log your IP when serving font files.
• jsDelivr (jsdelivr.com) — delivers some of the code libraries our pages use. It receives your IP address when a page loads them.
• Apple (iCloud) — stores copies of our backups.
• Google Analytics 4 & Google Ads (google.com) — audience measurement and advertising performance. The identifiers set in your browser are only active if you accept cookies. Separately, and regardless of that choice, a completed purchase that began with a Google ad is reported to Google Ads as an amount against the click identifier that brought you here — no name, email address or phone number. Google’s privacy policy applies.
• Meta (Facebook/Instagram) (meta.com) — advertising performance measurement. Only active if you accept cookies. Receives a hashed (non-reversible) email address and phone number, your IP address, your browser’s user-agent and Meta’s own cookie identifiers — never your name, your event details or your design work. Meta has no partial mode: the pixel either sends real browser data or it does not run, which is why declining the banner switches it off entirely rather than limiting it.
• Vercel (vercel.com) — website and API hosting. Processes request metadata as part of normal hosting.
• Calendly (calendly.com) — booking a consultation with us. Its booking window loads only when you press the button to book. When you choose a time, Calendly receives your name, your email address and the answers you type into its form, and tells us about the booking so that we can prepare. Calendly’s own privacy notice applies to what you type into it.
• WhatsApp (whatsapp.com, run by Meta) — only for guests who have said yes to WhatsApp themselves, as described above. Receives the guest’s number and the message, through Twilio.

Each of these companies handles this information under its own data protection terms, and we send each only what its job needs. Hosts: the Data Processing Terms list the services that handle your guests’ details and how we tell you before that list changes.

Where your data is processed, and transfers abroad

Evorrah is run by a company in the United States and our team works from Brazil. The services above are based in the United States, and our database and files are hosted there. So if you are in Brazil, the European Union or the United Kingdom, your information is transferred to, and stored in, another country.

• How it travels. Over encrypted connections (HTTPS), between your device, our hosting and the services listed above.
• For how long. For as long as we keep it, under Data retention.
• Why. For the purpose each service is listed for above, and for nothing else.
• Which countries. The United States; and Brazil, where our team reads it. Vercel serves the website from the location nearest to the visitor.
• On what terms — from Brazil. We will put in place the standard contractual clauses approved by Brazil’s data protection authority (ANPD Resolution CD/ANPD nº 19/2024) with the services that receive personal data in the United States. Until each is signed, a transfer relies on the protections in that service’s own data protection terms.
• On what terms — from Europe. The European Union and Brazil recognize each other’s data protection as adequate (EU decision 2026/179; ANPD Resolution 32/2026), which covers information reaching our team in Brazil. For the services in the United States we rely on the safeguards in each service’s data protection terms.
• A copy. You can ask us at hello@evorrah.com for a copy of the terms a transfer relies on.

Data retention

• Client records & Your Vision answers — 5 years after your most recent event with us, then deleted or anonymized.
• Delivered design files — 1 year after your event date, then deleted. We email you 30 days beforehand, and you can ask us to extend the window.
• Delivered design files of a canceled project — deleted 30 days after the cancellation. We email you 7 days beforehand.
• RSVP guest data — 5 years after your most recent event with us, then deleted. Held that long so a host who runs the same occasion year after year does not rebuild their list each time; you can ask us to delete it sooner at any point.
• Guest photographs — 90 days after your event date, then deleted, including the image files themselves. We email you 14 days beforehand so you can download anything you want to keep. These are your guests’ own pictures of themselves, so we hold them for as short a time as we sensibly can.
• Payment records — at least 7 years, to comply with financial record-keeping obligations.
• IP address logs — 90 days for security purposes, then purged.
• Sign-in records — the first part of the IP address and the kind of browser used for each sign-in to a portal: 1 year, then deleted.
• Staff activity records — which member of our team changed what, and when: the record itself is kept indefinitely as the account’s history; the IP address in it is removed after 90 days.
• Consent, opt-out and privacy-request records — what you agreed to or refused, which version of the wording you were shown and when, and each privacy request with our answer: kept indefinitely, including after the rest of your details are deleted, because they are our proof that we had your permission, honored your refusal and answered your request.
• Communication logs — the record of emails we sent you (recipient address, subject, delivery status): 5 years, then deleted, together with whether each email was opened. System health checks: 90 days.
• Guests’ replies by text message — 1 year, then the text of each reply is deleted; the record that someone opted out is kept.
• Check-in and QR code scans — 400 days when linked to a guest; 30 days otherwise.
• Records of what we send to Anthropic and what it answers — 90 days.
• Website browsing records — which pages you looked at and how far you got in the booking flow: kept indefinitely, and only ever recorded if you accepted the cookie banner. Decline it, or withdraw your consent, and nothing is recorded.
• Inquiries and consultation bookings — kept until you ask us to delete them.
• Free runbook requests — your email address and your answers: kept until you ask us to delete them. The follow-up notes end after the second one.
• Backups — our backups are replaced on their own rolling schedule, so a copy of deleted information can survive in them for up to 6 months after the deletion. Backups are never used to serve the product; they exist only to restore it after a failure.

Your rights

Depending on your location (EU/EEA, UK, Brazil, California, Canada, etc.) you may have rights to access, correct, delete, export, restrict or object to the processing of your personal data.

In Brazil, the LGPD (article 18) gives you the right to: confirm whether we hold data about you; see it; correct it; have unnecessary or excessive data anonymized, blocked or deleted; take it to another provider; have data held on your consent deleted; know who we share it with; be told what happens if you refuse consent; and withdraw a consent you gave. You can also ask for a person to review a decision made about you only by automated means. The one thing we do automatically is read a guest’s reply to a text or an email to record whether they are coming, as described under Third-party processors; the host sees that answer and can change it, and so can you, from your personal link or by writing to us.

Where to complain. If you think we have not handled your data properly, please tell us first — we would rather put it right. You also have the right to complain to the data protection authority: in Brazil, the ANPD (Autoridade Nacional de Proteção de Dados, gov.br/anpd); in the European Union, the authority of the country where you live or work; in the United Kingdom, the Information Commissioner’s Office (ico.org.uk).

If you are a guest, four of these you can exercise yourself, straight away — from the personal link in any invitation or reminder we sent you. You can see what we hold about you, correct it, stop receiving messages (one tap on the unsubscribe link in the footer of every reminder, or reply STOP to a text), or ask not to be contacted about that event at all. Nothing has to reach us first and there is nothing to wait for.

Once an event has taken place, that self-service form closes. Write to us and we will make the correction for you.

To export or delete your data, write to hello@evorrah.com with the subject line “Privacy Request”. Those two need a person at our end, and we will respond within 7 days.

Any other request under the rights above goes to the same address, marked “Data protection”, and is answered by our data protection officer. We may ask you to confirm who you are before we act, so that we never hand one person’s details to another. If you are a guest and the request is one for your host to decide, we tell them, and tell you that we have.

Two things deletion does not do, so you know before you ask. It does not remove the business records we must keep about an event that was paid for. And it does not remove records that belong to more than one person — a household, or a message sent to a whole guest list, where we take you out of the recipients and leave the message itself. Separately, if you have told us to stop contacting you, we deliberately keep your email address or phone number on a suppression list for that one purpose, so that a guest list uploaded later cannot reach you again.

Cookies & local storage

We use advertising and analytics cookies and identifiers — Google Analytics 4, Google Ads and the Meta pixel — but only if you accept them on the cookie banner. Until you accept, they are set to “denied” and no such identifier is stored; if you decline, they stay off. You can change your mind at any time: the Cookie choices link in this page’s footer reopens the banner, and your new answer replaces the old one. Nothing needs to be cleared. We keep a record of the choice itself and of any withdrawal — the answer, which version of the wording you were shown, the time, and the page it was given on — and there is nothing in it that identifies you: no name, no email address, no IP address, and no link to your account or your event.

Separately from that choice, we use local storage and session storage to keep you signed in to your portal and to remember which version of a page you were shown. These are required for the site to work and are not used for advertising. Session cookies may also be set by Google Fonts and Vercel as part of normal web operation.

Security

We protect your data with HTTPS everywhere, encrypted passwords (scrypt), Stripe-side payment handling, Row Level Security on our database, rate limiting on sign-in, checkout and public forms, and access tokens rotated on password reset. To report a vulnerability: hello@evorrah.com.

If something goes wrong. We keep a record of every security incident and follow a written procedure for them. If an incident could cause real harm to the people whose data it touches and the law requires notice, we tell those affected and, in Brazil, the ANPD, within the time Brazilian law sets. Where it touches a host’s guest list, the host decides how their guests are told: we tell the host without undue delay and offer to send the notices for them.

Children

Our service is for adults: we do not offer accounts to under-16s, and we never market to or collect information directly from a child. We do, however, hold children’s names when a host includes them on a guest list — a family invited as a household, or a child’s birthday party. That information is provided by the adult organizing the event, never by the child, and is used only so that they are invited, seated and looked after properly.

It is covered by exactly the same protections as every other guest detail: it is never sold, it is shared only with the people running that event, and it is deleted on the schedule set out in Retention — 5 years after the host’s most recent event. If you would like a child’s details removed sooner, or believe information about a child has been added without the organizer’s knowledge, write to hello@evorrah.com and we will remove it.

A child’s details are used only in that child’s interest — so that they are invited, seated and looked after properly — and never for anything else. When a parent or guardian replies for their household and gives an allergy or dietary need for a child in it, the parent’s tick is the consent for it (see Allergies, dietary needs and accessibility).

Changes

The “Last updated” date above reflects the current version. If a change affects how we use your data, we tell our clients by email before it takes effect.

Contact

hello@evorrah.com — for anything about your personal data, write “Data protection” in the subject line and it goes to our data protection officer, Bryan Buch.