Privacy policy

Last updated: 19 November 2026

This is an English translation of our German privacy policy at regyva.com/de/datenschutz. If the two versions differ, the German version applies.

1. Controller

REGYVA LLC
2108 N St Ste N
Sacramento, CA 95816
USA
Email: info@regyva.com

2. Overview

This website presents Regyva. Our own Regyva pixel runs on every page and lets us analyse where visitors come from and which path leads to an enquiry or booking. What it stores and sends is described in section 8. We do not embed videos, maps or social media content from third parties. We serve fonts from our own server. Beyond that, we process personal data only as far as necessary to operate the website and to handle your enquiry. What the Regyva app does with connected TikTok, Instagram, YouTube and Google Ads accounts is described in section 9.

3. Hosting and server logs

The website runs on a server of Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany, in the Falkenstein data centre in Germany. With every request, the server processes technically necessary data: IP address, date and time, requested address, referrer, browser and operating system. We do not keep an access log with this data.

The website writes only technical messages to its log, no form contents and no IP addresses, in some cases a random identifier of your request. These messages are deleted as soon as we deploy a new version of the website.

To protect against abuse, we briefly count how often forms are submitted from an IP address. This counter exists only in the server's memory, is never stored permanently and covers only the last ten minutes.

The purpose is delivering the website and keeping it stable and secure. The legal basis is Art. 6(1)(f) GDPR, our legitimate interest is secure and functioning operation. Hetzner processes the data on our behalf (Art. 28 GDPR). The data stays in Germany.

4. Demo request and chat

You request a demo in two steps: first a short form, then a chat.

In the first step, you enter your name, email address, company, your website or Instagram profile (field "Website or Instagram"), business model and revenue range. When you submit, we also transmit how you came to the page: campaign parameters from the link (utm_source, utm_medium, utm_campaign, utm_content, utm_term), click identifiers from Google and Meta (gclid, fbclid), the previously visited page and the landing page. The page reads this information from the address bar and keeps it only in your browser's memory. It is transmitted only when you submit the form. We do not pass it on to Google, Meta or other advertising networks. The legal basis is Art. 6(1)(b) GDPR (handling your enquiry) and Art. 6(1)(f) GDPR, our legitimate interest is to recognise which path your enquiry took to reach us. Submitting the form is not consent: the information is part of the address your browser sends anyway, and nothing is stored on or read from your device for this purpose. You can object at any time under Art. 21 GDPR to processing based on Art. 6(1)(f) GDPR.

Independently of the form, the Regyva pixel records information about your origin itself and stores it in your browser. This is described in section 8.

In the second step, you write with our chat assistant. It asks what is going wrong for you today, tells you whether Regyva fits, and can take a phone number for a callback during the conversation. You then choose a time for the demo on the page. We store every message, yours and the assistant's, on our server with your enquiry immediately after it is sent, so that we can read the conversation before the demo.

If the booking step shows no free time or our calendar is currently unavailable, you can enter a phone number for a callback there instead. A phone number you provide in the chat or in the booking step is stored with your contact details.

The assistant's replies are generated by an AI model from Anthropic. For this, Anthropic receives your company, your business model, your revenue range and the chat messages, not your name and not your email address. What you write in the chat goes to Anthropic as you write it. Please do not write sensitive data in the chat, such as health data or data about your customers.

The provider is Anthropic, PBC, 548 Market St, PMB 90375, San Francisco, CA 94104, USA. Anthropic processes the data on our behalf (Art. 28 GDPR), does not use it to train its models and, according to its own information, deletes it within 30 days. The transfer to the USA is based on the standard contractual clauses of the European Commission (Art. 46(2)(c) GDPR).

If you book an appointment, we transmit your name, email address and time zone to Calendly, which we use to manage our appointments. In addition, we transmit your answers to the appointment's questions so that we can prepare for the demo: your website or Instagram profile, your revenue range, the tools you use, what is currently going wrong for you, and a short note from the conversation, in each case as far as the appointment asks for it. The recipient is Calendly LLC in the USA. Calendly uses this to add the appointment to our calendar. The transfer to the USA is based on the standard contractual clauses of the European Commission (Art. 46(2)(c) GDPR). Without a booking, Calendly receives nothing.

What the assistant says about your case is an assessment of whether a demo makes sense. It is not an automated decision that produces legal effects concerning you or similarly significantly affects you (Art. 22 GDPR). Regardless of this, you can reach us by email at any time.

We process your information and the chat to handle your enquiry, arrange an appointment or a callback and prepare a possible contract (Art. 6(1)(b) GDPR). We process the information about your origin to understand which paths lead to enquiries (Art. 6(1)(f) GDPR).

5. Waiting list

As long as Regyva is not yet available, you can sign up for a waiting list. For this, we process your name, email address and company to inform you as soon as Regyva launches (Art. 6(1)(b) GDPR). You can unsubscribe at any time by email.

6. Contact by email

If you write to us, we process your message and your contact details to reply to you. The legal basis is Art. 6(1)(b) GDPR if it concerns a contract or an enquiry about one, otherwise Art. 6(1)(f) GDPR. Our mailbox is hosted by Google (Google Workspace). Google may also process data in the USA. Google LLC is certified under the EU-US Data Privacy Framework.

7. Retention period

We keep enquiries, waiting list entries and emails as long as we are handling them. If no contract is concluded, we delete them no later than 24 months after the last contact, unless a statutory retention obligation applies.

We delete chat conversations earlier: if you do not become a customer, we delete the conversation 12 months after the last message.

8. Regyva pixel and browser storage

The Regyva pixel, our own analytics tool, runs on every page of this website. It is loaded from info.regyva.com and sends its data there. We use it to analyse where visitors come from and which path leads to an enquiry or booking.

As soon as the page loads, before you have chosen anything in the cookie banner, the pixel stores entries in your browser, as a cookie, in local storage (localStorage) or in session storage (sessionStorage):

  • rv_id (cookie for .regyva.com, 400 days): a random identifier by which we recognise your browser on later visits.
  • rv_forced (cookie for .regyva.com, 400 days): records that rv_id was set without you choosing marketing in the banner.
  • _rv_session (session storage): the identifier of your current visit. Deleted when you close the tab.
  • _rv_attr_first and _rv_attr_last (local storage): remember the first and the last link with campaign parameters or click identifiers through which you arrived, with address and time. Created only if the link contains such information. Kept until you delete them.
  • _rv_queue (local storage): holds events that could not yet be sent.
  • regyva_consent_v1 (local storage): remembers your choice in the cookie banner. Kept until you delete it.

The pixel sends events to our server: page views, clicks, how far you scroll, how long you stay, leaving the page, starting, pausing and ending videos, as well as selecting form fields and submitting forms. Each event includes the identifiers from rv_id and _rv_session, your choice in the banner, the address and title of the page, the previously visited page, and campaign parameters (utm_source, utm_medium, utm_campaign, utm_content, utm_term, utm_id) and click identifiers from the link, including gclid and fbclid. As with every request, your IP address and your browser's information about browser and operating system also reach our server.

If the pixel detects that you submit a form with an email address or phone number, it also transmits this information together with the identifiers, so that we can attribute the enquiry to its origin. It sends answers from other form fields only for fields that are released for this, and only if you chose marketing in the banner. No field is currently released on this website.

The data goes to our own server at Hetzner Online GmbH in Germany (section 3).

On your first visit, the page shows a cookie banner with "Accept all", "Necessary only" and "Customise". Under "Customise", you choose statistics and marketing individually. Your choice is stored in regyva_consent_v1, reported to our server and sent with every event. For this website, the pixel is currently configured to set the entries listed above and send events regardless of your choice. Your choice changes the following: if you choose "Accept all" or marketing, rv_forced is deleted. If you choose anything else, rv_id and rv_forced remain.

In addition, the website itself stores these entries in your browser:

  • NEXT_LOCALE (cookie): remembers the language if it differs from your browser's language setting. Deleted when you close the browser.
  • regyva-theme (local storage): remembers whether you chose the light or dark display. Kept until you delete it.
  • regyva-spinner-shown (session storage): makes sure the loading animation appears only once per session. Deleted when you close the tab.
  • regyva:warteliste (local storage): remembers after a waiting list sign-up that you are signed up. Kept until you delete it.
  • vega-pegel (local storage): remembers the volume of the sounds in the demo request chat. Kept until you delete it.
  • vega (session storage): keeps the ongoing demo request conversation so that it continues after the page is reloaded: the conversation identifier, the step reached and the summary of your case, without your name and without your email address. Deleted when you close the tab.

The entries in this second list are technically necessary for the functions you use (Section 25(2) No. 2 TDDDG, German Telecommunications Digital Services Data Protection Act). Except for vega, they contain no information about you. vega contains the information about your case from the ongoing conversation, but neither your name nor your email address.

9. Connected accounts in the Regyva app (TikTok, Instagram, YouTube, Google Ads, Claude)

In the Regyva app at app.regyva.com, you can connect your own TikTok, Instagram or YouTube account to Regyva to see how your posts perform, and your Google Ads account to attribute your ad spend to your leads and sales. Only you start the connection, by signing in with the respective provider. There you see beforehand which permissions Regyva receives, and you consent.

From TikTok, with your consent, we read via the TikTok Login Kit:

  • Profile (permission user.info.basic): your TikTok identifier for Regyva, your display name and your profile picture, so that we can recognise and display the connected account.
  • Account statistics (permission user.info.stats): number of followers, accounts followed, likes and videos.
  • Videos (permission video.list): your public videos with title, description, thumbnail, link, duration, publication date as well as views, likes, comments and shares.

From Instagram, we read your account's profile, posts, their metrics, as well as comments and messages.

From YouTube, with your consent, we read via the YouTube API Services:

  • Channel and videos (permission youtube.force-ssl): name, identifier, profile picture and metrics of your channel, your uploaded videos with title, description, thumbnail, duration, publication date, visibility, views, likes and comment count, as well as the comments on your videos with their replies.
  • Analytics (permission yt-analytics.readonly): watch time as well as subscribers gained and lost per day, views, watch time and average view duration per video.

Regyva uses the youtube.force-ssl permission for writing for one thing only: if you change the description of one of your videos in Regyva, for example to swap a link, we write exactly this description back to YouTube when you click. Other details of the video remain unchanged.

By connecting YouTube, Regyva uses the YouTube API Services. The YouTube Terms of Service (https://www.youtube.com/t/terms) and the Google Privacy Policy (https://policies.google.com/privacy) apply.

From Google Ads, with your consent (permission adwords), we read the ad accounts you have access to, their campaigns, ad groups, ads and conversion actions, as well as per day cost, impressions, clicks, video views, conversions and their value. Regyva does not change anything in your Google Ads account.

With the datamanager permission, Regyva reports events from your sales back to your Google Ads account so that Google can optimise your ads for leads and purchases: new lead, booked or completed appointment, qualified lead and purchase, each to the conversion action you selected for it in Regyva. What is sent is Google's click identifier (gclid, gbraid or wbraid), the time, and value and currency. If the person consented to marketing on your page, their email address and phone number are added, only as a SHA-256 hash, a checksum from which the information cannot be recovered. Without this consent and without a click identifier, nothing goes to Google.

We use this data only to show it to you and your team in Regyva as an overview and analysis, and for Google Ads for reporting back to your own ad account. Apart from the video description mentioned above, Regyva does not publish, change or delete anything in your connected accounts. We do not sell the data, do not pass it on to third parties and do not use it for our own advertising. The data is stored on our server at Hetzner in Germany. The provider's access token is stored encrypted.

For data we receive via Google APIs (YouTube and Google Ads): "Regyva's use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements."

The legal basis is Art. 6(1)(b) GDPR, the connection is part of the service you use. If you disconnect an account in Regyva (TikTok, Instagram and YouTube under Organic, Channels, Google Ads under Paid Ads, Setup), Regyva no longer retrieves any data. You can also revoke access at any time in the settings of your TikTok or Instagram account, for YouTube and Google Ads at https://security.google.com/settings/security/permissions. We delete data already retrieved together with your Regyva account, or earlier on request to info@regyva.com.

If you own a team or use an agency account, you can also connect your own Claude account from Anthropic to Regyva. Only you start the connection, in Claude. In Regyva you see beforehand which data Claude receives, and you consent. After that, Claude only reads, and only when you ask Claude to: metrics of your team or of the coaches your agency manages (such as leads, appointments, deals, revenue, ad spend and commissions), leads with name, email address, phone number, creation date, source, channel, status, stage and deal value, figures per setter and closer with their names and, on your request, all other data you see in Regyva, without personal details of partners and team members such as their email address. On your instruction, this data goes to the Claude account you connected, and thus to Anthropic, PBC, 548 Market St, PMB 90375, San Francisco, CA 94104, USA. Anthropic does not process it on our behalf, your own contract with Anthropic applies. You can disconnect at any time in Regyva under Settings, Security, after which Claude receives no further data.

10. Your rights

You have the right of access (Art. 15 GDPR), rectification (Art. 16 GDPR), erasure (Art. 17 GDPR), restriction of processing (Art. 18 GDPR) and data portability (Art. 20 GDPR). To exercise them, write to info@regyva.com.

Where we process data on the basis of Art. 6(1)(f) GDPR, you can object at any time on grounds relating to your particular situation (Art. 21 GDPR).

You can also lodge a complaint with a data protection supervisory authority, in particular in the EU member state where you live or work (Art. 77 GDPR).

11. Obligation to provide data

You are not obliged to give us any data. Without name and email address, however, we cannot handle a demo request.

12. Changes

We update this policy when the website or the legal situation changes. The version published here applies.