PERSONAL DATA · SWISS FADP
Privacy notice
This page describes processing actually observed in the website code and infrastructure. It separates verified technical facts from contractual or identity information that still requires confirmation.
Introduce your need, then receive a human response.
The six onboarding forms collect your contact details, professional context and information relevant to your selected path, with your permission to process the request and contact you. Data is stored in D1 and the internal CRM queue, with a reference, notice version and consent date. No selection score is assigned; the decision and response remain human.
Onboarding supplement · . The information does not automatically subscribe you to a newsletter or publish your profile. Do not submit identity documents, trade secrets, sensitive data or third-party personal data that is unnecessary for your request.
- Sale or rental
- None
- Public audience analytics
- Disabled
- Final decision
- Always human
- External CRM
- None
- Book a call
- Enabled · human review
- Onboarding · six paths
- Open · human review
An inventory grounded in shipped code.
| Activity | Data | Purpose | Access / outcome |
|---|---|---|---|
| Book a call | Name, email, optional organisation, path, message, permission and limited attribution. | Review the request and propose a conversation. | D1 database, internal CRM queue and administrator in-app notification. |
| Onboarding · six paths | Name, email, organisation according to the path, path, professional context and form-specific answers; dated and versioned permission, reference, offer context and limited attribution. | Understand the project, need or contribution, prepare human review and contact the person about their request. | D1 and internal CRM, authorised administrator access and internal notification. Unscored request, with no automatic external email. |
| Legacy partner expression | Separate historical schema: organisation, contact, country, contribution, capacity, references, vision and permissions. | Qualify a potential collaboration under the legacy partner workflow. | Legacy form inactive: disabled interface and fail-closed API (503). The new Partner path is separate. |
| Member workspace | Authentication identity, profile, requests, evidence, permissions and logs according to features used. | Provide the private workspace, control access and trace decisions. | Access limited to the relevant member and authorised roles. |
| Abuse protection | SHA-256 fingerprint derived from the network address or request signals, tied to a 15-minute window. | Rate-limit automated submissions and protect forms. | The raw address is not stored in the application counter. |
Information requested for each path
- Startup. Project, problem and target audience, stage, support sought, early evidence, public link, team, timing and constraints.
- AURA. Professional role, team, AI use, process to improve, desired outcome, tools, data constraints, decision responsibility and resources.
- Community. Profile, city or region, interests, motivation, possible contribution, preferred format and availability.
- Experts. Expertise, experience, achievements, public profile, formats, languages, availability, working terms and possible conflicts.
- Partners. Organisation type, territory, official website, mandate, areas and contribution, references, mobilisation, value sought, constraints, consortium and communication preference without publication permission.
- Hub. Contribution, territory, proposal, general characteristics of any possible site, references, mandate, timing and desired outcome.
Each form identifies required fields. Answers remain within the internal review process; a professional link is supplied by you and does not authorise access to a private account.
A first-party application with no active marketing pixel.
The shipped public application code writes no application cookie, localStorage or sessionStorage on public pages. The audience-measurement module is not mounted and its endpoint is disabled: public page views and clicks are not stored for that purpose.
- __cf_bm
- Security cookie that may be set by Cloudflare infrastructure to detect automated traffic; observed duration is about 30 minutes. It is not an Agartha analytics cookie.
- Edge logs
- May include technical request and network-address data. Provider, countries and retention still require approval in the processor register.
Member authentication is delegated to the platform and may rely on necessary session mechanisms. The application uses Cloudflare infrastructure, D1 for structured data and R2 for objects. Technical logs may include request and IP-address data. Active public forms are described above. The complete processor, country, transfer and retention register still needs completion and approval; these details are not presented as verified.
The LinkedIn footer link is outbound, not an embed. No external email is automatically sent when a form is submitted: follow-up appears in the administration interface.
Retention remains governed, not claimed to be automatic.
The product includes a versioned retention-policy register and a data-rights request centre. No general automatic deletion is claimed. A quantified period for each purpose must be approved and released before this section is complete.
Observed safeguards include origin checks, bounded submission sizes, allow-listed fields, a honeypot, rate limits, role checks and immutable logs for sensitive decisions. A fingerprint of normalised answers prevents duplicate records when the same request is repeated within a short window; that window does not define the record’s retention period. No system guarantees absolute security.
Access, correction, restriction, portability or deletion — with human verification.
You may request access to, correction or deletion of your data, object to certain processing and, where statutory conditions are met, request delivery or transfer. Some requests may be restricted by retention duties, security, third-party rights or overriding interests.
A data-related request can be initiated through the brand email address or private centre. No deletion, export or identity verification is decided automatically.
For an onboarding request, email arnaudeste@icloud.com and include your reference if available. Specify the information to correct, your data-related request or that you no longer wish to be contacted. Do not send identity documents without a justified request as part of human verification.
Primary sources used to frame this page.
These links document the general framework. They do not replace identification of the actual operator or legal review applied to Agartha’s situation.