Privacy Notice
Courtesy translation: only the German version is legally binding. German version
Last updated: 11 November 2026
This notice applies to:
- the ArchX desktop app for Mac and Windows (the ‘app’);
- the online service for licence, trial, purchase, seats, invoices, updates and support, including its web pages such as ‘Download’, the purchase page and ‘Manage seats’ (the ‘service’).
It is based on the Swiss Federal Act on Data Protection (FADP, DSG). For persons in the EU, in particular in Germany and Austria, the General Data Protection Regulation (GDPR) also applies.
1. Controller
TYTOS GmbH
Arsenalstrasse 40
6010 Kriens
Switzerland
UID CHE-351.360.864
Contact for data protection: tim@frontierx.ch
2. The key points in brief
- We do not process your project data.
- The app stores plans, documents, tasks, conversations and results on your device, not at TYTOS.
- For the AI work, they go directly from your device to the AI provider you choose in the app: via your ChatGPT account to OpenAI, or with an API key to the provider of that key.
- Your company and that provider are responsible for this, not TYTOS (section 3).
- The app keeps an API key only in the credential store of your device’s operating system. TYTOS never receives it.
- For official records, some of the app’s tools query public geodata services directly, with the address, plot or coordinates of the project, never with your files (section 3).
- If you open ‘Find work’ or ask for it in a conversation, the app reads public tenders directly at the source, without any details about your practice (section 3).
- We process only what we need for the contract and operation: email address and installation ID for the licence, purchase and billing, support reports, update checks and error codes.
- Usage counters, switched on by default and can be switched off at any time. The app counts figures without content, such as app starts, tasks and active minutes (section 4.10).
- Accompanying trial emails: at most four short emails during and shortly after the trial; a reply ‘Stop’ is enough, and then no more will come (section 4.12).
- Follow-up when a purchase stays open: only if you tick the box on the purchase page, at most one short email asking whether Tim Gashi can help (section 4.12).
- Project data reaches us only if you send it yourself: as an attachment with ‘Report a problem’ or by email to support. We then process it on your behalf in accordance with the Data Processing Agreement (DPA).
3. What does not end up with us: project data and AI providers
What goes to the AI provider: The app works with OpenAI’s Codex core. For each task, the core sends to the AI provider you have selected in the app, with an API key via a translation step within the app itself:
- the task text, attachments and the conversation history;
- the details of your practice profile (such as areas of focus, area of work, team and references) that ArchX passes on with every conversation;
- the contents of files the agent reads;
- results of the tools and images;
- the beginning of a new task, so that the provider suggests a title for the conversation;
- with the setting ‘Approve for me’, the agent’s requests on which an AI decides.
Which provider: The connection runs directly from your device to the provider, without any intermediary service. TYTOS does not receive this data, sees neither content nor keys and is neither controller nor processor for this processing. The provider is determined by the AI access you connect in the app:
- Your ChatGPT account: The data goes to OpenAI.
- An API key: The data goes to the provider of the key. The options are:
- OpenAI (api.openai.com);
- Anthropic (api.anthropic.com);
- Google (generativelanguage.googleapis.com);
- Mistral (api.eu.mistral.ai): The app uses Mistral’s European location with data centres in the EU or the EFTA;
- xAI (api.x.ai).
With your ChatGPT account: Your contract and OpenAI’s privacy terms apply. Your password and the access keys of your ChatGPT account remain with OpenAI or in your device’s keychain. From the account, the service receives at most its email address (sections 4.1 and 4.7).
Whether OpenAI uses your content for training depends on your plan and your settings. According to OpenAI, content from ChatGPT Business, Enterprise and Edu is not used for training by default (OpenAI: Enterprise privacy). With Plus and Pro, this happens as long as the setting to improve the model is switched on; according to OpenAI, this setting also applies to tasks via Codex and thus via ArchX (OpenAI: Data Controls).
With an API key: Your company concludes the contract for the use of the models directly with the provider. The provider’s terms of business or API terms and its privacy terms apply, and the provider bills your company directly.
- The app checks the key with the provider and keeps it only in the credential store of your device’s operating system, on the Mac in the Keychain, under Windows in Credential Manager. The key is not stored in any file and goes to no one except the selected provider.
- According to the providers, as retrieved on 7 October 2026, OpenAI, Anthropic, Google and xAI do not use data from the API to train their models by default. For Google, this applies to the paid tier. For applications made available to users in Switzerland, Google permits only the paid tier, and for users in Switzerland Google applies the data rules of the paid tier to all tiers (Gemini API Additional Terms). With Mistral, you must opt out of training in your account with Mistral.
- For abuse detection, OpenAI, Anthropic, Mistral and xAI retain API data for up to 30 days, Google for 55 days; if violations are suspected, also for longer. Each provider sets out the details in its terms and its documentation.
Your practice catalogue: A practice catalogue that you connect in the app is read by the app on your device; it never goes to TYTOS. What the agent reads from it for a task may go to your AI provider like other content.
What the core itself could report: The Codex core has its own functions for usage statistics, metrics and feedback to OpenAI. The app switches them off.
Tools you connect yourself: The browser tool, MCP servers, plugins and account apps connect to the providers you choose. You or the respective provider are responsible for these data flows.
Downloads directly from third parties: The app downloads some components directly from the manufacturer. In doing so, these providers see your IP address, but receive no data from us:
- new versions of the Codex core from npm (registry.npmjs.org);
- directories of plugins and apps that the Codex core retrieves from OpenAI on every start, via github.com and chatgpt.com, and from the providers of the plugins;
- the Archicad add-on Tapir from GitHub (github.com), only if you confirm the set-up of the connection to Archicad;
- your practice’s website, only after you have confirmed that ArchX may read it for the practice profile;
- under Windows, the speech model from Hugging Face, only if you set up voice input;
- on the Mac, language packs from Apple;
- under Windows, spell-checking dictionaries from a Google server.
According to Electron, no input is transmitted in the process.
Public geodata and official records: For the feasibility study, the building application compliance statement, the excavation and the assignment of site photos, the app queries public services directly from your device, without any intermediary service:
- the federal geodata services (api3.geo.admin.ch, data.geo.admin.ch, wms.geo.admin.ch) and geodienste.ch;
- for the feasibility study and the building application compliance statement, the canton’s cadastre of public-law restrictions on landownership (ÖREB cadastre), the services named in the ÖREB extract (maps and legends of the canton, enactments and plans on pages of the canton and the municipality), and for federal enactments the publication platform for federal law;
- for a feasibility study in the Canton of Lucerne, the canton’s geoportal (svc.geo.lu.ch).
Depending on the service, it receives the project address or the plot as stated in the task, coordinates of the property, the EGRID of the plot, for the building application compliance statement also the EGIDs of the buildings and the EGRIDs of adjacent road plots, map extracts around the property, in the Canton of Lucerne the outline of the plot and, for collections of laws, only the number of the enactment. Location and extract may come from your documents, for example from the georeference of an IFC model or the extent of a point cloud. When outputting a bid comparison, the app also checks the postcodes of the building owner and of the project in the official directory of localities (api3.geo.admin.ch). Files, plan images, photos and conversation content never go to these services. As with the downloads, each of these services sees your IP address. TYTOS does not receive this data.
Public tenders and competitions (‘Find work’): Only when you open ‘Find work’ in the app or ask for it in a conversation does the app read the public procedures of the simap platform (www.simap.ch) directly from your device, without any intermediary service. From then on, it reads the source about every six hours while the app is running, also after a restart of the app, and additionally when you open ‘Find work’, choose ‘Check now’ or ask for it in a conversation. You can switch off the regular reading in the background at the bottom of the ‘Find work’ page.
In doing so, simap receives search details with no connection to your practice (planning service codes, type of publication and period) and, if ArchX reads an individual procedure in more detail for you, its identifier, the identifier of the tendering body and the identifiers of up to five earlier awards by that body. Name, address, area of work, references and other details about your practice do not go to simap; the app compares with your practice profile only on your device. As with any website visit, simap sees your IP address and technical details of the connection and, from the program identifier of the request, that it comes from ArchX. If the platform sets a cookie in the process, it is valid only until the app is closed. The app stores the procedures read, your decisions (‘Save’, ‘Not for us’) and the state of the source only on your device. TYTOS does not receive this data.
ArchX passes your practice profile, including area of work and references, on with every conversation; it thus goes to your AI provider like other content. If you ask about commissions in a conversation, the procedures found and the saved procedures, with the details of their publication, are added, together with ArchX’s reasoning, which may name individual references of yours. If ArchX reads a procedure in more detail, the contact details of the contracting authority and earlier awards by the same authority (procedure, number of submissions, name, location and amount of the winners) also go to your AI provider as simap publishes them. When an application is being prepared, this also applies to the documents and project data that ArchX reads for this purpose. If, at your request, ArchX downloads public documents of a procedure, it retrieves them from your device at the address named in the publication; the body there sees your IP address.
4. Which data we process and for what purpose
4.1 Sign-in and licence (app)
- Data:
- your licence email address: with a ChatGPT account, initially the email address of the ChatGPT account, which the app reads from the sign-in with OpenAI, or another address that you enter in the app and confirm with a code (section 4.2); with an API key, always an address that you enter and confirm in this way;
- a random installation ID that the app generates once;
- operating system (Mac or Windows), processor type, version of the app and of the Codex core;
- time of the check and licence status;
- the IP address of the request; to limit requests, we store only check values derived from IP and email addresses; in addition, there are the operator’s logs (section 4.11).
- When:
- when the app starts and every 24 hours thereafter;
- additionally, when you sign in, choose ‘Check again’ or ‘Check for updates’, or bring a device back into use with ‘Use on this device’, and as soon as a trial ends;
- when you choose ‘Buy licences’ and the last check is more than an hour old, once before the purchase page opens;
- while the app is in read-only mode, and for two hours after ‘Buy licences’ or ‘Manage seats’ has opened the browser: each time you return to the app window, at most once a minute;
- after a failed check, again after 30 minutes.
- Purpose:
- to check the licence and return it signed;
- to enforce a maximum of two active devices per seat;
- to communicate the released update version;
- to detect misuse;
- during the trial: to recognise from the time of the last check whether an accompanying email is appropriate (section 4.12), and whether the practice has the app open today and came back on a later trial day; only we see this, in the operations area, so that we can offer targeted help.
- Legal basis:
- Switzerland: conclusion and performance of the contract (Art. 31(2)(a) FADP);
- EU: Art. 6(1)(b) GDPR;
- for the accompanying trial emails and this overview: our legitimate interest (section 4.12);
- for the query from the device: the check is strictly necessary for the service ordered (Art. 5(3) ePrivacy Directive).
4.2 Device confirmation
- When:
- For paid seats and free seats, each device confirms once that the email address belongs to it.
- If you enter a licence email address in the app other than that of your ChatGPT account, you confirm it in the same way, also during the trial. With an API key, you always enter the address yourself and confirm it in this way.
- Otherwise, there is no device confirmation during the trial.
- How: We send a six-digit code to this email address. The code is valid for 15 minutes. The installation then receives a confirmation key.
- What we store: code and key only as a check value, plus installation ID, email address, time of confirmation and the device details from section 4.1.
- Purpose: to prevent anyone from using a seat with another person’s email address.
- Legal basis: contract (Art. 31(2)(a) FADP; Art. 6(1)(b) GDPR).
4.3 Trial
- Data: email address, start and end of the trial, the installation that started the trial, and the version of the GTC that the app referred to when the AI access was connected, with the time; if the trial start carries campaign tags, these as well (section 4.11).
- Company: When the trial starts, the service creates a company, with you as admin and your address as the first seat.
- Company name: If the app starts the trial by itself, the service derives the name from the domain of your email address; for public email providers, it uses ‘Mein Büro’ (‘My office’). Your admin can change it.
- Purpose: to grant the trial, to evidence the accepted version of the GTC and to ensure that each address receives the trial only once.
- Legal basis: contract (Art. 31(2)(a) FADP; Art. 6(1)(b) GDPR).
4.4 Purchase, company account and seats
- Data:
- on the purchase page: company, email address, number of seats, billing, optionally a referral code and the campaign tags of the link (section 4.11);
- time of the order and the version of the GTC you accepted;
- whether you ticked the box on the purchase page for the follow-up when a purchase stays open, with the time and the wording of the sentence;
- for the seats: the email addresses your admin enters, and who entered them and when;
- admin accounts: email address and role;
- free seats that TYTOS provides to your company.
- Purpose: to conclude and evidence the contract, manage seats, send invitations, assign a sales agent and, if you ticked the box, to ask once when a purchase stays open (section 4.12).
- Legal basis: contract (Art. 31(2)(a) FADP; Art. 6(1)(b) GDPR); for the follow-up, your consent (section 4.12).
4.5 Billing
- Data:
- company, address, UID or VAT number, billing email address;
- subscription, number of seats, payment method, invoices;
- payment events: amount, VAT, time, status.
- Card and TWINT details you enter directly with Stripe. We do not receive them.
- Purpose: invoicing, receipt of payments, dunning, accounting, commission to introducing sales agents.
- Legal basis:
- contract (Art. 31(2)(a) FADP; Art. 6(1)(b) GDPR);
- statutory retention (Art. 958f of the Swiss Code of Obligations, CO; Art. 6(1)(c) GDPR).
4.6 The ‘Manage seats’ page
- Sign-in: with a link by email. The link is valid for 15 minutes and only once.
- Cookie: For the session, we set a technically necessary cookie (‘__Host-archigpt-admin’). It is valid for 12 hours or until you sign out.
- Legal basis: contract.
4.7 Support
Channels: email to support@frontierx.ch and the ‘Report a problem’ button in the app.
What ‘Report a problem’ always sends. You see everything before sending:
- the type of feedback (‘Report a problem’, ‘Request a feature’ or ‘Request a workflow’);
- installation ID and email address of the ChatGPT account (if signed in with ChatGPT);
- operating system and its version, processor type, version of the app and of the core;
- with ChatGPT: plan and remaining allowance as a percentage;
- practice catalogue connected yes/no, licence status;
- up to 50 most recent error codes with their time, e.g. ‘ACC-003’;
- your text.
Only if you select it: at most two attachments, an image of the app window and/or messages that you select individually, at most 40. These may contain project data.
Never included automatically: the Codex core log, conversation histories, project files, the catalogue, access credentials and API keys.
What the service adds: company, seat and licence status from its own data, so that we can assign the report.
Answers in the app (‘Fixed for you’): If your device is confirmed (section 4.2), the app asks the service whether one of your reports has been resolved: for 90 days after a report from this device, as long as answers are available, and once if this device has never asked, in each case when the app starts and thereafter at most once a day. For this, it sends the licence email address, installation ID and confirmation key. If you hide an answer, the app reports this with the number of the report, so that the answer no longer appears on your other devices either.
Where: The service stores reports and attachments in its database in Zurich. We do not currently use an external support tool. Emails to support are held in the mailbox at Infomaniak in Switzerland. The service collects them there and stores sender, subject, date and text in the same database in Zurich; attachments remain only in the mailbox, and the service records their name and size. We use further tools or AI services for support data only if they are named in section 5 and in the DPA.
Purpose: to answer your enquiry and fix errors. If you have provided an email address, we confirm receipt by email; the confirmation contains only the number of the report.
Legal basis:
- Contract (Art. 31(2)(a) FADP; Art. 6(1)(b) GDPR).
- If your text, attachments or emails contain personal data from your projects, we process it as a processor, only on your behalf and only for your enquiry (Art. 9 FADP; Art. 28 GDPR). The DPA, which is an annex to the GTC, applies to this.
4.8 Updates and downloads
- The app’s update check: one minute after the app starts, then every four hours, after a failure as early as after 30 minutes and then at increasing intervals, and when you choose ‘Check for updates’. It states the channel, operating system, processor type and the installed version and, on the Mac, for practices that use ArchX in English, also the language. It contains neither an installation ID nor your email address.
- Explainer video: The signed-in app asks the service at most every six hours whether an explainer video is available, so that it shows the button only in that case. The request contains no identifier and no data from your practice; only the IP address ends up in the operator’s logs (section 4.11). The video itself opens only when you choose the button.
- Data: IP address, time, channel, operating system, processor type and file retrieved.
They are recorded in Vercel’s usual logs (section 5). - Download count: For each download of a file, the service stores the time, the file, the country and whether a program rather than a human downloaded it. We derive the country from the IP address; we do not store the IP address itself or the browser identifier for this. The count does not allow any conclusion about a person.
- First-start count: A newly installed app reports to the service once how far it gets before the first sign-in: window shown, click on ‘Connect’, account connected. Later, it likewise reports once each whether the offer to continue working (purchase of a licence) appeared and whether it was clicked, and, during the trial, whether the suggestion of a next step on your own work appeared (the first task, or suggestions for the next work in one of your projects), which of the two it was and whether it was clicked; it does not report the project’s name. Earlier versions reported instead whether the offer of a set-up call appeared and whether it was clicked. Likewise once each, it reports that the first task was started, that it was completed in a project folder and whether that was within ten minutes of the first window; it does not report the task itself, its result or the times. Each report contains only this step, the operating system, processor type, app version and the app’s market; the service adds the time and the country, which it derives from the IP address. We do not store an installation ID, your email address, the IP address or the browser identifier for this, and the steps are not linked to one another. The count does not allow any conclusion about a person.
- Purpose: to deliver updates and installation packages, to fend off misuse, and to count downloads and first starts so that we can improve getting started with the app and the path to purchase.
- Legal basis:
- contract or overriding interest in secure delivery (Art. 31(1) FADP);
- EU: Art. 6(1)(b) and (f) GDPR.
4.9 Error codes
- What the app stores: only error codes with their time, locally on your device, no message texts, paths or content.
- When they reach us: with their time only with ‘Report a problem’ (section 4.7); without a time, only as a number per code, with the usage counters (section 4.10).
4.10 Usage counters, switched on by default
What is counted, per day and installation:
- number of app starts;
- number of results created per function;
- whether the initial set-up has been completed;
- number of crashes of the Codex core;
- number of tasks, broken down into completed, ended with an error and stopped by you, and for those ended with an error also per error code (e.g. ‘TASK-001’);
- active minutes, i.e. minutes with an input in the app window or a running task;
- for each subject area of the app (such as bid comparison, floor plan or feasibility study), in how many tasks its tools were used.
How: The counters travel with the licence check, collected for at most 31 days. They contain no content, file names or texts: the app does not count what a task asks for, which files it uses or what it produces. We store the counters with the installation ID and your company; in operation, we also see them per seat, i.e. per email address.
Purpose: to recognise whether the app works and how it is used; to support practices on trial and customers in a targeted way, for example when a practice gets stuck; to find problems after new versions.
Legal basis and your choice:
- Our overriding interest in an app that runs reliably (Art. 31(1) FADP; Art. 6(1)(f) GDPR).
- For the transmission from the device, information and an option to refuse are sufficient in Switzerland (Art. 45c(b) of the Telecommunications Act, TCA). The counters are therefore switched on until you switch them off.
- You can switch them off at any time in the app under Settings, General, Licence, with the switch ‘Send usage counts’. When you switch them off, the app deletes counters not yet sent and no longer counts anything. This has no disadvantages.
4.11 Web pages of the service
Server logs: IP address, time, page accessed, browser. At Vercel, for delivery and security.
- Legal basis: overriding interest (Art. 31(1) FADP; Art. 6(1)(f) GDPR).
Cookies and analytics: The web pages set only the session cookie of the ‘Manage seats’ page (section 4.6) and, for persons at TYTOS, additionally a session cookie of the operations pages. We do not use analytics or advertising cookies or tracking tools.
Download links: They may contain a referral code (‘?ref=’). It serves only to assign a sales agent.
Campaign tags in links: Links to the service, for example from our emails or from our website, may carry campaign tags (‘utm_source’, ‘utm_medium’, ‘utm_campaign’, ‘utm_term’, ‘utm_content’). The service accepts only short tags made up of letters, digits and the characters ‘.’, ‘_’, ‘~’ and ‘-’, and thus never an email address. It stores them with an order on the purchase page and passes them on to Stripe with that order; if the app’s trial start carries such tags, it stores them with the company. This lets us see which campaign led to a trial or purchase, without advertising cookies, device fingerprints, tracking of opened emails or your history on other sites. You can remove the tags from the address before opening it or object to the processing. The tags of a trial remain with the company; those of an order are kept for as long as the order (section 7).
- Legal basis: overriding interest in understanding which campaigns lead to contracts (Art. 31(1) FADP; Art. 6(1)(f) GDPR).
Contact by email: We use your details to answer the enquiry.
4.12 Emails from the service
The service sends via Resend: sign-in links, device codes, invitations, order confirmations and confirmations of subscription changes, a reminder one day before the end of the trial, the accompanying trial emails (below), with your consent a follow-up when a purchase stays open (below), invoices with a QR payment slip and acknowledgements of receipt for support reports. For this, Resend receives the recipient address and the content of these emails. The service does not send any other promotional emails.
Accompanying trial emails: During and shortly after your trial, the service automatically sends you at most four short emails in Tim Gashi’s name: on the first morning of the trial, a welcome with the end of the trial and a pointer to the first task; two to three days after the start, a short guide to the first task, if the app has not been opened for a day and a half; two to four days before the end of the trial, a note about purchasing, if the app was opened after the first day and in the last three days; two to seven days after the end of the trial, a note about purchasing, if your company has not purchased and the app was opened after the first day. They go to one person per practice: to the owner, otherwise to the admin entered first. Anyone who is already in discussion with Tim Gashi or a partner does not receive them.
- Data: your email address, start and end of the trial, the time of the last licence check of your practice’s installations (section 4.1), whether your company has purchased or started a purchase, whether you or your company have written to support, whether an origin or a sales agent is recorded for your company, whether your address or your practice’s domain appears in our records of customers, appointments and conversations, and when the service last sent your practice a trial email. For the comparison with our records, the service receives only checksums (SHA-256) of addresses and domains, no list in plain text. We do not use usage counters or content for this.
- Unsubscribing: Reply with ‘Stop’ or write to support@frontierx.ch; you will then receive no more accompanying trial emails. Any reply and any support report also ends them.
- Legal basis: our legitimate interest in helping trial customers get started and offering them the purchase of ArchX (Art. 31(1) FADP; Art. 6(1)(f) GDPR). You can object to this at any time (Art. 21(2) GDPR).
Follow-up when a purchase stays open: Next to the email field on the purchase page, you can tick that Tim Gashi may write to you if you do not complete the purchase. Only then, and if the purchase is still open an hour later, the service sends you at most one short email in his name: whether he can help, with the link back to the purchase page. It goes only within the first 48 hours after the purchase began, and not if your company has purchased in the meantime, if you are already in discussion with Tim Gashi or a partner, or if you have received such an email in the last 30 days. The box is voluntary; you can buy without it.
- Data: your email address, the state of the order, whether and when you ticked the box and the wording of the sentence next to it, plus the same details as for the accompanying trial emails (purchase, support, origin and sales agent, comparison with our records via checksums, last email to your practice).
- Withdrawal: at any time, even before the email, with a reply ‘Stop’ or to support@frontierx.ch.
- Legal basis: your consent (Art. 31(1) FADP; Art. 6(1)(a) GDPR).
4.13 Sales agents and introducers
From persons who introduce customers to us, we process:
- name, email address, address, proof of company registration or of AHV registration (Swiss old-age and survivors’ insurance), VAT status;
- bank details, commission statements.
This serves the performance of the introduction agreement and accounting.
5. Recipients, storage locations and safeguards
We pass on data only to providers we need for operation. Unless stated otherwise, they work on our behalf and according to our instructions. For each recipient, we state the country and the safeguard (Art. 19(4) FADP).
- Vercel Inc., USA: operation of the service and its web pages; storage of the installation packages and updates in Vercel Blob.
- The service’s functions and the Blob storage run in Frankfurt (Germany). Delivery takes place via Vercel’s global network, which caches content; Vercel also processes data in the USA.
- Safeguard: Vercel is certified under the Swiss-U.S. Data Privacy Framework (Annex 1 to the Data Protection Ordinance, DPO); for the EU under the EU-U.S. Data Privacy Framework.
- Supabase Pte. Ltd., Singapore: the service’s database, stored in Zurich (Switzerland) at Amazon Web Services. Supabase and its sub-processors, for example Supabase, Inc. in the USA for support, may access it from abroad in individual cases.
- Safeguard: EU standard contractual clauses with the adaptations for Switzerland in Supabase’s data processing agreement (Art. 16(2)(d) FADP).
- Stripe: payments, invoices and customer portal. The contracting party is Stripe Payments Europe, Limited (Ireland) and, for payment services in Switzerland, additionally Stripe Payments UK Ltd (United Kingdom). Stripe passes data on to Stripe, LLC in the USA. Stripe partly processes data as a controller in its own right, for example for fraud prevention and because of legal obligations.
- Safeguard: Ireland and the United Kingdom provide adequate protection (Annex 1 DPO); Stripe, LLC is certified under the Swiss-U.S. Data Privacy Framework.
- Resend (Plus Five Five, Inc.), USA: sending of the service’s emails (section 4.12). The data is located in the USA.
- Safeguard: EU standard contractual clauses with the adaptations for Switzerland in Resend’s data processing agreement (Art. 16(2)(d) FADP).
- Infomaniak Network SA, Geneva: email mailbox for contact and support. The data is located in Switzerland.
- Help Scout PBC, USA: not currently used. Before we process support reports there, we will supplement this notice and announce this in accordance with the DPA. The safeguard would then be the EU standard contractual clauses with the adaptations for Switzerland in Help Scout’s data processing agreement.
In addition, where necessary, our fiduciary and legal advisers, as well as authorities where the law requires it.
The AI providers, i.e. OpenAI and the providers of the API keys, are not recipients of data that we process. The connection to them runs via your own ChatGPT account or your own API key (section 3).
6. Transfers abroad: the rules
Swiss law:
- According to the Federal Council’s determination, the countries of the EU and the EEA as well as the United Kingdom provide adequate protection (Art. 16(1) FADP; Annex 1 DPO).
- Since 15 September 2024, the USA has been considered adequate only for companies certified under the Swiss-U.S. Data Privacy Framework (Annex 1 DPO).
- With other recipients, the EU standard contractual clauses recognised by the FDPIC (EDÖB), with the Swiss adaptations, apply (Art. 16(2)(d) FADP). This currently concerns Supabase and Resend.
EU law:
- For Switzerland, there is an adequacy decision of the European Commission (Art. 45 GDPR; Decision 2000/518/EC).
- For certified US companies, Decision (EU) 2023/1795 on the EU-U.S. Data Privacy Framework applies.
- Otherwise, standard contractual clauses under Implementing Decision (EU) 2021/914 apply (Art. 46(2)(c) GDPR).
You can obtain a copy of the safeguards on request.
7. Retention and deletion
The service deletes expired data with a daily run.
- Sign-in links and device codes: They are valid for 15 minutes and are stored only as a check value. The daily run deletes expired device codes and sign-in links, the latter one day after expiry. Sessions of the ‘Manage seats’ page end after 12 hours.
- Check values derived from IP and email addresses for limiting requests: around two hours.
- Installations (ID, device, versions, device confirmation, last seen): We delete them 24 months after the last activity, i.e. the last licence check. We delete usage counters 24 months after the day counted, the download count 24 months after the download and the first-start count 24 months after the reported step.
- Support reports: We delete them 24 months after receipt.
- Attachments to support reports: deleted in the service 30 days after forwarding to the support inbox, at the latest after 90 days. As long as we do not use an external support inbox, therefore 90 days after receipt. We delete emails to support as soon as they are no longer needed, at the latest 24 months after receipt.
- Companies, seats and admin accounts: during the trial or the contract. If the trial ends without a purchase or the contract ends, we anonymise the company’s personal data, such as email addresses, 24 months after the end.
- Invoices, payment events, orders and commission statements: 10 years from the end of the financial year (Art. 958f CO), then deleted.
- Sales agents and introducers: for the duration of the introduction agreement; statements and payment details for 10 years thereafter (Art. 958f CO).
- Server and download logs as well as data at Stripe: in accordance with the providers’ retention periods.
8. Your rights
You can request from us:
- Access to your data (Art. 25 FADP; Art. 15 GDPR). Free of charge and as a rule within 30 days.
- Rectification of inaccurate data (Art. 32(1) FADP; Art. 16 GDPR).
- Erasure or the prohibition of processing (Art. 32(2) FADP; Art. 17 GDPR), provided that no retention obligation precludes this.
- Release of your data in a common electronic format (Art. 28 FADP; Art. 20 GDPR).
- Restriction of processing (Art. 18 GDPR).
- Objection to processing based on overriding interest, in particular to the usage counters (Art. 30(2)(b) FADP; Art. 21 GDPR).
- Objection to the accompanying trial emails (direct marketing, section 4.12): at any time and without giving reasons, with a reply ‘Stop’ or to support@frontierx.ch (Art. 30(2)(b) FADP; Art. 21(2) and (3) GDPR).
- Withdrawal of consent with effect for the future (Art. 7(3) GDPR), in particular of the consent to the follow-up when a purchase stays open (direct marketing, section 4.12): at any time and without giving reasons, with a reply ‘Stop’ or to support@frontierx.ch.
How: Write to tim@frontierx.ch. We may request proof of identity.
Complaint:
- in Switzerland, to the Federal Data Protection and Information Commissioner (FDPIC, EDÖB);
- in the EU, to the supervisory authority of your country (Art. 77 GDPR).
9. Security
Protection of transmission:
- encrypted transmission between app and service;
- signed licences.
Access:
- access protection per database row; only the service itself reads and writes;
- the service’s secret keys for signing, payment, email and database are kept only in the service, never in the app;
- sign-in links, device codes and keys only as check values.
Data minimisation:
- The service accepts only the defined fields; it rejects all others.
- Project content, file names, paths, conversation texts, catalogue and standards texts and API keys are not provided for in the contract between app and service.
- The service’s logs contain no email addresses and no content.
10. Automated decisions
Depending on the trial or payment status, the licence check automatically switches the app to read-only mode. On request, a human reviews any such block, and you can state your point of view (Art. 21 FADP).
11. Changes
We adapt this notice when the app, the service or the law changes. The version published here at any given time applies. We notify the admins of material changes by email.