STILLTALK · 17 SEPTEMBER 2026 · VERSION 2026-09-17.2

Privacy policy

We ask for an email address only if you choose to join the waitlist. Watching the story and trying the prepared recordings do not require an account or email.

1. Who is responsible

PMCC Performance Sp. z o.o.
ul. Woronicza 31/250, 02-640 Warszawa, Poland
KRS 0000530314 · NIP 5213681541
Share capital: PLN 126,000
Sąd Rejonowy dla m.st. Warszawy w Warszawie, XII Wydział Gospodarczy Krajowego Rejestru Sądowego

PMCC Performance Sp. z o.o. is the data controller for StillTalk. Contact for privacy and other enquiries: biuro@pmcc.pl.

2. The demo you are using

The characters are AI-generated, animated in your browser, with prerecorded synthetic speech. This is not a live person or a video call. When you press “Speak my sentence”, your text, chosen language and voice are sent through our server to Microsoft Azure Speech to generate matching audio and mouth movements. This happens only on your request; choosing a character or typing alone does not send your text. We do not send it to OpenAI. Please do not enter personal or confidential information.

Your browser requests the selected assets and recordings from our server. Your IP address is necessarily used to deliver those responses. We do not run advertising pixels, screen/session replay, key-press recording or third-party analytics. Optional first-party visit measurements are described in section 9. There are no automated decisions with legal or similarly significant effects.

3. Data, purpose and legal basis

• Requested live speech: your short text and selected language/voice, under Article 6(1)(b) GDPR, to provide the optional synthesis you request. The resulting audio, text and mouth data are held in a bounded server-memory cache for up to 16 minutes to avoid repeating the same synthesis. They are not saved to our content database or used for analytics.
• Waitlist and product contact: your email, signup/confirmation times and the precise consent and terms version. We use your consent under Article 6(1)(a) GDPR to send StillTalk launch, early-access and product updates. The separate email-contact consent also covers commercial communications under Article 398 of the Polish Electronic Communications Law. No unrelated newsletter is included. Consent is voluntary; declining it does not limit the demo.
• Delivering the requested waitlist service: maintaining your signup and processing its cancellation, under Article 6(1)(b) GDPR. Providing an email is not a statutory requirement, but we cannot provide email updates without it. In the current no-email mode, we save your request without verifying the mailbox and show a private cancellation link on the success screen. No automatic emails are sent. These records are labelled unverified, not confirmed.
• Security and abuse prevention: temporarily processing the connection IP and keeping a keyed, rotating representation for request limits; send status, attempts and timestamps. The application does not store a raw IP with a signup. Basis: Article 6(1)(f), our legitimate interest in preventing spam, protecting recipients and operating a secure service. A pseudonymous rate-limit key is not anonymous data.
• Enquiries and complaints: contact information and correspondence you choose to send. Basis: Article 6(1)(f), handling enquiries and protecting rights, or Article 6(1)(b) where the enquiry concerns a requested service. A legal duty may also require processing under Article 6(1)(c).
• Consent evidence: minimal dates, consent version/text and a keyed representation of the email after removal, under Article 6(1)(f), to demonstrate permission and address disputes. It is not used to contact you.

4. How long we keep it

• No-email signup requests: until cancellation or at most 12 months. When email confirmation is enabled, pending confirmation requests are kept for at most 7 days and confirmation links expire after 48 hours.
• If email confirmation is introduced later, confirmed subscriptions are also limited to 12 months from the original signup. A later, fresh signup requires fresh consent.
• After unsubscribe: the active email and queued mail are removed immediately; limited pseudonymous consent evidence is kept for up to 12 months. No new updates are queued for that subscription. A message already handed to a mail server cannot always be recalled.
• General rate-limit records: at most 48 hours after their time bucket ends. Live-speech quota records contain timestamps, a keyed network identifier, voice, reserved budget and outcome, but no text or audio, and are retained for up to 35 days to enforce monthly free-tier limits. IPv6 addresses are grouped by /64 network. These pseudonymous records are used for abuse prevention under Article 6(1)(f). SMTP job records are removed with the request or subscription.
• Correspondence: normally until the enquiry closes and up to 12 months afterwards. A specific legal duty or documented dispute can justify a longer, restricted retention period; we do not use that exception to keep the mailing list indefinitely.

These are our operational retention limits, not claims that the law prescribes these exact periods. Encrypted backups have a documented expiry and must reapply unsubscribe/deletion records before a restore is used.

5. Who can receive data

Only authorised PMCC personnel and contracted technical providers to the extent needed for the service: hosting and email delivery, and legal advisers where necessary. Public authorities may receive data where legally required. We do not sell the list or share it with any other company for its own marketing.

Hosting: Hetzner Online GmbH, Nuremberg, Germany (EEA). Waitlist data is stored on this server. Optional live speech is sent to Microsoft Azure Speech in the configured West Europe region.

Email delivery: Not connected. No emails are sent.

Playing the supplied recordings does not send your email or typed text to Azure or OpenAI. Microsoft Azure also processes text you explicitly submit for live speech. We use prebuilt voices, not uploaded voice training. Microsoft states that input text and output audio from this real-time prebuilt-voice service are not retained in its logs. Microsoft’s speech data notice.

6. Transfers outside the EEA

Assets and waitlist data are hosted in Germany. Waitlist data is not forwarded to Azure or OpenAI. Only text explicitly submitted for live speech is forwarded to Microsoft Azure. The configured speech endpoint is in West Europe; Microsoft’s applicable data-processing terms govern its handling of this data.

Where an international transfer is needed, an applicable GDPR mechanism and any necessary additional safeguards must be in place. You can ask the contact above for information and a copy or explanation of applicable safeguards.

7. Your choices and rights

Use the private cancellation link shown after signup (or an unsubscribe link in an email, when email is enabled), or contact us, to withdraw consent at any time, without affecting the lawfulness of earlier processing. You may request access, correction, erasure, restriction and, where applicable, portability. You may object to legitimate-interest processing; you can always object to direct marketing. Some rights depend on the legal basis and circumstances.

We normally respond within one month, with any lawful extension explained. You may complain to the Polish data protection authority, President of the Personal Data Protection Office (UODO), or to a competent supervisory authority in your country.

8. Browser storage, diagnostics and changes

See Cookies & storage. The support-only diagnostic mode is off in ordinary visits. If you are invited to use it, it displays a diagnostic badge and sends timing, selected recording IDs, browser information and error events for troubleshooting, not typed text or images. It is separate from the waitlist and is not a visitor-analytics feature. Its scope and retention must be explained as part of that support session.

Material changes will be announced before they affect your choices. We will request new consent where the purpose changes. This version applies to the demo and waitlist described here, not to an unlaunched paid avatar-generation service.

You can save this page or print it to PDF using your browser’s Share / Print menu.

9. First-party visit measurements and server reliability

The server counts page requests, transferred bytes, HTTP failures and CPU/memory use without a visitor identifier. These aggregate operational statistics help us run the service under Article 6(1)(f) GDPR and are kept for up to 12 months; detailed server performance and errors are kept for 30 days. Page requests include reloads and bots and are not a count of unique people.

If you choose “Allow measurements” under version 2026-09-16.2, we collect a random browser ID linking visits for a maximum of 30 days, per-page session IDs, connection IP addresses, approximate country, visit and playback timestamps, foreground-tab duration, fixed character/language/recording selections, scene numbers, live-synthesis outcomes and sanitised technical errors. The browser credential is stored in localStorage only after consent and expires after 30 days without automatic extension. We use the connection IP locally to estimate country and group connection-level activity in an access-controlled operations panel. Different people may share an IP or browser; a browser ID does not identify a verified person. This optional measurement relies on consent under Article 6(1)(a) GDPR and is off until allowed. Full IP addresses and pseudonymous IDs are personal data. Older measurement consent is not silently expanded: you are asked again. Earlier records retain only masked networks and are not retrospectively linked. We do not use device fingerprinting.

These measurements stay on our Hetzner server in Germany and in encrypted backups held by the controller, and are not combined with the email waitlist. There is no screen recording, keystroke logging, advertising profile or forwarding of your IP to a geolocation API. Country lookup uses a local DB-IP Lite database; country can be wrong for VPNs or mobile networks. IP Geolocation by DB-IP.

Session, event and connection details expire after at most 30 days; expired browser groups are removed on the next hourly cleanup or server start. The Privacy choices button lets you decline or withdraw consent. Withdrawal stops new measurements and requests deletion of all visits linked to the current browser credential, including associated IPs and events; aggregate operational counts remain. Other open tabs are notified to stop. If offline, transmission stops locally and server records expire normally. Clearing browser storage removes the credential and preference, not existing server data. You can contact us about data rights. Optional measurements are incomplete if you decline, block requests, close the tab abruptly or your browser crashes.