Who is responsible?
Nora is a project operated personally from Switzerland by Addrielle Arismendy Mendez Gonzalez, responsible for the website and Demo. The service currently targets Swiss garages only. No company has been incorporated. “Nora” and “The Nora Team” are project names.
For commercial enquiries and privacy, access, correction or deletion requests, contact norateam.2026@gmail.com. Both use this Gmail address. Addrielle personally handles privacy requests; there is no separate privacy department.
Addrielle is the controller for Nora’s website, commercial and privacy enquiries, public Demo and tests, account administration and platform security, and Nora’s own service-quality reviews. These are Nora’s purposes, distinct from a garage’s workshop work.
For a real garage conversation, the garage identified in the chat controls the handling of its customer relationship, workshop follow-up and appointment decisions. Nora processes reception records on that garage’s behalf when carrying out its instructions; this processor role does not cover Nora’s separate purposes above. A technical support feature does not itself establish a processing agreement or authorize every use. Contact the garage about its workshop records, or the privacy email above for help identifying responsibilities. Do not send privacy requests to the fictitious garage chat.
Information processed and why
- Website and commercial enquiries: technical connection data handled by the hosting service; your email address, message and any business details you choose to send when contacting the team.
- Customer conversations: messages, language, supplied name, phone or email, vehicle details and optional registration, service or problem description, scheduling preferences, selected times and request history. These support replies, workshop follow-up and appointment requests or changes.
- Garage accounts: login email, password hash, roles, memberships, invitations, sessions, configuration and relevant audit records for authorized access and administration.
- Operations: timestamps, request state, booking history, channel/source labels, delivery state and security diagnostics for continuity, reliability and activity reporting. Contact groups in reports are not verified identities.
Only share information needed for the garage request. Do not send passwords, payment-card details, identity documents or sensitive personal information. The Demo represents a fictitious garage: use invented details. Anything actually entered in the Demo may still be processed and stored; “Demo” does not mean anonymous or automatically erased.
AI, people and appointment decisions
The application sends conversation messages and garage context to the configured OpenAI API for language interpretation. Messages can include personal details you supplied. Application rules, not model text alone, control availability, authorization and booking transitions. A submitted or locally reserved request is not necessarily workshop acceptance.
Authorized garage staff can read their garage’s requests. Authorized Nora administrators can access garage conversations through a read-only, audited support process for support and quality review. You can request human follow-up; Nora is not an emergency service.
Providers and data locations
The operator has confirmed Germany, Render’s Frankfurt (EU Central) region, for both Nora Demo and Pilot. This has not been independently checked in the service accounts and does not establish locations for backups or other providers.
Local development and test databases are also kept on the operator’s computer, including real contact identifiers in restricted WhatsApp tests. An older local database has not yet been classified and is treated as potentially personal data. The absence of other device or cloud copies has not been verified.
The following identifies providers and relevant countries, separating published safeguards from account-specific verification. It is not a guarantee that every listed country receives every conversation.
- Render — application/database hosting: Germany as confirmed above; its US-based service also handles account and operational information. Render publishes a data-processing addendum with Swiss transfer provisions and Swiss–US Data Privacy Framework certification.
- Cloudflare — website delivery and the temporary WhatsApp test tunnel: distributed processing, including the United States; no country restriction for these Nora services has been verified. Its standard DPA provides Swiss-adapted standard contractual clauses; its transfer policy also describes Swiss–US Framework coverage.
- OpenAI — message interpretation: the global API supplier list includes the United States, Ireland, United Kingdom and other named countries in the API processing-location list. Nora’s individual request destinations are not verified. The standard DPA identifies OpenAI Ireland for Swiss customers and provides contractual clauses or adequacy-based transfers where applicable.
- Google Gmail — commercial enquiries and privacy requests: both use norateam.2026@gmail.com. This includes processing in the United States, without a verified mailbox residency restriction. Google’s transfer framework describes Swiss–US Framework coverage and contractual clauses. Nora has not verified a Google Workspace processing agreement for this Gmail address.
- WhatsApp/Meta — restricted message tests: relevant entities are in Ireland and the United States. The Business transfer addendum addresses onward transfers; WhatsApp’s Swiss–US Framework disclosure covers qualifying Business Services transfers. Its processor terms apply only to the processing they specify, not every Meta purpose.
Apple — optional Operator notifications: the operator’s check found Apple push subscriptions registered in both Demo and Pilot. Registration does not establish that notifications remain enabled or were delivered. Apple’s privacy policy identifies an Irish controller for Swiss individuals, general US storage and standard contractual clauses for international transfers. This does not verify a particular notification’s route or a separate Nora–Apple agreement.
The operator confirms standard signup for Render, Cloudflare, OpenAI API and Meta’s WhatsApp Cloud API, without negotiated special contracts; WhatsApp testing uses Meta directly, without an intermediary. The linked standard terms are the relevant references, not proof of a separately signed Nora agreement or special regional guarantees. Some processing and backup locations remain unverified. No Swiss-only or Europe-only processing guarantee is made. Deleting Nora records does not automatically delete provider records or recipients’ copies.
OpenAI receives the messages and context sent for interpretation. Nora’s OpenAI project uses the default/global configuration: no specific data-residency region has been configured or contracted. Processing is not guaranteed to take place exclusively in Europe. This is separate from Nora’s Render hosting in Frankfurt.
OpenAI’s published API policy distinguishes stored response data from abuse-monitoring logs and permits different account-level controls. The absence of a selected residency region does not establish a particular retention period or training setting. Nora does not promise that all provider copies disappear immediately or that special retention controls apply to its account. See OpenAI’s API data controls.
WhatsApp — planned, restricted testing
WhatsApp is being tested and is not generally activated. When enabled for a garage, Meta supplies the sender’s WhatsApp number, message identifiers, timestamps, supported message content and delivery events. Nora associates these with the routed garage and conversation, stores receipts for retry/deduplication, and uses the same conversation and availability rules as web chat.
The planned staff workflow shares actionable requests with an authenticated, authorized workshop staff member in their private WhatsApp chat. Staff can respond or take over. Explicit workshop acceptance, not merely acknowledgement, can trigger a customer confirmation. Copies delivered through WhatsApp are also handled in Meta’s services and recipients’ devices under their applicable terms and settings.
The current isolated webhook test receiver verifies signatures and restricts routing and test recipients. It can store accepted test receipts but does not send replies, invoke the model or notify a workshop. Other authorized Demo/web sessions are separate and may use the model.
Browser storage and activity measurement
The website remembers the selected language in local storage. Nora account access uses session cookies; application language preferences may also be saved locally. Private conversation or appointment access uses protected capabilities. Keep private appointment links and keys private.
The website loads the widget script from Nora’s Demo domain. Opening it loads the embedded chat and makes further requests to that service. Nora records business-scoped direct-link, QR or widget source information where supported and derives activity reports from stored requests. The website source does not include an advertising pixel or fingerprinting script. Hosting and security services can still handle technical connection data.
Retention, deletion and your choices
Conversation and appointment history is stored; cancelling an appointment does not erase its history. Nora’s separate operational backups are not currently deleted automatically, and no fixed deletion deadline is currently applied to those copies. Provider records and messages on recipient devices are handled separately.
Render disk snapshots: the operator checked both Demo and Pilot dashboards, which show daily snapshots available for seven days after capture. This is the displayed recovery-availability period, not a guarantee that every provider copy is deleted after seven days. Snapshot storage location has not been verified. These snapshots are separate from Nora’s operational backups described above.
There is currently no fixed automatic deletion period for Nora conversation history or WhatsApp test receipts. Records remain stored until a specific removal or anonymisation is carried out. Session or access-key expiry does not delete the associated conversation. When assessing a request, Addrielle considers the records concerned, ongoing workshop work, security, applicable obligations and technical dependencies; retention is not treated as permission to keep unnecessary data indefinitely.
To request deletion, email the privacy contact with the service or garage involved and an approximate date. Do not send passwords, access keys or unnecessary identity documents. Addrielle may ask for proportionate verification and will explain what can be removed, what needs further work, and any reason a record must be retained. Nora currently has no self-service, all-systems deletion button.
Deletion from active records and removal from backups or providers are separate operations. Copies may remain in backups pending their controlled removal or expiry, and on recipients’ devices or in provider systems. No immediate or universal deletion is promised. If a backup is restored, completed deletion requests must be considered before restored data is returned to normal use.
Depending on applicable law, you may request access, correction or deletion, object to processing or withdraw consent where consent is the basis. Applicable obligations can limit deletion. You may also contact the competent data-protection authority, including the Swiss Federal Data Protection and Information Commissioner where Swiss law applies.