privacy policy

Protecting your personal data matters to us. This notice explains what data we process on everdigital.ch and for what purpose, on what legal basis, and what rights you have. Processing is governed by the revised Swiss Federal Act on Data Protection (FADP) and, where applicable, the EU General Data Protection Regulation (GDPR).

1. Controller

The controller within the meaning of Art. 5(j) FADP (or Art. 4(7) GDPR) is:

Heezen EverDigital (sole proprietorship)
Owner: Ralph Heezen
Alte Strasse 28
5734 Reinach AG, Switzerland
Email: info@everdigital.ch
Phone: +41 79 170 80 49

2. Privacy contact

For questions about privacy, including access, correction or deletion, please contact:

Ralph Heezen
info@everdigital.ch

We are not required to appoint a data protection officer under Art. 10 FADP and Art. 37 GDPR; enquiries are handled directly by the owner.

3. Principles

We process personal data according to these principles:

• Lawfulness and good faith: only on a legal basis or with consent.
• Purpose limitation: processing only for the purpose stated when the data was collected.
• Data minimisation: as little data as possible and as much as needed for the purpose.
• Transparency: you can understand what we process and why.
• Security: appropriate technical and organisational measures (TLS, access controls, current software and hardened server configuration).

4. Data we process

4.1 Website visits

When you visit everdigital.ch, our hosting provider automatically records the following in server logs:

• IP address of the requesting device
• Date and time of access
• Requested URL and HTTP status code
• Amount of data transferred
• Referrer URL (if provided)
• User agent (browser, operating system)

Purpose: Providing the website, stability, and detecting and preventing attacks.
Legal basis: Legitimate interest in securely operating the website (Art. 31(1) FADP / Art. 6(1)(f) GDPR).
Retention: A maximum of 7 days, followed by automatic deletion. These records are not combined with other data sources.

4.2 Contact form

If you use our contact form, we process:

• First and last name (required)
• Email address (required)
• Company, area of interest and message (optional)

The message is sent over an encrypted SMTP connection to our business mailbox (Infomaniak, Switzerland). Its contents are stored there as business correspondence.

Each enquiry also receives a random lead reference and is stored encrypted in our access-restricted PostgreSQL database on the application server (Hetzner, Germany). Our internal system records processing status, timestamps and any order values; plain-text contact data is visible only in the authenticated administration area.

Purpose: Responding to your enquiry, contacting you and potentially initiating a contract.
Legal basis: Pre-contractual measures or legitimate interest in communication (Art. 31(1) FADP / Art. 6(1)(b) and (f) GDPR).
Retention: Until your enquiry is completed; if a business relationship is established, 10 years under Art. 958f of the Swiss Code of Obligations (CO). You may request earlier deletion at any time unless a retention obligation applies.

4.3 Challenge widget

Using the widget "Your challenge" you can describe a specific problem. We process your name, email address and submitted text. The purpose, legal basis and retention follow section 4.2.

4.4 Whitepaper requests

On the page /architektur you can download a three-page technical whitepaper as a PDF. To provide it and respond to questions, we collect:

• Email address (required)
• Company (optional)
• Whitepaper slug and request source (e.g. ‘architektur-page’)
• Anonymised IP hash (daily rotating salt, no plain text)
• User agent to filter bot requests
• Consent and request timestamps

Purpose: Providing the whitepaper (immediate PDF download) and one sales follow-up to establish whether a 30-day pilot would be relevant for you.
Legal basis: Your explicit consent via checkbox (Art. 6(1)(a) GDPR or Art. 6(6) FADP), plus legitimate interest in B2B contact (Art. 6(1)(f) GDPR or Art. 31(1) FADP).
Retention: 36 months from your request. You may request deletion at any time at info@everdigital.ch.
Storage location: Local database (SQLite) on our application server in Germany (EU). The data does not leave this server and is not sent to third-party services.

4.5 Cookies and local storage

We do not use tracking cookies without your consent. Necessary preferences (e.g. light/dark mode) are stored locally in your browser. Your cookie choices are also recorded in a signed, necessary first-party cookie and our consent log. Consent for analytics or marketing cookies is requested through a banner.

Details and a complete list of the technologies used are available in our Cookie policy.

4.6 Consent log

To document granted or withdrawn cookie consent, we store on our server: a random consent ID, timestamp, your choices, the policy version, an anonymised IP hash (daily rotating salt) and the user agent. No names, email addresses or plain-text IP addresses are stored.

Legal basis: Accountability under Art. 7(1) GDPR or Art. 6(6) FADP.
Retention: 3 years.

4.7 Demo login

Access to live demos (/demo-modules) is reserved for approved pilot customers. We use Clerk for one-time-code login and session management. It processes your email address, an authentication token and technical session cookies. These cookies are essential for login and therefore do not require cookie consent.

Legal basis: Initiating or fulfilling a contract (Art. 31(2)(a) FADP, Art. 6(1)(b) GDPR), and our legitimate interest in protecting access.
Provider: Clerk, Inc., USA (see sections 5 and 6).

4.8 Web analytics (Google Analytics 4, server side)

With your consent, we measure website use with Google Analytics 4. Analytics events pass through our own server: your browser sends events (e.g. page views) to an endpoint on our domain, and our server forwards them to Google Analytics in pseudonymised form. Google Tag Manager loads only after analytics or marketing consent and manages these events, but does not send free-text form fields to GA4. The IP address of the request to our analytics endpoint is not forwarded to Google Analytics. The Google tag also uses _ga and _ga_* cookies (up to 13 months) and ed_ga_sid (30 minutes) to identify visitors and sessions. Your browser stores a random identifier for recognition (ed_cid, 13 months). Names, email addresses or other plain-text identifiers are not sent.

Legal basis: Consent (Art. 6(6) FADP, Art. 6(1)(a) GDPR). You may withdraw consent at any time via cookie settings; the identifier is then deleted immediately.
Provider: Google Ireland Ltd., Ireland (see section 5).

4.9 Google Ads attribution and qualified leads

If you consent to the ‘Marketing’ category and reach our site via an advertisement, we store Google click identifiers (GCLID, GBRAID or WBRAID), campaign parameters, landing page, referrer, timestamp and technical session information in an encrypted first-party cookie. On form submission, these data are linked in encrypted form to your lead reference in our PostgreSQL database.

After a lead form is successfully submitted, the user-provided-data tag in Google Tag Manager sends only an email address normalised in the browser and hashed with SHA-256. Raw email addresses, names, messages or company details are not written to the dataLayer. Only when we internally mark the enquiry as qualified or as a won order does our server also send status, timestamp, any order value and consented click identifiers to Google Ads. Refused, withdrawn or absent marketing consent blocks this transfer. With marketing consent, Google click identifiers are also sent to Google Analytics to attribute confirmed form leads to Google Ads. Without marketing consent, our analytics endpoint removes these identifiers.

Purpose: Connecting advertising spend to actual qualified enquiries and orders, and optimising campaigns for business outcomes rather than form submissions alone.
Legal basis: Your consent (Art. 6(6) FADP, Art. 6(1)(a) GDPR). You can withdraw it at any time via cookie settings with effect for the future.
Provider: Google Ireland Ltd., Ireland / Google LLC, USA (see sections 5 and 6).

4.10 ChatGPT Ads pixel and conversion measurement

If you consent to ‘Marketing’, we load the OpenAI Ads Pixel. It stores a pseudonymous click reference attached to the destination URL by ChatGPT Ads (oppref) in a first-party cookie and may process page and browser information for advertising measurement. Without marketing consent the pixel does not load; on withdrawal, consent is revoked in the SDK and the click reference is deleted.

Following a server-confirmed contact, challenge or prototype request, browser and server report the standard event lead_created. Both use the same pseudonymous lead ID for deduplication. The server sends event ID, timestamp, page path, action source and event type, plus the pseudonymous click reference if available. Email addresses, and first and last names when collected separately, are sent only after normalisation and SHA-256 hashing; free-text form contents are not transferred. Automatic Advanced Matching may also recognise, normalise and hash supported contact data in the browser.

Purpose: Connecting ChatGPT advertising spend to confirmed enquiries and optimising campaigns for leads.
Legal basis: Your consent (Art. 6(6) FADP, Art. 6(1)(a) GDPR). You can withdraw it at any time via cookie settings with effect for the future.
Provider: OpenAI, L.L.C., USA (see sections 5 and 6).

4.11 ‘The 10-day prototype’ applications

Via the page /prototyp companies can apply for a free software prototype. We process the following details (all required):

• Company, website and business identification number (UID)
• Systems in use, process description, process volume and desired timeframe
• Contact person’s name and business email address

The details are sent over encrypted SMTP to our business mailbox (Infomaniak, Switzerland) and are also stored in an access-restricted log on our server (Hetzner, Germany) so applications are not lost. We use Cloudflare Turnstile to protect against automated abuse (see section 4.7 on the same technology for demo login).

If an applicant subsequently sends sample documents, these may contain third-party personal data (e.g. customer names in order PDFs). We process these documents on the applicant’s behalf: our Privacy Gateway tokenises personal data before an AI model (Anthropic Claude or Google Gemini) processes them. Details are covered by our Confidentiality and data processing agreement (PDF).

Purpose: Reviewing the application, building and demonstrating the prototype, and potentially initiating a contract.
Legal basis: Pre-contractual measures or legitimate interest (Art. 31(1) FADP / Art. 6(1)(b) and (f) GDPR).
Retention: We delete sample documents immediately on request, or no later than 30 days after the demo appointment if no order follows. Application details are handled as business correspondence under section 4.2.

5. Recipients / processors

We disclose personal data only to carefully selected processors with contractual commitments under Art. 9 FADP (or Art. 28 GDPR):

Where AI models are used in demo modules or MCP/copilot integrations, this is based on the providers’ data processing agreements (DPAs), with training excluded in business/API plans: Anthropic DPA, Google DPA (Gemini) und OpenAI DPA. In tokenised mode these providers receive no plain-text personal data, only placeholders (e.g. ‘Customer_8f31’).

We currently use no other third-party services. If further processors are added, we will update this list and the ‘Last updated’ date.

6. International data transfers

Hetzner operates data centres in Germany. Under Annex 1 of the Swiss Data Protection Ordinance (DPO), the EU is recognised as providing adequate data protection; transfers there are permitted without additional safeguards (Art. 16(1) FADP).

Infomaniak processes data in Switzerland. No transfers to third countries take place.

For consented Google Ads attribution, data is sent to Google Ireland Ltd.; further processing by Google LLC in the USA may take place within Google’s infrastructure. Google relies on applicable transfer mechanisms and contractual safeguards.

Clerk, Inc. processes demo customers’ login data (section 4.7) in the USA. This third-country transfer is also based on Standard Contractual Clauses (SCCs) under Decision (EU) 2021/914 together with the provider’s supplementary safeguards. It concerns only approved pilot customers who actively register for demo access.

If US-based AI providers (e.g. Anthropic PBC, Google LLC, OpenAI) are used in demo modules, MCP/copilot integrations or prototype development (section 4.11), transfers also rely on SCCs under their DPAs. In tokenised mode, only placeholders are transferred, with no plain-text personal data.

7. Your rights

You have the following rights regarding your personal data:

• Access (Art. 25 FADP / Art. 15 GDPR): whether and which data we process about you. The first access request within 12 months is free of charge.
• Rectification of incorrect data (Art. 32(1) FADP / Art. 16 GDPR).
• Erasure oder Destruction (Art. 32(2)(c) FADP / Art. 17 GDPR), unless a retention obligation applies.
• Restriction of processing (Art. 18 GDPR).
• Objection to processing based on legitimate interest (Art. 30(2)(b) FADP / Art. 21 GDPR).
• Data delivery / portability (Art. 28 FADP / Art. 20 GDPR): provision in a commonly used electronic format.
• Withdrawal of consent with future effect, without giving reasons.

Exercising these rights is generally free. We may request proof of identity to avoid disclosing personal data to unauthorised persons.

8. Right to complain

If you believe we process your personal data unlawfully, you may complain to:

Federal Data Protection and Information Commissioner (FDPIC)
Feldeggweg 1, 3003 Bern, Switzerland
www.edoeb.admin.ch

If you reside in the EEA, you may also contact the supervisory authority in your member state.

9. Data security

We operate the website exclusively over encrypted connections (TLS). Servers and applications are updated regularly, and access is restricted to the owner. External interfaces (form API, consent log) are rate-limited and validate all inputs. Absolute security of internet data transfers cannot be guaranteed.

10. Automated individual decisions

We do not make automated individual decisions with legal effects or significant adverse consequences (Art. 21 FADP / Art. 22 GDPR).

11. Changes to this notice

We update this notice when legal requirements or our processing activities change. The version currently published here applies. The ‘Last updated’ date indicates the most recent revision.