Privacy Policy
How we collect, use, and protect your dataPrivacy Policy Overview
This privacy policy is structured to provide comprehensive information about how we handle your data. Below are the main sections covered:
1. Company/Owner Information
Essential contact information for Ögren Digital including company address, email, phone number, and general contact details for privacy-related inquiries.2. Privacy Notice for Swiss Residents
Specific privacy notice for Swiss residents covering FADP compliance, data protection principles, your rights under Swiss law, international data transfers, and information about our Swiss data protection representative.3. General Privacy Policy Highlights
Overview of our data processing practices including audio processing and text processing, local data storage, third-party services, user account management and more.4. Contact Information for Representatives
Contact details for our Swiss representative (for FADP matters) and GDPR representative (for EU data protection matters), including addresses, phone numbers, and email contacts for data protection inquiries.Company/Owner Information
Company Name:
Ögren Digital
Ögren Digital
Product Brand Name:
WritingAnt
WritingAnt
Address:
Loretostrasse 1
6300 Zug
Switzerland
Loretostrasse 1
6300 Zug
Switzerland
Phone:
+41 (0) 77 267 65 62
+41 (0) 77 267 65 62
For questions about this privacy policy, please contact us using the information above.
Privacy Notice for Swiss Residents
This Notice outlines how Ögren Digital processes personal data of Swiss residents in compliance with the Swiss Federal Act on Data Protection (FADP) and the Swiss Data Protection Ordinance (DPO).
Data Protection Principles Under FADP
FADP is underpinned by six important principles that Ögren Digital adheres to. These principles require that personal data must: Be processed lawfully; Be processed in good faith and proportionately; Be collected for a specific purpose that the data subject can recognise; and may only be further processed in a manner that is compatible with this purpose; Be destroyed or anonymised as soon as they are no longer required for the purpose of processing; Be accurate and kept up to date; If processed with consent as a lawful base, the consent is given voluntarily for one or more specific instances of processing based on appropriate information.
Legal Basis for Processing
Ögren Digital relies on the following legal bases for processing: Your consent, Performance of a contract with you, Compliance with a legal obligation, Protection of your vital interests, Our legitimate interests, provided they do not override your fundamental rights and freedoms, Public interest or exercise of official authority.
Your Rights Under FADP
As a Swiss resident, you have the following rights regarding your personal data:
Right of access to personal data
(including right to receive the following information: Identity and contact details of the data controller, the personal data processed, purpose of processing, retention period or criteria, source of data (if not collected from the data subject), information about automated individual decisions and their logic, recipients of personal data)
(including right to receive the following information: Identity and contact details of the data controller, the personal data processed, purpose of processing, retention period or criteria, source of data (if not collected from the data subject), information about automated individual decisions and their logic, recipients of personal data)
Right to data portability
(including the right to request from us to deliver your personal data to another controller in a conventional electronic format if: your data is being processed in an automated way and if your data is being processed with your consent or in direct connection with performance of a contract between Ögren Digital and you.
(including the right to request from us to deliver your personal data to another controller in a conventional electronic format if: your data is being processed in an automated way and if your data is being processed with your consent or in direct connection with performance of a contract between Ögren Digital and you.
Right to personal data deletion or destruction
Right to personal data rectification
(including the right to demand correction of inaccurate personal data and the right to request that disputed data be marked as such)
(including the right to demand correction of inaccurate personal data and the right to request that disputed data be marked as such)
Right to personal data processing prohibition
Right to personal data non-disclosure
Right to be informed of measures taken
(including the right to request that measures related to deletion, rectification, prohibition of processing, or non-disclosure of your data be published or communicated to third parties)
(including the right to request that measures related to deletion, rectification, prohibition of processing, or non-disclosure of your data be published or communicated to third parties)
To exercise these rights, please contact us at info@oegren-digital.ch. We will respond to your request within 30 days.
International Data Transfers
Ögren Digital may transfer personal data outside Switzerland to countries whose law does not ensure an adequate level of data protection, provided that data protection is ensured by other mechanisms, in particular on the basis of standard data protection clauses or other suitable guarantees. In exceptional cases, we may export personal data to countries without adequate or suitable data protection if the specific data protection requirements are met, for example, the express consent of the data subjects or a direct connection with the conclusion or processing of a contract.
We will gladly provide data subjects with information about any guarantees or provide a copy of any guarantees upon request.
Sub-processors: third-party services and data transfers
The letter A or B under “Service Provided” shows under which text-processing option a party sees the text you send. Which option applies is your own choice: when you install the application, before you can start using it, it asks you to choose between option A, Global (including the United States), where the text goes to OpenAI through our Azure services, and option B, Switzerland & Europe, where it goes to our European service on Scaleway (Paris) and the Swiss AI host PHOENIQS and never reaches Microsoft or OpenAI. No option is preselected, and you can change your choice at any time in the settings. The option applies only to the text-processing step; usage events without text, account and billing data are handled by the same parties under both options.
Business customers: these sub-processors are also listed in Annex IV of our Data Processing Agreement (Article 28 GDPR, Article 9 FADP), which applies automatically to business use of WritingAnt.
Your Right to Object to a Transfer
You have the right to object to the transfer of your personal data to these third parties. To exercise this right, please contact us at info@oegren-digital.ch. Please note that objecting to certain data transfers may affect our ability to provide certain services to you.
Swiss Representative
Under Article 14 of the FADP, we have appointed a Swiss Representative to act as our data protection agent. Our nominated Swiss Representative is:
Company:
ALTRION Sagl
ALTRION Sagl
Phone:
Tel +41 78 229 72 57
Tel +41 78 229 72 57
Address:
Via Luigi Lavizzari 8
6850 Mendrisio
Switzerland
Via Luigi Lavizzari 8
6850 Mendrisio
Switzerland
Legal Protection
Data subjects have the right to enforce their data protection claims through legal channels or to lodge a complaint with a competent data protection supervisory authority. The data protection supervisory authority for private data controllers and federal bodies in Switzerland is the Federal Data Protection and Information Commissioner (FDPIC). In the case of projects financed by cantons or municipalities in Switzerland, the cantonal data protection commissioners are responsible in some cases.
Highlighted user responsibility related to data during usage of our services
Our services allow users to input and process speech and or text content as part of the main functionality of this speech-to-text software, including through third-party AI providers (find more details in the main privacy policy at the link below). We recommend that users avoid using personal or sensitive information when recording audio for speech-to-text, text enhancements, and audio prompts for creative writing, or when using text as input for text enhancements. Users are responsible for the content they choose to submit and should ensure that they have the legal right to process such information.
Local Audio Processing and Data Handling
Audio Stays Local:
Your audio recordings never leave your device. All audio data from your microphone is processed locally on your computer and is never transmitted to our servers, third-party services, or any cloud infrastructure.
Your audio recordings never leave your device. All audio data from your microphone is processed locally on your computer and is never transmitted to our servers, third-party services, or any cloud infrastructure.
Initial Speech-to-Text Processing:
The first step of converting your speech to text happens entirely on your computer using local speech recognition technology. This initial transcript is created without any data leaving your device.
The first step of converting your speech to text happens entirely on your computer using local speech recognition technology. This initial transcript is created without any data leaving your device.
Transcript Enhancement:
Only the text transcript (not the audio) resulting from the local speech-to-text conversion is sent to our cloud services for further enhancement and improvement. This text-only data is then processed through our AI services to create well-written, formatted text. We never use your transcripts, selected text, results or any other content to train or improve AI models, and OpenAI and PHOENIQS, the AI providers behind the two text-processing options, are contractually bound not to use them for that purpose either. Custom writing styles work differently from training: the style descriptions and the examples you save with "Train by examples" are stored on your computer and are sent along with your text in each request that uses that style, as instructions to the AI model. This improves the results for you through prompting, not by training a model, and your examples are used only for your own requests, or for those of colleagues with whom you have shared a style by exporting it.
Only the text transcript (not the audio) resulting from the local speech-to-text conversion is sent to our cloud services for further enhancement and improvement. This text-only data is then processed through our AI services to create well-written, formatted text. We never use your transcripts, selected text, results or any other content to train or improve AI models, and OpenAI and PHOENIQS, the AI providers behind the two text-processing options, are contractually bound not to use them for that purpose either. Custom writing styles work differently from training: the style descriptions and the examples you save with "Train by examples" are stored on your computer and are sent along with your text in each request that uses that style, as instructions to the AI model. This improves the results for you through prompting, not by training a model, and your examples are used only for your own requests, or for those of colleagues with whom you have shared a style by exporting it.
Applies to All Speech Features:
This local audio processing approach applies to all speech-to-text features in our application, including:
• Standard speech-to-text conversion
• Speech-to-text creative writing features
• Voice command keyword detection and recognition
• All other voice-activated functionality
This local audio processing approach applies to all speech-to-text features in our application, including:
• Standard speech-to-text conversion
• Speech-to-text creative writing features
• Voice command keyword detection and recognition
• All other voice-activated functionality
Privacy Benefits:
This architecture ensures maximum privacy for your spoken content. Your voice, pronunciation patterns, and audio characteristics remain completely private and secure on your device, while still allowing us to provide advanced AI-powered text enhancement services.
This architecture ensures maximum privacy for your spoken content. Your voice, pronunciation patterns, and audio characteristics remain completely private and secure on your device, while still allowing us to provide advanced AI-powered text enhancement services.
Local Event Data Communication
Socket.io Communication:
Our application uses a random available Socket.io port communication to handle real-time data exchange between different components of the application on your local computer.
Our application uses a random available Socket.io port communication to handle real-time data exchange between different components of the application on your local computer.
Application Architecture:
The application consists of both Python backend components and Electron/JavaScript frontend components that need to communicate with each other. This local Socket.ioconnection enables seamless coordination between these different parts of the software.
The application consists of both Python backend components and Electron/JavaScript frontend components that need to communicate with each other. This local Socket.ioconnection enables seamless coordination between these different parts of the software.
Encrypted Communication:
All data transmitted through these Socket.io events are encrypted so only the logged-in user in the operating system should be able to have access. Further limiting is set to only allow a client application to connect from the local computer, and limitation is set to one client application.
All data transmitted through these Socket.io events are encrypted so only the logged-in user in the operating system should be able to have access. Further limiting is set to only allow a client application to connect from the local computer, and limitation is set to one client application.
Highlighted AI Third-Party Services for Data Processing including international data transfers
We use third-party services from Microsoft Azure (hosting of our cloud services and database) and, depending on the text-processing option you choose in the application, either Microsoft Azure and OpenAI Ireland Ltd (Global incl. United States option) or Scaleway and PHOENIQS (Switzerland & Europe option) to process data as part of providing our services, in particular the AI text enhancement and generation features. With the Global option this processing involves international data transfers outside Switzerland, the European Union (EU), the European Economic Area (EEA) and the United Kingdom; with the Switzerland & Europe option your text stays in Switzerland and the EU.
Any such data transfers are carried out in compliance with applicable data protection laws, including the Swiss Federal Act on Data Protection (nFADP) and the General Data Protection Regulation (GDPR). In particular, we rely on Standard Contractual Clauses (SCCs) approved by the European Commission and, where applicable, the UK International Data Transfer Addendum (IDTA).
Appropriate safeguards are used to protect your personal data during international transfers and maintain documentation of these safeguards in accordance with Article 30(2) of the GDPR.
Microsoft is certified under the EU-U.S. Data Privacy Framework, the Swiss-U.S. Data Privacy Framework, and the UK Extension to the EU-U.S. Data Privacy Framework. These certifications ensure an adequate level of data protection for international transfers.
Choosing where your text is processed. In the application you choose between two options for the text-processing step, that is where your speech-to-text results and the text you highlight for editing are processed. No option is preselected: the application asks you to choose before any text is processed in the cloud, and you can change your choice at any time in the settings.
Text processing optionA
Global (including the United States)
- Our cloud services on Microsoft Azure (Switzerland North) receive your text and forward it to OpenAI.
- OpenAI runs the AI model in the United States (contracting entity OpenAI Ireland Ltd).
- Involves international data transfers outside Switzerland, the EU, the EEA and the United Kingdom, under the safeguards described in this section.
Text processing optionB
Switzerland & EuropeZero cloud data retention
- Your text is sent to our European text-processing service hosted by Scaleway in Paris (France).
- Scaleway forwards it to the Swiss AI host PHOENIQS (Phoenix Technologies AG), where the AI model runs exclusively in Switzerland.
- Neither Microsoft nor OpenAI receives your text; it stays in Switzerland and the EU.
- Zero data retention in the cloud: your text and the result are not logged or stored in the cloud beyond the processing. Whether results are kept in the text history on your own computer is a separate, local setting that you control.
The choice covers exactly one thing: the text-processing step, that is the text you dictate or select, the instructions and writing-style examples sent with it, and the text the AI model produces for you. Everything else is the same under both options: speech recognition still runs on your computer, and account, authentication, licence and usage data are still processed on Microsoft Azure. In particular, each request under the Switzerland & Europe option still produces a usage event on Azure, used for your quota and the statistics described below; it records the time, language, model, token counts and the option used.
Data Storage and Retention by Third-Party Services:
Under text-processing option A (Global, including the United States), Microsoft Azure and OpenAI Ireland Ltd may store request data and logs for up to 30 days. This data can include:
• User ID and authentication information
• Text input and transcripts
• Text enhancement and generation results
• HTTPS request metadata (including IP address, user agent, timestamps, request headers)
• Language settings used for processing
This temporary storage is necessary for service operation, error handling, and system stability and quality assurance. After the retention period, this data is automatically deleted. Under text-processing option B (Switzerland & Europe), Scaleway and PHOENIQS apply zero data retention in the cloud to your customer content, that is the text you dictate for speech-to-text or select for text editing, and the result: our European text-processing service on Scaleway never logs or stores it, its technical logs contain no text or user identifiers and are kept for 1 day, and PHOENIQS neither logs nor stores inference traffic. Whether results are kept in the text history on your own computer is a separate, local setting that you control.
Under text-processing option A (Global, including the United States), Microsoft Azure and OpenAI Ireland Ltd may store request data and logs for up to 30 days. This data can include:
• User ID and authentication information
• Text input and transcripts
• Text enhancement and generation results
• HTTPS request metadata (including IP address, user agent, timestamps, request headers)
• Language settings used for processing
This temporary storage is necessary for service operation, error handling, and system stability and quality assurance. After the retention period, this data is automatically deleted. Under text-processing option B (Switzerland & Europe), Scaleway and PHOENIQS apply zero data retention in the cloud to your customer content, that is the text you dictate for speech-to-text or select for text editing, and the result: our European text-processing service on Scaleway never logs or stores it, its technical logs contain no text or user identifiers and are kept for 1 day, and PHOENIQS neither logs nor stores inference traffic. Whether results are kept in the text history on your own computer is a separate, local setting that you control.
Advertising on this website (only with your consent):
If you consent in the cookie banner, Google Ads cookies may be set on this website for remarketing, so that we can show you WritingAnt ads on Google Search, YouTube and the Google Display Network after your visit, and for measuring conversions. For this processing Google Ireland Ltd acts as an independent controller under its own privacy policy, including transfers to the United States under its own safeguards; it is not a sub-processor of ours. Without your consent no advertising cookies are set, and you can withdraw consent at any time in the cookie settings linked in the footer. The cookies and their lifetimes are listed in our Cookie Policy.
If you consent in the cookie banner, Google Ads cookies may be set on this website for remarketing, so that we can show you WritingAnt ads on Google Search, YouTube and the Google Display Network after your visit, and for measuring conversions. For this processing Google Ireland Ltd acts as an independent controller under its own privacy policy, including transfers to the United States under its own safeguards; it is not a sub-processor of ours. Without your consent no advertising cookies are set, and you can withdraw consent at any time in the cookie settings linked in the footer. The cookies and their lifetimes are listed in our Cookie Policy.
Highlighted User Accounts Data
We use the third-party WorkOS Inc. (US) to provide authentication and user account management. When you create or use a user account, we collect and process limited personal data needed for authentication, account management, fraud prevention, and service security.
Account data we collect:
• Full name
• Email address
• IP address
• Browser user agent
WorkOS Data Processing Addendum
• Full name
• Email address
• IP address
• Browser user agent
WorkOS Data Processing Addendum
Backups in Microsoft Azure (EU / Switzerland)
Highlighted Online Storage and Processing of Usage Data
Usage Data Collection:
We want to highlight that we especially store and process the usage data listed below, related to our speech-to-text and, text generation, and text enhancement features to manage your subscription limit usage and providing our services as well as analysis of whether the usage limits in the subscription plans are viable for future business, and other analytical evaluations for assessing our business model. We keep this data linked to your account for up to two years to evaluate usage changes over time; after that we irreversibly anonymise it by removing the link to your account and reducing the timestamp to the day, and keep only the resulting aggregate statistics for long-term business analysis. We want to avoid setting prices that are too high or too low based on these usage-driven costs. Our goal is to have a simple and clear way to communicate pricing quotas to the end user which we can achieve by analyzing the data from this two-year period.
We want to highlight that we especially store and process the usage data listed below, related to our speech-to-text and, text generation, and text enhancement features to manage your subscription limit usage and providing our services as well as analysis of whether the usage limits in the subscription plans are viable for future business, and other analytical evaluations for assessing our business model. We keep this data linked to your account for up to two years to evaluate usage changes over time; after that we irreversibly anonymise it by removing the link to your account and reducing the timestamp to the day, and keep only the resulting aggregate statistics for long-term business analysis. We want to avoid setting prices that are too high or too low based on these usage-driven costs. Our goal is to have a simple and clear way to communicate pricing quotas to the end user which we can achieve by analyzing the data from this two-year period.
Highlighted Types of Usage Data Collected:
• Email address
• Number of requests made for speech-to-text, text generation, and text enhancement features
• Time and date of each request
• Language used for processing
• Amount of requests and number of tokens consumed by third-party AI language models
• Information about which AI model was used for processing (GPT AI models under option A, the Swiss-hosted open-source AI model under option B)
• The text-processing option you chose when installing the application, under which the request was processed: option A, Global (including the United States), or option B, Switzerland & Europe
• Application version
• Operating system (Windows or Mac)
• User interface used (simplified window view or variant for inserting text into any application)
• Text result quality requested
• Result character size
• Request timing for the underlying AI service
• Situation profile (e.g., general, customer support, corporate communication, sales)
• Application startup events, including how far you progress through the startup flow, to confirm that the program launches and initializes correctly
• Whether the operating-system permissions the application asks for during setup (microphone, and on macOS accessibility and input monitoring) were granted, reported during the startup dialog and once setup completes, so we can detect installations that fail because a required permission is missing
• A randomly generated, pseudonymous launch identifier. Before you sign in, application startup and AI-model download progress events are reported with this identifier only — it is generated anew for each launch, kept solely in the program's memory, never written to your disk, and never linked to your name, email address, or user account. Because a fresh identifier is used every time, two launches cannot be connected to each other, and these events are only sent until the application has started up completely for the first time
• Which steps of the built-in learning guides (the Key Functionality Guide and Guide Level 2) you have completed, so we can see which features new users discover and improve the guides
• Whether you currently have an active subscription
• How you heard about WritingAnt (for example: from a friend, an online search, social media, or other)
• The country you selected for pricing and whether you are purchasing as a private person or as a company
• The interface language you selected in the application
• That you saved a teaching example for a custom writing style (the event only, without the text)
• A pseudonymous device identifier: a one-way hash computed on your computer from your operating system's installation identifier and your operating-system account name. We never receive those values themselves, only the hash, and we hash it again on our servers with a secret key before storing it
• A random installation identifier that the application creates on first run and keeps in your operating system's secure key store (macOS Keychain or Windows Credential Manager, entry "WritingAnt"); it contains no information about you or your computer
• Email address
• Number of requests made for speech-to-text, text generation, and text enhancement features
• Time and date of each request
• Language used for processing
• Amount of requests and number of tokens consumed by third-party AI language models
• Information about which AI model was used for processing (GPT AI models under option A, the Swiss-hosted open-source AI model under option B)
• The text-processing option you chose when installing the application, under which the request was processed: option A, Global (including the United States), or option B, Switzerland & Europe
• Application version
• Operating system (Windows or Mac)
• User interface used (simplified window view or variant for inserting text into any application)
• Text result quality requested
• Result character size
• Request timing for the underlying AI service
• Situation profile (e.g., general, customer support, corporate communication, sales)
• Application startup events, including how far you progress through the startup flow, to confirm that the program launches and initializes correctly
• Whether the operating-system permissions the application asks for during setup (microphone, and on macOS accessibility and input monitoring) were granted, reported during the startup dialog and once setup completes, so we can detect installations that fail because a required permission is missing
• A randomly generated, pseudonymous launch identifier. Before you sign in, application startup and AI-model download progress events are reported with this identifier only — it is generated anew for each launch, kept solely in the program's memory, never written to your disk, and never linked to your name, email address, or user account. Because a fresh identifier is used every time, two launches cannot be connected to each other, and these events are only sent until the application has started up completely for the first time
• Which steps of the built-in learning guides (the Key Functionality Guide and Guide Level 2) you have completed, so we can see which features new users discover and improve the guides
• Whether you currently have an active subscription
• How you heard about WritingAnt (for example: from a friend, an online search, social media, or other)
• The country you selected for pricing and whether you are purchasing as a private person or as a company
• The interface language you selected in the application
• That you saved a teaching example for a custom writing style (the event only, without the text)
• A pseudonymous device identifier: a one-way hash computed on your computer from your operating system's installation identifier and your operating-system account name. We never receive those values themselves, only the hash, and we hash it again on our servers with a secret key before storing it
• A random installation identifier that the application creates on first run and keeps in your operating system's secure key store (macOS Keychain or Windows Credential Manager, entry "WritingAnt"); it contains no information about you or your computer
Startup and Onboarding Telemetry — Purpose, Legal Basis, and Retention:
The application startup, onboarding-progress, and installation-identifier events listed above are collected so that we can confirm that installations and application launches complete successfully, diagnose startup problems across different devices and operating-system versions, and understand whether the first-run experience is intuitive so we can improve it. Where the GDPR applies, we process this data on the basis of our legitimate interest in ensuring that our software installs and runs reliably and that new users can get started without problems (Art. 6(1)(f) GDPR); under the Swiss FADP we process it in accordance with the principles of lawfulness, proportionality, and purpose limitation. You have the right to object to this processing at any time (Art. 21 GDPR) using the contact details provided in this policy. Like the other usage data in this section, these events are kept linked to your account for a maximum of two years and are then irreversibly anonymised as described above.
The application startup, onboarding-progress, and installation-identifier events listed above are collected so that we can confirm that installations and application launches complete successfully, diagnose startup problems across different devices and operating-system versions, and understand whether the first-run experience is intuitive so we can improve it. Where the GDPR applies, we process this data on the basis of our legitimate interest in ensuring that our software installs and runs reliably and that new users can get started without problems (Art. 6(1)(f) GDPR); under the Swiss FADP we process it in accordance with the principles of lawfulness, proportionality, and purpose limitation. You have the right to object to this processing at any time (Art. 21 GDPR) using the contact details provided in this policy. Like the other usage data in this section, these events are kept linked to your account for a maximum of two years and are then irreversibly anonymised as described above.
The pre-login launch identifier is anonymous in practice: it is a random value generated fresh for every launch, held only in the program's memory and never stored on your device, so neither we nor anyone else can connect two launches or trace the events back to you. The events reported with it are limited to startup milestones, the platform (Windows or macOS), the application version, and the interface language you selected, and they stop permanently once the application has completed one successful startup. We do not join or correlate these events with your user account or any other account data on our servers — not even after you sign in.
One Account per Computer — Pseudonymous Device Identifiers:
Our licence terms allow each person one free account and one account per computer. To make sure the free plan cannot be reset by signing in with a second account on the same computer, the application reports the two pseudonymous device identifiers listed above once per installation, when it signs in and registers the computer with your account. On our servers they are stored only in hashed form next to the computer registration and are used for one purpose: to recognise that more than one user account is being used from the same computer and operating-system login. The first account registered on a computer is not affected; any further account on the same computer is paused and the application asks you to contact support, who reviews the case personally before deciding, and you can contest the decision at any time. If you want to switch the account you use on a computer, for example from a personal account to one provided by your employer, email support and we make the switch for you. We process these identifiers on the basis of our legitimate interest in preventing misuse of the free plan and ensuring fair access for all users (Art. 6(1)(f) GDPR) and, under the Swiss FADP, in line with the principles of proportionality and purpose limitation. We do not use them for advertising or for tracking you across other services or websites, and we never share them with third parties. They cannot be reversed into the original values, and the server-side secret can be changed at any time to make all stored values permanently unlinkable. The identifiers are kept for as long as the computer registration they belong to is active and at most twelve months after it was last used; records of a pause are kept for up to two years after the pause was lifted; and all of it is deleted when you ask us to delete your account. You have the right to object to this processing (Art. 21 GDPR) using the contact details in this policy; because the processing exists to prevent misuse, we may continue it for the duration of your account, but we will explain our reasons and you can always close the account.
Our licence terms allow each person one free account and one account per computer. To make sure the free plan cannot be reset by signing in with a second account on the same computer, the application reports the two pseudonymous device identifiers listed above once per installation, when it signs in and registers the computer with your account. On our servers they are stored only in hashed form next to the computer registration and are used for one purpose: to recognise that more than one user account is being used from the same computer and operating-system login. The first account registered on a computer is not affected; any further account on the same computer is paused and the application asks you to contact support, who reviews the case personally before deciding, and you can contest the decision at any time. If you want to switch the account you use on a computer, for example from a personal account to one provided by your employer, email support and we make the switch for you. We process these identifiers on the basis of our legitimate interest in preventing misuse of the free plan and ensuring fair access for all users (Art. 6(1)(f) GDPR) and, under the Swiss FADP, in line with the principles of proportionality and purpose limitation. We do not use them for advertising or for tracking you across other services or websites, and we never share them with third parties. They cannot be reversed into the original values, and the server-side secret can be changed at any time to make all stored values permanently unlinkable. The identifiers are kept for as long as the computer registration they belong to is active and at most twelve months after it was last used; records of a pause are kept for up to two years after the pause was lifted; and all of it is deleted when you ask us to delete your account. You have the right to object to this processing (Art. 21 GDPR) using the contact details in this policy; because the processing exists to prevent misuse, we may continue it for the duration of your account, but we will explain our reasons and you can always close the account.
Local Data Storage: User session auth data and optional personal data for voice command actions
Keyword-Trigger Features:
When you use the optional keyword-trigger features in the installed desktop application that start with "private" (e.g., "private address" or "private first name"), you must first save this private data in the App Settings. This data is subject to the local processing and encryption measures described below.
When you use the optional keyword-trigger features in the installed desktop application that start with "private" (e.g., "private address" or "private first name"), you must first save this private data in the App Settings. This data is subject to the local processing and encryption measures described below.
Local-Only Storage:
We store this kind of data strictly on your device and never transmit or retain it on our servers. All keyword-trigger data remains exclusively on your local machine.
We store this kind of data strictly on your device and never transmit or retain it on our servers. All keyword-trigger data remains exclusively on your local machine.
Encryption at Rest:
Your settings and personal data are encrypted at rest using a industry-standard encryption algorithm (AES with HMAC authentication) to ensure that this data can only be accessed and decrypted on your specific device. The encryption key is derived locally, and never transmitted or stored on our servers.
Your settings and personal data are encrypted at rest using a industry-standard encryption algorithm (AES with HMAC authentication) to ensure that this data can only be accessed and decrypted on your specific device. The encryption key is derived locally, and never transmitted or stored on our servers.
Memory Processing:
Data is decrypted in memory and then inserted into the input field where you placed your cursor/caret at the time of use.
Data is decrypted in memory and then inserted into the input field where you placed your cursor/caret at the time of use.
User Control:
You retain full control over your data—you can delete or clear the local cache at any time via the App Settings.
You retain full control over your data—you can delete or clear the local cache at any time via the App Settings.
Encrypted Credential Storage:
Your user credentials are stored in encrypted form on your computer to enable easier login in the future. This encrypted storage uses industry-standard encryption algorithms (AES with HMAC authentication) to ensure that only your device can access and decrypt these credentials. The encryption keys are derived locally and never transmitted to our servers, maintaining the security and privacy of your authentication information.
Your user credentials are stored in encrypted form on your computer to enable easier login in the future. This encrypted storage uses industry-standard encryption algorithms (AES with HMAC authentication) to ensure that only your device can access and decrypt these credentials. The encryption keys are derived locally and never transmitted to our servers, maintaining the security and privacy of your authentication information.
Where data is stored on your device:
Settings and the encrypted cache are kept under the OS “user data” folder. Typical paths:
Settings and the encrypted cache are kept under the OS “user data” folder. Typical paths:
Windows: %LOCALAPPDATA%\OegrenDigital\SpeechToWellWrittenTextAssistantmacOS: ~/Library/Application Support/SpeechToWellWrittenTextAssistantFolders Created on Your Computer:
The desktop application and its helper processes (the launcher, the overlay user interface, and the local speech-recognition subprocesses) create the folders and entries listed below on your computer. Data described as encrypted is encrypted at rest using an AES-based algorithm; the encryption key is stored in the operating system's secure key store (macOS Keychain or Windows Credential Manager, entry name "WritingAnt") and never leaves your device.
The desktop application and its helper processes (the launcher, the overlay user interface, and the local speech-recognition subprocesses) create the folders and entries listed below on your computer. Data described as encrypted is encrypted at rest using an AES-based algorithm; the encryption key is stored in the operating system's secure key store (macOS Keychain or Windows Credential Manager, entry name "WritingAnt") and never leaves your device.
Main data folder:
This folder contains:
• Encrypted files: settings.json (application settings), credentials.json (login session), history.json (dictation history and results), magic_snippets.json (personal snippets), custom_app_launchers.json (custom voice commands), custom_writing_styles (one file per custom writing style), writing_styles_setup.json, feature_settings_v2.json and feature_settings_v3.json (feature preferences)
• audio_recordings — optionally saved audio recordings, stored encrypted (*.enc.wav); the subfolder audio_recordings/exported holds temporarily decrypted exports and is emptied automatically at the next application start
• ai_models — downloaded AI transcription models (not encrypted; may be deleted at any time to free disk space, the application offers to download the models again when needed)
• CrashLogs — crash and diagnostic reports (not encrypted; they contain technical information, not your recorded audio or dictated text)
• logs — application log files (not encrypted)
• launcher_status.json (application startup progress) and tokens.json (non-sensitive login metadata) — not encrypted
• development — a subfolder with the same structure that is only used by development builds of the application
macOS: ~/Library/Application Support/SpeechToWellWrittenTextAssistantWindows: %LOCALAPPDATA%\OegrenDigital\SpeechToWellWrittenTextAssistantThis folder contains:
• Encrypted files: settings.json (application settings), credentials.json (login session), history.json (dictation history and results), magic_snippets.json (personal snippets), custom_app_launchers.json (custom voice commands), custom_writing_styles (one file per custom writing style), writing_styles_setup.json, feature_settings_v2.json and feature_settings_v3.json (feature preferences)
• audio_recordings — optionally saved audio recordings, stored encrypted (*.enc.wav); the subfolder audio_recordings/exported holds temporarily decrypted exports and is emptied automatically at the next application start
• ai_models — downloaded AI transcription models (not encrypted; may be deleted at any time to free disk space, the application offers to download the models again when needed)
• CrashLogs — crash and diagnostic reports (not encrypted; they contain technical information, not your recorded audio or dictated text)
• logs — application log files (not encrypted)
• launcher_status.json (application startup progress) and tokens.json (non-sensitive login metadata) — not encrypted
• development — a subfolder with the same structure that is only used by development builds of the application
Additional folders and entries:
On macOS:
• ~/Library/Application Support/writing-ant and ~/Library/Application Support/writing-ant-overlay — framework caches of the application windows (Chromium/Electron caches, local storage, cookies); no user documents are stored here
• ~/Library/Logs/WritingAnt Overlay — log folder of the overlay user interface (normally empty)
• ~/Library/Preferences/com.writingant.app.plist and ~/Library/Preferences/com.oegren-digital.writing-ant-frontend.plist — small preference files (window and overlay position)
• macOS Keychain — an entry named "WritingAnt" holding the local encryption key and the random installation identifier described in the usage-data section
On Windows:
• %APPDATA%\writing-ant and %APPDATA%\writing-ant-overlay — framework caches of the application windows (Chromium/Electron caches, local storage, cookies); no user documents are stored here
• %LOCALAPPDATA%\Oden — state of the native overlay user interface (overlay position and dismissed update notifications)
• Windows Credential Manager — an entry named "WritingAnt" holding the local encryption key and the random installation identifier described in the usage-data section
• Registry value HKCU\Software\WritingAnt\InstalledFrom — written only by Microsoft Store installations and removed when the application is uninstalled
On macOS:
• ~/Library/Application Support/writing-ant and ~/Library/Application Support/writing-ant-overlay — framework caches of the application windows (Chromium/Electron caches, local storage, cookies); no user documents are stored here
• ~/Library/Logs/WritingAnt Overlay — log folder of the overlay user interface (normally empty)
• ~/Library/Preferences/com.writingant.app.plist and ~/Library/Preferences/com.oegren-digital.writing-ant-frontend.plist — small preference files (window and overlay position)
• macOS Keychain — an entry named "WritingAnt" holding the local encryption key and the random installation identifier described in the usage-data section
On Windows:
• %APPDATA%\writing-ant and %APPDATA%\writing-ant-overlay — framework caches of the application windows (Chromium/Electron caches, local storage, cookies); no user documents are stored here
• %LOCALAPPDATA%\Oden — state of the native overlay user interface (overlay position and dismissed update notifications)
• Windows Credential Manager — an entry named "WritingAnt" holding the local encryption key and the random installation identifier described in the usage-data section
• Registry value HKCU\Software\WritingAnt\InstalledFrom — written only by Microsoft Store installations and removed when the application is uninstalled
On both operating systems the application additionally uses the system's temporary folder for an instance lock file (writing_ant_main.lock) and for short-lived audio buffers during transcription; these temporary files are removed automatically.
If the ai_models folder is deleted, the AI models are simply downloaded again on demand.
Removing Local Data:
Uninstalling the application does not by itself delete the data listed above. On Windows, the uninstaller asks whether this data should be deleted as well; a silent uninstall keeps it unless the /REMOVEDATA=1 switch is used. On both operating systems, Help → Privacy → "Remove local data" inside the application deletes all folders and files listed above and then closes the application; you can also delete the folders yourself. On macOS the application itself is removed by moving it from the Applications folder to the Trash. Two things remain on the computer in every case: the Keychain or Credential Manager entries named "WritingAnt" (the local encryption key and the random installation identifier, which contain no personal data) and the system permissions you granted to the application, which you can revoke in the system settings.
Uninstalling the application does not by itself delete the data listed above. On Windows, the uninstaller asks whether this data should be deleted as well; a silent uninstall keeps it unless the /REMOVEDATA=1 switch is used. On both operating systems, Help → Privacy → "Remove local data" inside the application deletes all folders and files listed above and then closes the application; you can also delete the folders yourself. On macOS the application itself is removed by moving it from the Applications folder to the Trash. Two things remain on the computer in every case: the Keychain or Credential Manager entries named "WritingAnt" (the local encryption key and the random installation identifier, which contain no personal data) and the system permissions you granted to the application, which you can revoke in the system settings.
Deleting local data on your computer does not delete your account or the data stored under it on our servers; see "User Account Data Retention" below for how to request account deletion.
Keyboard Shortcuts, Mouse Buttons, and Input Monitoring
Optional Keyboard Shortcuts:
If you enable keyboard shortcuts in Settings (for example, to start or stop recordings for writing sessions — including double-press shortcuts, combination shortcuts such as a modifier key plus a letter or punctuation key, and, on Mac, the Globe (fn) key), the application observes keyboard events system-wide, even while you are using other applications. This observation is not limited to the designated shortcut combinations: while any keyboard shortcut is enabled, the application sees which keys are pressed, because combination shortcuts can only be detected that way, and because the application must recognize ordinary commands (for example copy-and-paste shortcuts) so that they never falsely trigger a writing session. Every keyboard event is evaluated in the moment against your configured shortcuts and then discarded: keystrokes are never logged, stored, or transmitted, and the application never reconstructs the text you type. Key presses that match an enabled shortcut are consumed by the application; all other keystrokes pass through to your applications unchanged. While no keyboard shortcut is enabled, this monitoring does not run at all.
If you enable keyboard shortcuts in Settings (for example, to start or stop recordings for writing sessions — including double-press shortcuts, combination shortcuts such as a modifier key plus a letter or punctuation key, and, on Mac, the Globe (fn) key), the application observes keyboard events system-wide, even while you are using other applications. This observation is not limited to the designated shortcut combinations: while any keyboard shortcut is enabled, the application sees which keys are pressed, because combination shortcuts can only be detected that way, and because the application must recognize ordinary commands (for example copy-and-paste shortcuts) so that they never falsely trigger a writing session. Every keyboard event is evaluated in the moment against your configured shortcuts and then discarded: keystrokes are never logged, stored, or transmitted, and the application never reconstructs the text you type. Key presses that match an enabled shortcut are consumed by the application; all other keystrokes pass through to your applications unchanged. While no keyboard shortcut is enabled, this monitoring does not run at all.
Optional Mouse-Button Triggers:
You can optionally assign spare mouse buttons (such as the side or wheel buttons) as triggers for writing sessions. While a mouse-button trigger is assigned, the application listens for presses of the middle and additional (side) mouse buttons, even while you are using other applications. On macOS, ordinary left and right clicks and pointer movement are excluded at the operating-system level and never reach the application; on Windows, the system-provided hook technically routes all mouse events past the application, but anything other than a middle- or side-button press is passed on immediately without being examined. Presses of a button you have assigned are handled by the application instead of being passed to other programs, so that button can no longer trigger its original function while the application is running; presses of spare buttons you have not assigned are received but ignored and passed through unchanged. The application does not record or transmit your mouse activity; button presses are used in the moment, solely to start or stop the action you assigned. While no mouse-button trigger is assigned, this monitoring does not run at all.
You can optionally assign spare mouse buttons (such as the side or wheel buttons) as triggers for writing sessions. While a mouse-button trigger is assigned, the application listens for presses of the middle and additional (side) mouse buttons, even while you are using other applications. On macOS, ordinary left and right clicks and pointer movement are excluded at the operating-system level and never reach the application; on Windows, the system-provided hook technically routes all mouse events past the application, but anything other than a middle- or side-button press is passed on immediately without being examined. Presses of a button you have assigned are handled by the application instead of being passed to other programs, so that button can no longer trigger its original function while the application is running; presses of spare buttons you have not assigned are received but ignored and passed through unchanged. The application does not record or transmit your mouse activity; button presses are used in the moment, solely to start or stop the action you assigned. While no mouse-button trigger is assigned, this monitoring does not run at all.
Mac Users - Additional Permission Required:
On macOS, the system requires you to grant additional permission in System Settings (Accessibility, or Input Monitoring) to allow the application to detect these triggers. The application will guide you to enable the permission when you first set up a keyboard or mouse-button trigger.
On macOS, the system requires you to grant additional permission in System Settings (Accessibility, or Input Monitoring) to allow the application to detect these triggers. The application will guide you to enable the permission when you first set up a keyboard or mouse-button trigger.
Alternatives to Keyboard and Mouse Triggers:
You can use the application without enabling keyboard shortcuts or mouse-button triggers. Alternative control methods include using voice commands or starting and stopping writing sessions by clicking buttons in the application window.
You can use the application without enabling keyboard shortcuts or mouse-button triggers. Alternative control methods include using voice commands or starting and stopping writing sessions by clicking buttons in the application window.
Application Aware Preset Switching
What it detects:
If you turn on the optional Application Aware feature and configure mappings, the application reads the name of the currently active application and, only for the browser rules you create, the web address of the active browser tab. On Windows this is done via standard Windows APIs and Windows' built-in accessibility interface (UI Automation); on macOS via Apple's system interfaces. This is used solely to apply the language and writing-style preset you chose for that app or website. Page contents and password fields are never read.
If you turn on the optional Application Aware feature and configure mappings, the application reads the name of the currently active application and, only for the browser rules you create, the web address of the active browser tab. On Windows this is done via standard Windows APIs and Windows' built-in accessibility interface (UI Automation); on macOS via Apple's system interfaces. This is used solely to apply the language and writing-style preset you chose for that app or website. Page contents and password fields are never read.
Processed locally, never transmitted:
This detection happens entirely on your device. Application names and browser tab addresses are used in the moment to switch your preset and are never stored beyond your own settings, and never transmitted to our servers or any third party.
This detection happens entirely on your device. Application names and browser tab addresses are used in the moment to switch your preset and are never stored beyond your own settings, and never transmitted to our servers or any third party.
Optional and off by default:
Application Aware is turned off by default and must be explicitly enabled in Settings, where you configure every mapping yourself. While the feature is off, the application never checks which application or website is active — no such detection runs on your computer at all.
Application Aware is turned off by default and must be explicitly enabled in Settings, where you configure every mapping yourself. While the feature is off, the application never checks which application or website is active — no such detection runs on your computer at all.
Connectivity Checks
What the application does:
To distinguish a lost internet connection from a problem with our service, and to show you an accurate “no internet” notice, the application periodically sends a small reachability request (an HTTP request expecting a fixed, content-free reply) to one or more of the following public connectivity-check endpoints: connectivitycheck.gstatic.com (Google), cp.cloudflare.com (Cloudflare) and captive.apple.com (Apple). These are the same endpoints that Windows, macOS, Android and Chrome use to detect captive portals. The checks run about every two seconds while a writing session is active or the connection appears unstable, and about every 30 seconds while the application is idle.
To distinguish a lost internet connection from a problem with our service, and to show you an accurate “no internet” notice, the application periodically sends a small reachability request (an HTTP request expecting a fixed, content-free reply) to one or more of the following public connectivity-check endpoints: connectivitycheck.gstatic.com (Google), cp.cloudflare.com (Cloudflare) and captive.apple.com (Apple). These are the same endpoints that Windows, macOS, Android and Chrome use to detect captive portals. The checks run about every two seconds while a writing session is active or the connection appears unstable, and about every 30 seconds while the application is idle.
What these endpoints receive:
Each request discloses your IP address and a generic identifier of the application (“WritingAnt-connectivity”) to the operator of the endpoint, which is technically unavoidable for any internet request. No account data, cookies, audio, text or other content is included, and we receive nothing about you from these operators. Google, Cloudflare and Apple act as independent controllers for any logs they keep of such requests, under their own privacy policies; they are not sub-processors of ours and do not process data on our behalf.
Each request discloses your IP address and a generic identifier of the application (“WritingAnt-connectivity”) to the operator of the endpoint, which is technically unavoidable for any internet request. No account data, cookies, audio, text or other content is included, and we receive nothing about you from these operators. Google, Cloudflare and Apple act as independent controllers for any logs they keep of such requests, under their own privacy policies; they are not sub-processors of ours and do not process data on our behalf.
Legal basis:
Where the GDPR applies, we rely on our legitimate interest in keeping the application reliable and in giving you accurate information about its connection status (Art. 6(1)(f) GDPR); under the Swiss FADP we process this data in accordance with the principles of lawfulness, proportionality and purpose limitation. The checks are a technical requirement for operating the application and cannot be switched off separately.
Where the GDPR applies, we rely on our legitimate interest in keeping the application reliable and in giving you accurate information about its connection status (Art. 6(1)(f) GDPR); under the Swiss FADP we process this data in accordance with the principles of lawfulness, proportionality and purpose limitation. The checks are a technical requirement for operating the application and cannot be switched off separately.
Clipboard-Based Text Processing
Selected Text Capture via Clipboard:
When you use the correct voice command, keyboard shortcut, or another trigger you have configured (such as an assigned mouse button or, on Mac, the Globe (fn) key), the Software will take the text you have selected in an application and automatically copy it to the operating system clipboard. The Software then reads this text from the clipboard and sends it to our cloud services for further processing, such as text enhancement or rewriting.
When you use the correct voice command, keyboard shortcut, or another trigger you have configured (such as an assigned mouse button or, on Mac, the Globe (fn) key), the Software will take the text you have selected in an application and automatically copy it to the operating system clipboard. The Software then reads this text from the clipboard and sends it to our cloud services for further processing, such as text enhancement or rewriting.
Similarity to Recording-Based Processing:
This feature works similarly to making a recording to capture text as a basis for further editing. The difference is that instead of recording speech, you select existing text. The same cloud processing, third-party AI services, and data handling practices described elsewhere in this Privacy Policy apply to this clipboard-based text processing.
This feature works similarly to making a recording to capture text as a basis for further editing. The difference is that instead of recording speech, you select existing text. The same cloud processing, third-party AI services, and data handling practices described elsewhere in this Privacy Policy apply to this clipboard-based text processing.
Automatic Pasting of Processed Result:
After processing, the system will automatically paste the result through your operating system. If the text is still selected in a third-party application, it will be replaced with the processed result. The processed text passes through the operating system clipboard during this operation.
After processing, the system will automatically paste the result through your operating system. If the text is still selected in a third-party application, it will be replaced with the processed result. The processed text passes through the operating system clipboard during this operation.
Clipboard Restoration (Processed Locally):
By default, immediately before the Software inserts text for you (for example a dictation result or a processed text), it briefly reads the content currently on your operating system clipboard — which may include text, formatting, or an image you copied earlier — solely in order to put that content back on the clipboard shortly after the insertion. This snapshot is held only temporarily in the application's memory on your device; it is never written to disk, never used for any other purpose, and never transmitted to our servers or to any third party. It is discarded as soon as the restoration has been performed or abandoned. Restoration works on a best-effort basis and may not succeed for every content type (for example, copied files cannot be restored). If you prefer that the most recently inserted result stays on the clipboard so you can paste it again elsewhere, you can turn restoration off in the application settings; in that case the clipboard is not read before insertions.
By default, immediately before the Software inserts text for you (for example a dictation result or a processed text), it briefly reads the content currently on your operating system clipboard — which may include text, formatting, or an image you copied earlier — solely in order to put that content back on the clipboard shortly after the insertion. This snapshot is held only temporarily in the application's memory on your device; it is never written to disk, never used for any other purpose, and never transmitted to our servers or to any third party. It is discarded as soon as the restoration has been performed or abandoned. Restoration works on a best-effort basis and may not succeed for every content type (for example, copied files cannot be restored). If you prefer that the most recently inserted result stays on the clipboard so you can paste it again elsewhere, you can turn restoration off in the application settings; in that case the clipboard is not read before insertions.
User Control:
This clipboard-based text processing only occurs when you actively trigger it via the designated voice command, keyboard shortcut, or another trigger you have configured (such as an assigned mouse button). Apart from the insertion-time restoration snapshot described above — which likewise happens only as part of an action you triggered — the Software does not monitor or access your clipboard at any other time.
This clipboard-based text processing only occurs when you actively trigger it via the designated voice command, keyboard shortcut, or another trigger you have configured (such as an assigned mouse button). Apart from the insertion-time restoration snapshot described above — which likewise happens only as part of an action you triggered — the Software does not monitor or access your clipboard at any other time.
Local Storage of Audio Recordings and Results
Temporary Audio Storage During Processing:
Transcription is the process of converting speech audio to text out of that speech, which happens locally on the user's computer. In some situations the transcription takes place fully in memory and sometimes a temporary file is stored, depending on which AI model framework is used and if storing a temporary audio file is necessary or not. Audio recordings are stored unencrypted temporary during transcription and are automatically removed by default after the transcription has succeded. You can also choose to store the recordings on disk for longer if you want, as described below.
Transcription is the process of converting speech audio to text out of that speech, which happens locally on the user's computer. In some situations the transcription takes place fully in memory and sometimes a temporary file is stored, depending on which AI model framework is used and if storing a temporary audio file is necessary or not. Audio recordings are stored unencrypted temporary during transcription and are automatically removed by default after the transcription has succeded. You can also choose to store the recordings on disk for longer if you want, as described below.
Optional Local Storage:
You have the option to save the results of text enhancements, speech-to-text conversions / text generation / text enhancements (offline and online requests), and audio recordings locally on your computer. This is an optional feature that you can choose to enable or disable.
You have the option to save the results of text enhancements, speech-to-text conversions / text generation / text enhancements (offline and online requests), and audio recordings locally on your computer. This is an optional feature that you can choose to enable or disable.
Storage Security:
All locally stored files, including audio recordings and processing results, are encrypted using industry-standard encryption algorithm (AES with HMAC authentication) to ensure that this data can only be accessed and decrypted on your specific device. The encryption key is derived locally, and never transmitted or stored on our servers.
All locally stored files, including audio recordings and processing results, are encrypted using industry-standard encryption algorithm (AES with HMAC authentication) to ensure that this data can only be accessed and decrypted on your specific device. The encryption key is derived locally, and never transmitted or stored on our servers.
User-Controlled Duration:
The duration of local storage is entirely under your control and can be configured in the application settings. You can choose how long to keep files locally and delete them at any time.
The duration of local storage is entirely under your control and can be configured in the application settings. You can choose how long to keep files locally and delete them at any time.
Data Storage and Retention for Bookkeeping Purposes
Swiss Legal Requirements:
As a company based in Switzerland, we are required by Swiss law to maintain certain business records for bookkeeping and tax purposes. We store the following data for compliance with these legal obligations:
As a company based in Switzerland, we are required by Swiss law to maintain certain business records for bookkeeping and tax purposes. We store the following data for compliance with these legal obligations:
Data Types Retained for Bookkeeping:
• Email address
• Subscription tier purchases
• Name and billing address information
• Potentially VAT ID
• Payment method data (payment processor references)
• Email address
• Subscription tier purchases
• Name and billing address information
• Potentially VAT ID
• Payment method data (payment processor references)
Retention Period:
This bookkeeping data is retained for 10 years from the end of the fiscal year in which the transaction occurred, as required by Swiss commercial and tax law.
This bookkeeping data is retained for 10 years from the end of the fiscal year in which the transaction occurred, as required by Swiss commercial and tax law.
Legal Basis:
This data retention is based on our legal obligations under Swiss law, including the Swiss Code of Obligations (CO) and Swiss tax regulations. This constitutes a legitimate interest that overrides individual data deletion requests for this specific category of data during the retention period. We store and potentially share bookkeeping data and invoices with authorities in order to comply with applicable Swiss and EU legal requirements related to financial record-keeping, audit, registrations, and statutory obligations. Payments you make by bank transfer are received by our bank, UBS Switzerland AG, which processes the payer data under its own responsibility as an independent controller (privacy notice at ubs.com/privacy); it is therefore not a sub-processor.
This data retention is based on our legal obligations under Swiss law, including the Swiss Code of Obligations (CO) and Swiss tax regulations. This constitutes a legitimate interest that overrides individual data deletion requests for this specific category of data during the retention period. We store and potentially share bookkeeping data and invoices with authorities in order to comply with applicable Swiss and EU legal requirements related to financial record-keeping, audit, registrations, and statutory obligations. Payments you make by bank transfer are received by our bank, UBS Switzerland AG, which processes the payer data under its own responsibility as an independent controller (privacy notice at ubs.com/privacy); it is therefore not a sub-processor.
Data Security:
All bookkeeping data is stored securely with appropriate technical and organizational measures to prevent unauthorized access, modification, or disclosure. Access is restricted to authorized personnel who require this information for legitimate business purposes.
All bookkeeping data is stored securely with appropriate technical and organizational measures to prevent unauthorized access, modification, or disclosure. Access is restricted to authorized personnel who require this information for legitimate business purposes.
User Account Data Retention
Account Deletion on Request:
Account deletion is currently handled manually on request. Email support@writing-ant.com from the address linked to your account, and we delete your account and the data associated with it within 30 days of your request. Self-service deletion inside the application or on this website is not available yet; this section will be updated when it is. Deleting the application's local data on your computer (Help → Privacy → "Remove local data") is a separate step that does not delete your account, and account deletion does not remove data stored on your computer.
Account deletion is currently handled manually on request. Email support@writing-ant.com from the address linked to your account, and we delete your account and the data associated with it within 30 days of your request. Self-service deletion inside the application or on this website is not available yet; this section will be updated when it is. Deleting the application's local data on your computer (Help → Privacy → "Remove local data") is a separate step that does not delete your account, and account deletion does not remove data stored on your computer.
Subscription Cancellation:
If you cancel your subscription, your account remains active until the end of the current subscription period and then continues as a free account. It is not deleted automatically. If you no longer want an account, request deletion as described above.
If you cancel your subscription, your account remains active until the end of the current subscription period and then continues as a free account. It is not deleted automatically. If you no longer want an account, request deletion as described above.
Withdrawing a Deletion Request:
You can withdraw a deletion request at any time before we have carried it out, and your account then stays as it is. Once the deletion has been carried out, your account data is permanently deleted and cannot be recovered.
You can withdraw a deletion request at any time before we have carried it out, and your account then stays as it is. Once the deletion has been carried out, your account data is permanently deleted and cannot be recovered.
Exception for Legal Requirements:
Please note that certain data may be retained longer if required by law, such as the bookkeeping data described in the previous section, which is subject to separate legal retention requirements.
Please note that certain data may be retained longer if required by law, such as the bookkeeping data described in the previous section, which is subject to separate legal retention requirements.
Support and Sales Communication: Channels and Retention
Channels we use:
Support and sales conversations take place by email, through Microsoft Teams, by phone, through WhatsApp and through LinkedIn messaging. Usually you reach us first and we reply on the channel you used; sometimes we reach out to you, as described further down. In each case we process your contact details (name, email address, phone number or profile), the content of the conversation and its timestamps, in order to answer your request, to prepare or perform a contract with you and to follow up on it (Art. 6(1)(b) GDPR), or on the basis of our legitimate interest in running customer support and sales (Art. 6(1)(f) GDPR). WhatsApp is operated by Meta Platforms Ireland Ltd and LinkedIn by LinkedIn Ireland Unlimited Company; each processes the data exchanged on its platform under its own responsibility and privacy policy, including transfers to the United States under its own safeguards, and neither is a sub-processor of ours. Email and Microsoft Teams, by contrast, are hosted for us by Microsoft (Microsoft 365), which acts as our sub-processor and is listed in the sub-processor table above; notes from phone calls are kept there as well, and calls are not recorded. WhatsApp on our device has no access to the device's address book, so your phone number is not shared with Meta through WhatsApp's contact-upload function. If we save your number as a contact within WhatsApp in order to answer you on the channel you chose (our legitimate interest, Art. 6(1)(f) GDPR), WhatsApp stores that entry on Meta's servers in encrypted form; tell us if you prefer that we do not save it. We may also be the one who reaches out: by email, on LinkedIn or, if you gave us your number for that purpose, on WhatsApp, for example to follow up on a conversation, a download or a trial, to answer an enquiry you made elsewhere, or to introduce WritingAnt to you where your public professional role suggests a genuine interest. For such individual outreach we use contact details you published yourself (for example a LinkedIn profile or company website) or gave us (at an event, through a referral, on our website or in the application), on the basis of our legitimate interest in sales and customer care (Art. 6(1)(f) GDPR). We do not send bulk advertising messages without your consent. We do keep a simple record of the people we have contacted or spoken with (name, company, LinkedIn profile or email address, date, the messages we sent or drafted, outcome and any objection), so that we do not contact anyone twice and can honour objections; this record is used only to plan, carry out and follow up our individual outreach and to honour objections, never for bulk mailings, and is kept for the same period as support and sales correspondence. Postal advertising to companies is different: Swiss law permits addressed business mailings without prior consent, so we may send such mailings to companies in Switzerland at business addresses taken from public sources (commercial register, company websites, directories) and keep a mailing record for them (company, address, named contact where applicable, date and content of the mailing, and any objection) in order to plan the mailings and to honour objections. A company that does not wish to receive mail from us can tell us at any time and is then excluded. You can object to outreach at any time, by replying or by writing to info@oegren-digital.ch; we then stop and note the objection. You can also ask us at any time to continue a conversation by email instead. The retention periods below apply to all of these channels alike. One exception: a transcript or a text that WritingAnt produced for you (for example a transcript that came out wrong), and any other material you share so that we can resolve your request, such as screenshots of other applications, log files or a saved recording, should be sent to us by email or Microsoft Teams only. If you send such material over WhatsApp or LinkedIn anyway, we use it solely to resolve your request and delete it from the conversation once the request is closed, instead of keeping it for the periods below; the conversation itself, such as your question and our answer, is kept as described below. A recording you share with us in a support request, for example to show a recognition problem, is used only to resolve that request and is never passed on to the AI providers. For business customers this is also set out in our Data Processing Agreement.
Support and sales conversations take place by email, through Microsoft Teams, by phone, through WhatsApp and through LinkedIn messaging. Usually you reach us first and we reply on the channel you used; sometimes we reach out to you, as described further down. In each case we process your contact details (name, email address, phone number or profile), the content of the conversation and its timestamps, in order to answer your request, to prepare or perform a contract with you and to follow up on it (Art. 6(1)(b) GDPR), or on the basis of our legitimate interest in running customer support and sales (Art. 6(1)(f) GDPR). WhatsApp is operated by Meta Platforms Ireland Ltd and LinkedIn by LinkedIn Ireland Unlimited Company; each processes the data exchanged on its platform under its own responsibility and privacy policy, including transfers to the United States under its own safeguards, and neither is a sub-processor of ours. Email and Microsoft Teams, by contrast, are hosted for us by Microsoft (Microsoft 365), which acts as our sub-processor and is listed in the sub-processor table above; notes from phone calls are kept there as well, and calls are not recorded. WhatsApp on our device has no access to the device's address book, so your phone number is not shared with Meta through WhatsApp's contact-upload function. If we save your number as a contact within WhatsApp in order to answer you on the channel you chose (our legitimate interest, Art. 6(1)(f) GDPR), WhatsApp stores that entry on Meta's servers in encrypted form; tell us if you prefer that we do not save it. We may also be the one who reaches out: by email, on LinkedIn or, if you gave us your number for that purpose, on WhatsApp, for example to follow up on a conversation, a download or a trial, to answer an enquiry you made elsewhere, or to introduce WritingAnt to you where your public professional role suggests a genuine interest. For such individual outreach we use contact details you published yourself (for example a LinkedIn profile or company website) or gave us (at an event, through a referral, on our website or in the application), on the basis of our legitimate interest in sales and customer care (Art. 6(1)(f) GDPR). We do not send bulk advertising messages without your consent. We do keep a simple record of the people we have contacted or spoken with (name, company, LinkedIn profile or email address, date, the messages we sent or drafted, outcome and any objection), so that we do not contact anyone twice and can honour objections; this record is used only to plan, carry out and follow up our individual outreach and to honour objections, never for bulk mailings, and is kept for the same period as support and sales correspondence. Postal advertising to companies is different: Swiss law permits addressed business mailings without prior consent, so we may send such mailings to companies in Switzerland at business addresses taken from public sources (commercial register, company websites, directories) and keep a mailing record for them (company, address, named contact where applicable, date and content of the mailing, and any objection) in order to plan the mailings and to honour objections. A company that does not wish to receive mail from us can tell us at any time and is then excluded. You can object to outreach at any time, by replying or by writing to info@oegren-digital.ch; we then stop and note the objection. You can also ask us at any time to continue a conversation by email instead. The retention periods below apply to all of these channels alike. One exception: a transcript or a text that WritingAnt produced for you (for example a transcript that came out wrong), and any other material you share so that we can resolve your request, such as screenshots of other applications, log files or a saved recording, should be sent to us by email or Microsoft Teams only. If you send such material over WhatsApp or LinkedIn anyway, we use it solely to resolve your request and delete it from the conversation once the request is closed, instead of keeping it for the periods below; the conversation itself, such as your question and our answer, is kept as described below. A recording you share with us in a support request, for example to show a recognition problem, is used only to resolve that request and is never passed on to the AI providers. For business customers this is also set out in our Data Processing Agreement.
Retention Periods:
We retain customer support-related email and Microsoft Teams communications (error reports, information inquiries, troubleshooting, and non-contractual sales discussions) for up to 3 years after the conclusion of the support interaction. This period allows us to provide ongoing customer service, reference past issues, and ensure quality assurance.
We retain customer support-related email and Microsoft Teams communications (error reports, information inquiries, troubleshooting, and non-contractual sales discussions) for up to 3 years after the conclusion of the support interaction. This period allows us to provide ongoing customer service, reference past issues, and ensure quality assurance.
Emails that contain or reference invoices, contracts, billing, or other financial or legal documentation are retained for up to 10 years, in order to comply with applicable Swiss and EU legal requirements related to financial record-keeping, audit, and statutory obligations.
At the end of the respective retention periods, we permanently delete or irreversibly anonymize the emails, unless a longer retention is required by law, or unless you request otherwise and it is legally permissible.
Consent & Agreement Records Retention
Cookie and consent banner acceptance:
We store records of your consent—including timestamp, method, version of consent options, and your browser/session identifier—for up to 12 months. After that, we will request renewal to ensure continued valid and informed consent.
We store records of your consent—including timestamp, method, version of consent options, and your browser/session identifier—for up to 12 months. After that, we will request renewal to ensure continued valid and informed consent.
Acceptance of policies and EULA/T&C documents:
When you accept our Privacy Policy, End User License Agreement, Terms of Service, or similar legal documents during signup, we keep a record of the version accepted and date of acceptance for as long as your account remains active, and for an additional 3 months following account deletion related to last day of canceled subscription period. This ensures we can reference these agreements in case of disputes or audit.
When you accept our Privacy Policy, End User License Agreement, Terms of Service, or similar legal documents during signup, we keep a record of the version accepted and date of acceptance for as long as your account remains active, and for an additional 3 months following account deletion related to last day of canceled subscription period. This ensures we can reference these agreements in case of disputes or audit.
At the end of these periods, we delete or irreversibly anonymise records unless continued retention is required by law.
Children's Data Protection
Our services are not directed at children and we do not knowingly collect, use or process personal data from children. If we become aware that we have inadvertently collected personal data from a child without appropriate consent, we will take steps to delete such data as soon as possible. If you are a parent or a guardian and believe that your child has provided us with their personal information without your consent, please contact us at patric@oegren-digital.ch so that we can take appropriate action.
Main Privacy Policy
Below is our main privacy policy
Our Privacy Policy is managed through Iubenda to help ensure compliance with privacy regulations.
Last Updated: 5th November 2026
Swiss Representative
For Swiss Data Protection MattersUnder Article 14 of the FADP, we have appointed a Swiss Representative to act as our data protection agent.
Company Name:
ALTRION Sagl
ALTRION Sagl
Phone:
+41 78 229 72 57
+41 78 229 72 57
Address:
Via Luigi Lavizzari 8
6850 Mendrisio
Switzerland
Via Luigi Lavizzari 8
6850 Mendrisio
Switzerland
EU GDPR Representative
For EU Data Protection MattersIf you are located in the European Union and have questions, concerns, or requests regarding your personal data or our data protection practices, you can contact our designated EU GDPR Representative:
Company Name:
Instant EU GDPR Representative Ltd
Instant EU GDPR Representative Ltd
Representative Name:
Adam Brogden
Adam Brogden
EU Dublin Address:
INSTANT EU GDPR REPRESENTATIVE LIMITED
Office 2
12A Lower Main Street, Lucan Co.
Dublin K78 X5P8
Ireland
INSTANT EU GDPR REPRESENTATIVE LIMITED
Office 2
12A Lower Main Street, Lucan Co.
Dublin K78 X5P8
Ireland
You can submit data protection requests, complaints, or other GDPR-related inquiries through our online portal or by contacting the representative directly.
Our EU representative can assist with Subject Access Requests, Right to Erasure, Data Breach reports, complaints, and other data protection matters under GDPR Article 27.