Privacy Policy

This policy describes which personal data Wackerle Digital Solutions processes for the website solobooth.app and the application SoloBooth (studio.solobooth.app), for what purpose, and which rights you have. The Swiss Federal Act on Data Protection (FADP) applies. Where the EU General Data Protection Regulation (GDPR) is applicable, it applies in addition.

1. Controller

Wackerle Digital Solutions
Fabian Wackerle
Breitenlooweg 6
8047 Zurich
Switzerland
Email: hallo@solobooth.app

2. Visiting the website

When you open solobooth.app, our hosting provider stores technically necessary information in server log files: IP address, date and time, the page requested, the amount of data transferred, browser and operating system, and the page visited before. We need this data for secure and stable operation; it is not combined with other data and is deleted after a short time.

The website sets no cookies and loads no content from third parties – no third-party analytics or advertising scripts either. How we measure which ads lead to a subscription is described in section 3. The fonts are served from our own server. The only exception: if you take out a subscription on the website, your browser loads program code from our payment processor Paddle for that purpose (see section 5).

Visitor statistics: we count how many people visit the website and where they come from ourselves – without a cookie, without third-party scripts or services, on our server in Switzerland. For this, your browser reports on each page view the page requested, the language, the page visited before and any campaign parameters in the address (utm_source, utm_medium, utm_campaign, utm_content, utm_term, ref). Of this we store the page, the language, only the domain of the page visited before, the campaign parameters, the type of device (computer, phone, tablet) and a daily identifier. The daily identifier is a hash of your IP address, your browser and a random value that we generate anew each day; we delete the old one. This lets us count the visitors of a day, but neither identify you nor recognize you on another day. We do not store your IP address for this. We delete these entries after 13 months.

3. Signing up on the website

If you create your account in the window on the website, your name, email address and password are sent to our application; section 5 applies. So that the window can continue after a reload, your browser remembers a key for this sign-up until the tab is closed (session storage). We keep only a hash of it, together with the IP address of the sign-up to protect against abuse – both for a few days.

Ads: if you reach the website through one of our ads on Google, Google appends a click identifier to the address. Your browser remembers it until the tab is closed (session storage); we set no cookie for this and load no script from Google. If you create an account, we store the identifier with it. If you then take out a subscription, we report to Google (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland) the identifier, the amount excluding tax, the currency, the time and the number of the payment – no name and no email address. This shows us which ads lead to subscriptions. We delete the identifier together with the account.

Origin: so that we can see which channels lead to sign-ups, your browser remembers until the tab is closed how you reached the website: the first page you opened, the domain of the page visited before and any campaign parameters in the address (session storage). If you create an account – in the window on the website or via the application’s sign-up, to whose link we append this information – we store it with your account. We delete it together with the account.

4. Contact by email

If you write us an email, we process your details in order to answer your request.

5. Using SoloBooth

To let you use the application, we process:

• Account: name, email address, password (stored only as a secure hash), plan, time of sign-up and of the last sign-in, origin of the sign-up (see section 3).
• Sign-in protection: sign-in attempts with email address, IP address and time, to detect and slow down attacks on accounts.
• Content: projects, imported scripts and PDFs, markup, voice recordings, room tone, music and effect files, and the exports created from them.
• Collaboration: invitations, project shares, roles, assignments and an activity log within a project.
• Client review: if you send someone a client review link, we process the name that person enters there (and their email address if they provide it), their favorites and comments. They are visible to you and to those involved in the project. If you protect the link with a password, we store it with the link so you can display it again.
• Profile page: demos you mark or upload, and the details you enter for your public page – profile picture, details about your voice, studio, productions, contact, linked videos, logo, your own domain and the details for your legal notice. On the Pro plan, this also includes testimonials (quote, name and role of the person quoted), client logos and names, and images and texts of custom sections. For details about other people you need their consent. Only what you publish is public.
• Account emails: we send to your address the message to confirm the address, a welcome, on request the link to reset your password, and the confirmation when your account has been deleted. We store the links in them only as a hash; for a “Forgot your password?” request we store the IP address for a short time to slow down abuse.
• Subscription: if you take out a subscription, we store plan, billing period, status and the customer number at our payment processor (see below). We neither see nor store payment details such as card numbers.
• Feedback: if you report something via the “Feedback” button, we store category, text, the address of the page, language, browser and – if you attach one – the screenshot. Reports are anonymous by default; we only store your name and email address if you untick “Send anonymously” so that we can reply to you. To help us trace errors, technical details without personal data are added: browser and operating system with version, screen and window size, time zone, device performance, connection type, storage used in the browser, microphone permission and the number of audio devices (without their names), supported features, loading times, the latest error messages and failed requests since the page was loaded, as well as your plan and the age of your account. Text from your projects, device names and your IP address are not included; email addresses and access keys in these details are removed before saving. Anonymous reports are stored without any link to your account – without name, email address, project IDs and account age. We remember your choice in your account or, as a guest, in your browser.
• Usage statistics: we count how often the individual pages and functions of the application are opened per day and by how many people. For this we use a daily identifier as on the website (section 2), formed from your account number instead of the IP address; it is deleted after one day. Only totals per day and function are kept – with no link to your account and no content from your projects.
• Requests via your profile page: name, email address, project details and any script attached by the person making the request. We store them on your behalf; only you can view them. We send a notice without the content of the request to your account address. To protect against abuse, we store a hash of the IP address for each request.

We need this data to provide the application to you. We do not analyze your recordings and scripts, do not sell them and do not use them to train AI models.

AI prep: if you start AI prep, the text of the selected chapters is sent to the AI services of Infomaniak Network SA in Switzerland so that they can suggest paragraphs, characters and direction. According to Infomaniak, the requests are neither stored nor used to train models. We ourselves log neither texts nor responses; we only store how much you have used. No text is sent to an AI without your action, and recordings never are.

Payment: subscriptions are processed by Paddle (Paddle.com Market Ltd, Judd House, 18–29 Mora Street, London EC1V 8BT, United Kingdom). Paddle is the contracting party for the purchase (Merchant of Record), collects the amount and issues the invoice. For this purpose Paddle processes, under its own responsibility, your name, email address, billing address, payment details and IP address; Paddle’s privacy policy applies. On the “Subscription” page and when completing a purchase in the window on the website, your browser loads program code from Paddle for this; the data may also be processed outside Switzerland, for example in the United Kingdom and the USA. If you do not take out a subscription and do not open the “Subscription” page, you have no contact with Paddle.

Videos on profile pages: we fetch preview images of linked YouTube videos once and serve them from our server. YouTube itself is only loaded when someone starts a video.

Speech recognition: auto-scroll and breath detection run locally in your browser. The speech model needed for this is loaded from our server; your voice is not transmitted to us or to third parties for it.

Cookies: the application sets a session cookie for signing in. If you choose “keep me signed in”, a further cookie recognizes you for up to 30 days. If you choose a language, another cookie remembers that choice. A fourth only records that you are signed in (value “1”, for up to 30 days): it lets our website recognize that you already have an account, so that choosing a plan takes you into the application instead of to the sign-up. All four are technically necessary; there are no tracking cookies.

Program libraries: some views of the application load JavaScript libraries (Alpine.js, vosk-browser) from the public content delivery networks unpkg.com and cdn.jsdelivr.net. Their operators receive your IP address and technical information about your browser; the servers may also be located outside Switzerland, for example in the USA. No content from your projects is transmitted in the process.

6. Profile pages and client review links

Our users’ profile pages and client review links are hosted on our servers – at a SoloBooth address or at the person’s own domain. The person who owns a profile page is responsible for its content and for requests received via its form; we process this data on their behalf. Each profile page has its own privacy policy describing what the page does.

Visits: When a profile page or client review link is visited, the same technically necessary information is processed as when visiting the website (section 2). Profile pages set a technically necessary session cookie (it protects the request form against misuse); there is no analytics and no tracking. Fonts, images and demos come from our server. YouTube is only loaded when someone starts a video.

Client review links: If someone enters a name on the review page, a cookie remembers who is commenting for up to one year. If the link is password-protected, another cookie keeps it unlocked for 30 days. After an incorrect entry, we store a hash of the IP address with the time to slow down repeated attempts; we delete these entries after one day.

Custom domains: For a custom domain, we automatically obtain a certificate for the encrypted connection on the first visit, from Let’s Encrypt (Internet Security Research Group, USA) or alternatively from ZeroSSL. Only the domain name is transmitted. Certificates are entered in public logs (Certificate Transparency); the domain name is visible there to everyone.

7. Hosting and server location

Website, application, database and all uploaded files are hosted by Infomaniak Network SA, Rue Eugène-Marziano 25, 1227 Geneva, in data centers in Switzerland. Infomaniak processes the data only on our behalf.

8. Disclosure

We disclose personal data only when it is necessary for operation (hosting, see above; for custom domains, the domain name to the certificate authority, see section 6), when you initiate it – for example when inviting other people to a project, publishing your profile page, sending a client review link, starting AI prep or taking out a subscription (Paddle, see above) – or when we are legally obliged to do so.

9. Retention and deletion

We store account data and project content for as long as your account exists. If you delete a project, the associated data is removed. You can delete your account yourself at any time in the application under “Account”, including all content and immediately; on request we do it for you. What you recorded or uploaded in other people’s projects remains part of those projects. Paddle retains invoices for as long as the law requires. Backups are overwritten as part of their normal cycle. We delete requests via profile pages after 180 days unless you delete them yourself earlier. Images for your profile page (logos, images of custom sections) that you no longer use are deleted the next time you save. We keep sign-in attempts and server log files only for as long as necessary for security. We delete the website’s visitor statistics (section 2) after 13 months; the totals of the usage statistics contain no personal data.

10. Data security

Transmission is encrypted (HTTPS). We store passwords only as a hash. Only you and the people you invite have access to your projects.

11. Your rights

You can at any time request information about your stored data, have it corrected or deleted, object to its processing and request that your data be handed over in a common format. To do so, write to hallo@solobooth.app. You also have the right to lodge a complaint with the Federal Data Protection and Information Commissioner (FDPIC) or – where the GDPR applies – with the competent supervisory authority in your country.

12. Changes

We adapt this policy when our data processing changes. The version published here applies.