This Privacy Policy explains how Risphai ("we", "us", or "our") collects, uses, stores, shares, and protects your personal data when you use our AI assistant service available at risphai.com (the "Service").

Dluvan Ali, based in Switzerland and operating the Service under the name Risphai, is the data controller responsible for the processing described in this policy. Risphai is the service name, not a separate legal entity. We are responsible for protecting personal data and meeting applicable data protection obligations. Rahand Ali is the creator and developer of the app.

By creating an account or using the Service, you acknowledge that you have read and understood this Privacy Policy. Acknowledging this policy is not consent to every processing activity. Where consent is required, it must be obtained separately.

Scope: This policy describes our data practices for the website and mobile apps. Privacy settings have specific limits explained below. It does not waive our responsibilities or your rights under applicable data protection law.

Account Data

When you create an account, we collect:

• Email address
• Password submitted for authentication; our authentication service stores a password hash. Passwords are not retained in account profile data or signup drafts.
• Email verification status
• Account creation date and last sign-in date
• If you sign in with Google or Apple: your email address and basic profile information provided by the authentication provider

Profile Data (Optional)

You may optionally provide the following information. All profile fields can be skipped during onboarding and are not required to use the Service:

• Name
• Gender
• Pronouns
• Age
• Custom instructions for personalization where enabled and outside incognito mode
• Default privacy mode tier for text-based AI (no training on data or zero data retention), when you save it as your default during onboarding or in chat; stored in your user profile in our database (Supabase)
• Whether the Memories feature is enabled ("Use memories in AI replies" in Account settings); stored in your user profile

Memory Data (Optional)

When you use the Memories feature, we store:

• Individual memory entries you create or that the assistant saves from facts you state during chat while memories are enabled, within the per-entry length limit shown in the product
• Sort order of memories in your list

When memories are enabled, the assistant may save facts you state without a separate approval for each entry. We may include saved entries as context with later AI requests. Review, correct, or delete them in Account settings and avoid submitting unnecessary sensitive information. Disabling memories stops their use in new requests; saved entries remain until you delete them or delete your account.

We instruct the assistant to save only ordinary facts and preferences you state and to exclude sensitive information, including health information, racial or ethnic origin, political or religious beliefs, trade-union membership, genetic or biometric identification data, sexual life or orientation, criminal-offence information, and secrets. These instructions also apply when you ask the assistant to remember an excluded detail. This safeguard relies on the assistant following its instructions and can make mistakes; it is not a guarantee that sensitive information cannot be saved. Do not enter sensitive details through manual memory edits or restores, and remove any such entry you find. The policy does not automatically remove existing memories or prevent sensitive information from being processed in ordinary chats.

Conversation Data

When you use the Service, we store:

• Your messages and AI assistant responses
• Conversation titles and metadata (timestamps, message counts)
• Web search results, image search results, and YouTube video results generated during your conversations
• Usage and task details needed to display results, track credit consumption, and operate the Service
• Related follow-up questions suggested by the AI

Prompt Data

When you create custom prompt templates, we store:

• Prompt labels (display names)
• Prompt text content
• Sort order (for custom ordering)
• Timestamps (creation and last update)

Project Data

When you create and use projects, we store:

• Project names and descriptions
• Uploaded project files: images, documents, and text notes
• File metadata (original filename, file size, MIME type, file type)
• Project-conversation associations (which conversations are linked to which projects)

Scheduled Task Data

When you create scheduled tasks, we store:

• Task prompts and titles
• Schedule configuration (type: daily/weekly/monthly, time, day of week/month, timezone)
• Task status (active or paused)
• Execution history (last run time, next scheduled run time)
• Linked conversation IDs from task executions
• Task options (web search mode, model overrides, response length)

Generated Content

When the AI generates media or files on your behalf, we store:

• Generated images, videos, audio files, documents, spreadsheets, archives, and other code-created files
• The prompts used to generate them (including any rewritten prompts)
• File metadata (dimensions, duration, storage paths, MIME types)

Uploaded Content

When you upload files in conversations or within projects, we store:

• Uploaded image files
• Uploaded documents (PDF, Word, text files, and other supported formats)
• Text notes created within projects
• Original filename, file size, and MIME type

Payment Data

When you subscribe or purchase credits, we store:

• Stripe customer ID and subscription ID when you pay on the web
• Subscription plan type, status, billing cycle, and which platform the subscription is billed through (web via Stripe, iOS via App Store, or Android via Google Play)
• Identifiers used to link your account to RevenueCat and store purchase information for native apps
• Payment transaction records (amounts, credits added, discounts applied where applicable)
• Credits balance

We do not store your credit card number, CVV, or full billing address on Risphai servers. Web card payments are processed by Stripe. In-app subscription payments on iOS and Android are processed by Apple or Google respectively; RevenueCat validates receipts and synchronizes entitlement data with our backend.

For web purchases using Stripe Managed Payments, Stripe and its affiliate Sold through Link, LLC process payment, billing and order information for payment collection, tax handling, fraud prevention, receipts, subscription management and transaction support. Relevant order and subscription information is shared with Risphai to provide access, update credits and handle support. Stripe and Link also process information for their own payment, security and legal purposes under the applicable Stripe privacy notice and Link privacy notice.

Usage Data

• Credits consumed per AI request and tool run
• AI model configurations selected
• Response durations and error occurrences
• Limited operational failure metadata, including error categories, timestamps, and request identifiers. Reporting is designed to omit request bodies and redact recognized sensitive information; diagnostic error text may incidentally contain request-related details.

Credit consumption is calculated from request processing and provider usage charges, including applicable context, output, and tool use.

Moderation and Enforcement Data

When content is blocked by moderation or a safety classifier, we may store limited metadata needed to enforce the Service rules:

• Violation type, such as unsafe, illegal, copyrighted, initial safety flag, or upload flagged
• Source of the event, timestamp, and technical metadata needed to operate the enforcement system
• Restriction status and event counts needed for abuse prevention and enforcement

If a chat message is classified as illegal, the blocked message is ordinarily not stored as conversation content, but limited safety metadata may be stored.

Technical Data

• Purchase Terms versions and times, separate service-start requests, and withdrawal and cancellation notices and confirmations needed to manage contracts and legal requests. Cancellation notices include identifying details, the requested end date and a reason only for extraordinary cancellation.
• Authentication cookies (managed by Supabase, required for login functionality)
• Local and session storage data: theme, privacy and model preferences, consent choices, temporary drafts, and limited identifiers needed to recover an active incognito request in the same browser session
• IP address (processed by Cloudflare as part of hosting)

Mobile Notifications and Diagnostics

If you enable native notifications, we process your device push token, platform, and account association to deliver notifications through Google Firebase and, on iOS, Apple's notification service. Notifications may contain a result excerpt and can be visible on your lock screen. You can disable them in app or device settings.

Native crash diagnostics are optional and disabled by default. If you enable Crash Diagnostics in Settings, Firebase Crashlytics processes installation identifiers, device and app information, crash traces, and limited diagnostic metadata to help fix app errors. Risphai's custom error reporting excludes message and prompt text. You can withdraw this choice in Settings on each device; this stops collection and deletes unsent reports from that device. Reports already sent remain subject to the retention described below.

Sensitive categories of personal data

Do not submit sensitive personal information about yourself or anyone else in messages, uploads, profile fields, custom instructions, or memories. This includes health information, racial or ethnic origin, political or religious beliefs, trade-union membership, genetic or biometric identification data, sexual life or orientation, and criminal-offence information. Do not submit passwords, API keys, payment-card or bank-account details, government identification numbers, or confidential third-party information. General questions about these topics that do not reveal personal information are allowed.

If you accidentally submit sensitive information or someone else's private information, contact support@risphai.com to request removal. Identify the affected conversation, file, or memory without sending another copy of the sensitive information. We will help remove the affected content and address provider-held copies where applicable, subject to the retention limits in Section 7.

Ordinary account creation and acceptance of the Terms are not explicit consent to sensitive-data processing. The Service is not designed for regulated or professional handling of these categories.

We use your personal data for the following purposes:

• Providing the Service: Processing your messages through AI models, generating images, videos, and audio, performing web searches, and delivering responses.
• Account Management: Creating and maintaining your account, authenticating your identity, and enabling features like multi-factor authentication.
• Personalization: Using your optional profile name and custom instructions to personalize AI responses when you are not in incognito mode. When Memories are enabled, saved memory entries may be included as additional context with AI requests.
• Custom Instructions: Applying saved instructions to supported requests outside incognito mode. Instructions are screened for suspected policy violations before saving; a save may be refused when required screening cannot complete.
• Prompt Management: Storing and serving your custom prompt templates so they are available in the / slash menu across sessions and devices.
• Memories: When "Use memories in AI replies" is enabled, allowing the assistant to save facts you state during chat and include saved entries as context with later requests. Entries are not individually approved before saving. You can review, edit, delete, or disable memories in Account settings; disabling stops their use in new requests without deleting saved entries.
• Project Organization: Allowing you to organize conversations, files, and notes into projects for structured access and persistent context for AI conversations.
• Scheduled Task Execution: Executing recurring AI tasks on your configured schedule (daily, weekly, or monthly), storing task configurations, and creating conversations with execution results.
• Payment Processing: Managing subscriptions, credit purchases, and billing records through the applicable web or mobile payment services.
• Content Safety and Enforcement: Screening messages, uploads, custom instructions, project content, and extracted document content for policy violations; blocking flagged content; storing limited enforcement metadata; and applying proportionate access restrictions for suspected violations.
• Communication: Sending email verification, password reset emails, and important service-related notifications through Resend as our transactional email provider.
• Service Improvement: Monitoring usage patterns, error rates, and sanitized server-side failure logs to improve the reliability and quality of the Service.
• Legal Compliance: Fulfilling our obligations under applicable data protection laws and responding to lawful requests from authorities.

We do not use your data for advertising or third-party marketing. Automated safety checks may block content or restrict access based on suspected violations. You may contest a restriction and request review by a person through support. We do not use your data to make credit, employment, or similar eligibility decisions.

We process your data based on the following legal grounds where applicable law recognizes them:

You may withdraw your consent at any time where consent is the legal basis. Withdrawal does not affect the lawfulness of processing carried out before the withdrawal.

We disclose data to the following recipients as needed for the features you use. Providers acting as processors handle data under our instructions and applicable processing agreements. Sign-in, payment, store, and embedded-content providers may also act as independent controllers for their own services. Their policies provide additional information and do not replace our responsibilities.

YouTube and Google Maps embeds are only loaded if you have accepted third-party embeds through our cookie consent banner. Page-reading and search services process the URLs and queries needed for your request. Risphai's bundled fonts are served locally; third-party content you enable may load its own resources.

We do not sell, rent, or trade your personal data to any third party. Data is shared with the above providers solely to operate the Service. Independent providers also process data for their own services under their privacy policies; processors remain subject to our processing arrangements. We recommend reviewing the privacy policies linked above, particularly for providers located outside the EU.

OpenRouter acts as an AI routing provider under our data processing agreement and sends requests to selected inference providers. Depending on the model, these can include OpenAI, Microsoft Azure, Google AI Studio, Google Vertex AI, Anthropic, Amazon Bedrock, xAI, InferenceNet, Morph, DeepInfra, CoreWeave, DigitalOcean, NextBit, Novita, Ionstream, Makora, Relace, Wafer, Baseten, Together, Modal, Parasail, Venice, Near AI, Phala, SiliconFlow, Reka, Sail Research, and Prime Intellect. We send an internal user identifier for request attribution and abuse isolation. OpenRouter retains request metadata, including token counts, costs, latency, and user attribution. Content logging and use of prompts or responses for OpenRouter product improvement must remain disabled in our OpenRouter account. See OpenRouter's data collection notice for its content and metadata policies.

fal processes media generation requests under our data processing agreement. MiniMax video models are only available through fal, and fal can also process supported Google, xAI and ElevenLabs image, video and sound-effect requests when the direct provider or OpenRouter is unavailable. For partner models, fal may pass the content needed for processing to the model developer, which processes it under its own terms. We send each request with fal's option not to store request and response payloads, set generated output files to expire after one hour, and request deletion of a video or audio request's remaining data and output files once the result has been saved to our storage. Generated images are returned directly instead of as stored output files. fal and its subprocessors may still process temporary, billing, usage and security data under their applicable policies.

Risphai is operated from Switzerland. The primary application database is hosted in Frankfurt, Germany (AWS eu-central-1). Other recipient locations include the United States and Germany as indicated in Section 5; hosting, delivery, authentication, support and subprocessor infrastructure may process or access data in additional countries. A provider's headquarters and a configured database region do not identify every processing location. AI routing and media providers can pass requests to model developers that process data in other countries.

Transfers to countries without adequate protection require an applicable legal mechanism. These may include standard contractual clauses with Swiss adaptations and necessary supplementary measures, or an adequacy framework for a recipient whose certification covers the transfer. A provider's privacy policy alone is not a transfer safeguard.

You may contact support@risphai.com for information about the destination countries and safeguards applicable to your data, including a copy or description of relevant safeguards, subject to lawful redactions. We remain responsible for meeting applicable transfer requirements.

We retain your data for as long as necessary to provide the Service and fulfill the purposes described in this policy:

Deleting content initiates removal from active systems. Temporary processing, backup copies, legal holds, and independently retained provider records can follow different schedules. We retain exceptions only where necessary and lawful. Removing the account association from payment records does not necessarily anonymize remaining payment identifiers.

Technical delays and errors: Software bugs, outages, failed cleanup jobs, backup recovery, or provider delays can cause data to remain longer than the normal retention periods or cleanup triggers described here, including in incognito mode or when Zero Data Retention is selected. Operational periods describe normal processing, not a guarantee that every copy is erased at an exact time; applicable statutory deadlines still apply. If we identify unintended retention, we take reasonable steps to investigate, restrict unnecessary use, and complete deletion as soon as reasonably practicable. A technical failure does not authorize indefinite retention or use for new purposes.

Account deletion initiates removal of account content and operational records from active systems. Temporary processing and backups follow their respective cleanup schedules. Required payment records remain with the account association removed; remaining transaction references may still identify a payment. The email suppression record normally expires after 30 days; permanent-ban records have no automatic expiry and remain subject to necessity review and applicable rights, as described above. You may request information about retained personal data through support.

Rights that may apply to you

Depending on where you live and what law applies, you may have rights such as:

• Request information about whether and how we process your personal data
• Request access to your personal data
• Request rectification of inaccurate or incomplete data
• Request deletion of your personal data
• Request data portability (receive your data in a structured, commonly used format)
• Object to the processing of your personal data
• Restrict the processing of your personal data
• Withdraw consent at any time where processing is based on consent
• Lodge a complaint with a data protection supervisory authority
• Receive information about applicable automated decisions, express your view, contest the decision, and request review by a person where the law provides these rights

California residents

If you are a California resident and the California Consumer Privacy Act as amended by the CPRA applies to our business, you may have rights such as:

• To know what personal information we collect, use, and disclose
• To request deletion or correction of your personal information
• To opt out of the sale or sharing of personal information (we do not sell your data)
• To non-discrimination for exercising your privacy rights

How to Exercise Your Rights

You can exercise most of these rights directly through your account:

• Data Export: Go to Account Settings to download a ZIP export of your account data, including conversations, billing records, media files, and other personal data we hold that is linked to your account. The automatic export does not include every infrastructure diagnostic. You may separately request access to personal data we hold outside the export, subject to applicable legal exceptions.
• Account Deletion: Go to Account Settings to delete your account and initiate removal of operational data. Deletion timing, technical delays, payment records, and post-deletion email suppression are handled as described under Data Retention.
• Profile Changes: Edit or remove your profile information at any time in Account Settings.
• Email suppression: For support, privacy requests, data protection requests, abuse reports, copyright complaints, illegal content reports, and legal notices, contact us at support@risphai.com. If your email is blocked from new registration after you deleted your account and you believe that is wrong, use the same address and describe the issue.
• Other requests: For support, privacy requests, data protection requests, abuse reports, copyright complaints, illegal content reports, and legal notices, contact us at support@risphai.com. We respond within the period required by applicable law, normally one month under the GDPR or 30 days under Swiss law, and explain any lawful extension. We may request proportionate identity verification.

Essential (Required)

• Authentication: Cookies and app storage needed to sign in and maintain a session. Blocking them may prevent account features from working.
• Bot protection: Cloudflare Turnstile, where enabled on authentication and public legal forms, processes device, browser, network, and interaction signals to detect abuse. Its processing is separate from optional analytics.

Functional (Local and Session Storage)

We use browser local storage (not cookies) to remember your preferences. Some items remain on your device; preferences or content you submit may also be synchronized to your account or included in service requests:

• Theme preference: Your light/dark mode setting.
• Incognito mode: Whether incognito is enabled and limited recovery identifiers for an active request in the same browser session; this recovery storage does not include the prompt or response.
• Cookie consent: Your cookie preference choice.
• Draft text: Unsent message drafts (temporary).
• Model preferences: Your default AI model selections.

Session Storage (Ephemeral)

We use browser session storage for temporary signup details such as your email, form choices and return destination when you open our Terms or Privacy Policy. Signup passwords are not saved in this draft. Session storage generally lasts for the tab's session; browser session restoration may preserve it. We remove the signup draft after successful submission for email verification. The draft is not sent to our servers just to preserve the form; details you submit for registration are processed as described elsewhere in this policy.

Native Device Storage

The mobile apps store authentication information, preferences, drafts and copies of supported account content on your device to provide access and offline viewing. The local content database uses encryption; downloaded media is held in the app's cache. These copies can remain until refreshed, evicted or cleared. You can use the app's offline-storage controls or remove local app data through your device. Server deletion does not instantly erase exports, downloads or copies on disconnected devices.

Third-Party Embeds (Consent Required)

The following third-party services may set cookies or tracking technologies, but only if you accept them through our cookie consent banner:

• YouTube embeds: When AI responses include YouTube videos, the YouTube player may set tracking cookies. Videos are not loaded until you accept third-party embeds.
• Google Maps embeds: When AI responses include maps, Google Maps may set tracking cookies. Maps are not loaded until you accept third-party embeds.

Website Analytics (Consent Required)

When you opt in to Website Analytics, Cloudflare Web Analytics measures visits and browser performance on selected public information pages. We do not load its beacon before your choice. It is excluded from chat, account, authentication, billing, shared-content and native-app pages, and pages with URL parameters or fragments. Measurements may include public page URLs, referring sites, browser/device information and performance timings. Network requests expose connection information to Cloudflare; this is not a promise of anonymous processing. Cloudflare states that Web Analytics does not use cookies, local storage or fingerprinting to identify visitors. Our separate preference record is stored in your browser.

Analytics consent lasts up to 180 days on this browser. Withdrawal stops subsequent analytics requests from this browser, including requests by an already loaded beacon; it does not undo earlier lawful processing. Cloudflare processing and international transfers are subject to the arrangements described in Sections 5 and 6. Hosting and security logs remain separate.

You can accept, reject, or change optional preferences through Cookie Settings, including from this page's footer. Rejecting optional features does not prevent essential account access. Native crash diagnostics are described separately in Section 2.

Risphai is intended only for adults aged 18 and over. People under 18 may not create an account or use the Service, including with parental permission.

At signup, account holders must confirm that they are at least 18 and accept the Terms. This confirmation is a declaration of eligibility; additional checks may be needed if we have reason to doubt it.

For support, privacy requests, data protection requests, abuse reports, copyright complaints, illegal content reports, and legal notices, contact us at support@risphai.com.

If we learn that we have collected personal data from someone under 18, we will take steps to delete that information. Tell us at the same address if you believe this has occurred.

Incognito requests are not saved as normal conversation history. Optional account profile details, custom instructions, and saved memories are excluded from incognito AI context. Information you type, upload, or otherwise supply in the request is still processed and may itself identify you.

Accepted work may continue after navigation or disconnection and may consume credits. Request content, output, and recovery state are held temporarily so processing can finish and the same session can reconnect. Completion, abandonment and expiry trigger cleanup, subject to active-work deferral and retries. Temporary media older than 24 hours is targeted by the scheduled sweep; that threshold is not a guaranteed deletion deadline. Closing a tab does not mean that all processing and deletion finish immediately.

Account, payment, security, and enforcement records remain subject to their separate retention rules. Providers receiving your requests apply the retention rules of the relevant service and agreement, including safety and legal retention. Incognito does not make you anonymous to Risphai or its providers. The model ZDR option is separate; see Section 12.

Incognito is designed to keep chats out of normal history; it is not a guarantee of error-free processing or immediate deletion of every copy. Bugs and other technical failures may cause unintended storage or longer retention. The handling of these delays is explained in Section 7.

Privacy Mode controls eligible text-model generation and routing. You can change it in chat settings and save a default to your account.

No Training on Data (Default)

Risphai does not use your conversations or personal data to train AI models. Eligible AI requests use API services under their applicable no-training terms and processing arrangements. This setting does not mean that request data is never retained.

Zero Data Retention (ZDR)

Eligible requests use supported hosted open-source services or OpenRouter inference endpoints configured for no training and no persistent prompt or completion storage under the relevant provider arrangements. For OpenRouter requests, we enforce its per-request Zero Data Retention filter and our allowed inference providers. This can make supported proprietary text models available in ZDR mode. Endpoint availability varies; a request with no eligible endpoint may use another eligible model or fail. It does not fall back to non-ZDR text processing. Temporary inference processing and in-memory prompt caching may still occur. OpenRouter and inference providers may retain request, billing, and security metadata; ZDR does not disable that metadata processing.

Scope: ZDR covers eligible text-model inference, including the text synthesis part of research. Image generation and editing, video generation, and audio generation stay available but do not support ZDR. Web search, page reading, research or transcript retrieval, voice features, and required moderation and security checks are not affected by this model setting and follow separate retention rules. ZDR also does not remove saved Risphai conversation history, billing records, or security records. Incognito separately limits conversation-history storage.

Cost and speed: ZDR may be more expensive and slower because requests are limited to providers with eligible Zero Data Retention endpoints. Fewer providers are available to serve the request.

Outside eligible ZDR processing, providers may retain content for service operation, safety monitoring, or legal obligations; retention depends on the feature and agreement. Contact support for information about retention applicable to a request. Do not assume that one retention period applies to every provider or feature.

The Zero Data Retention label describes this limited provider setting, not a guarantee that the whole Service stores no data or operates without bugs. Technical failures may affect privacy controls or delay cleanup, as explained in Section 7. We remain responsible for applicable data protection obligations.

Risphai provides AI-generated responses and media. Outputs can contain errors, fabricated sources, bias, or inappropriate content and should be checked before use.

• Request context: We may send relevant conversation history, files or extracted content, and optional personalization to one or more providers to deliver your request. Incognito excludes saved account personalization.
• Search and retrieval: Queries and URLs may reveal personal information. Retrieval providers are outside the model ZDR setting and may retain request data under their applicable arrangements.
• Voice and audio: Providers process live audio, uploaded audio, or text for speech. Risphai does not keep a live voice recording as conversation history; non-incognito text transcripts may be saved and follow conversation retention. Uploaded and generated audio follow file retention rules.
• Safety: Automated screening may process messages, files, extracted content, and instructions. We may refuse processing or restrict access for suspected violations. Screening can make mistakes; you may request review by a person through support.
• Training and retention: We do not train AI models on your conversations. No-training processing and no-retention processing are different; the limits of each privacy setting are explained in Section 12.
• Shared conversations: If you enable a share link, anyone who receives the link may access the shared content and copy it. Revoking a link does not recall copies already obtained. Check content for personal or confidential information before sharing.

We use measures including encrypted network connections, access controls, account authentication, optional multi-factor authentication, and restricted file access to protect personal data. Access needed for authorized operations and content you deliberately share follows the relevant permissions.

No system can guarantee absolute security. We remain responsible for safeguards and for investigating and notifying personal-data breaches where applicable law requires. Security limitations do not waive your data protection rights.

We do not sell your personal information. We do not share your personal information with third parties for cross-context behavioral advertising. We do not use your data for targeted advertising of any kind.

Data shared with third-party service providers (as listed in Section 5) is shared solely for the purpose of operating the Service and is subject to the applicable processor agreements or independent-controller terms, as described in Section 5.

We may update this Privacy Policy from time to time to reflect changes in our practices, the Service, or applicable laws. When we make material changes, we will:

• Update the "Last updated" date at the top of this page
• Notify you via email or through a prominent notice within the Service

Changes to this notice do not create consent or authorize a new incompatible use of personal data. Where a change requires consent or advance notice, we will obtain it or provide it as required by law.

Privacy features have the specific scope described in this policy. Provider policies explain additional processing, but do not replace our duties as controller or our responsibilities for processors we engage.

Nothing in this policy or the Terms of Service excludes mandatory privacy rights, complaint rights, or compensation required by applicable law. We may protect confidential technical details when answering requests, while providing disclosures required by law.

For support, privacy requests, data protection requests, abuse reports, copyright complaints, illegal content reports, and legal notices, contact us at

If you have any questions, concerns, or requests regarding this Privacy Policy or our data practices not covered above, please contact us using the same address.

You may complain to the Swiss Federal Data Protection and Information Commissioner or, where applicable, the supervisory authority in your country of residence, work, or the place of an alleged infringement. You do not need our permission to make a complaint.

If you are located in the EU/EEA and have questions or concerns regarding your personal data, you may contact our appointed GDPR representative:

To submit a Data Subject Access Request (DSAR), data deletion request, or any other GDPR-related enquiry, please use our secure DSAR portal.