Privacy & legal

How Epimela handles your information.

This notice explains how Epimela handles information across our website, interactive demos, the public Worst Call Challenge, Founding Pilot applications, and MVP pilot accounts.

Version: 14 October 2026

1. Controller

GDPR Data Controller

Revisum d.o.o.Kruzna 79, 10000 Zagreb, CroatiaEmail: [email protected]

Epimela is operated by Revisum d.o.o.

We act as controller for website inquiries, personalised demo requests, feedback, pilot applications, account administration and our own product operations described below.

When a service business uses Epimela to manage its customers’ information, that business determines the purposes of that processing. If your information was submitted by such a business, contact it first about the handling of your service request. The respective responsibilities and processing instructions should be set out in the applicable pilot or data-processing agreement.

Part A

Privacy on the website & in inquiries

2. Website hosting & technical data

Hosting and secure delivery

Epimela is hosted on infrastructure provided by Hetzner Online GmbH, Germany. Technical request information such as IP address, request time, browser or device information and server logs may be processed as necessary to deliver, secure and troubleshoot the service.

Website and demo usage measurement is described in the first-party analytics section below.

3. Demo requests, feedback & pilot applications

Information you send to us

When you request a personalised demo, send feedback or apply for the Founding Pilot, we may process your name, business name, work email, optional telephone or contact details, company website, business profile, communication channels, workflow challenges, notes and other information you choose to submit.

We use this information to respond to you, assess pilot fit, prepare a relevant demo, operate the pilot and improve Epimela.

For demos, please use sample or anonymised customer information where possible. Do not send sensitive personal information or real customer data unless we have specifically agreed that this is appropriate for the pilot.

Part B

Privacy in the demo & product

4. Accounts & authentication

Keeping pilot accounts secure

For registered pilot users, Epimela stores the account and security records needed to provide access. These can include your email address and account identity, account permissions, authentication records, active session records, verification records and, if you enable two-factor authentication, the related security configuration.

Epimela uses necessary authentication cookies to keep you signed in and protect access to your account. Account and authentication records are stored with the Epimela application database on our hosted infrastructure. They are not used for advertising.

Account information is kept while the pilot account is active and for as long as reasonably necessary afterwards for security, support or legal obligations. Sessions and verification records are retained according to their security lifecycle and may expire or be revoked earlier.

5. AI processing

Google Gemini

Epimela currently uses Google Gemini services for AI functionality. When you use an AI-enabled demo or pilot workflow, the content needed for that function may be sent to Google for processing so Epimela can understand requests, extract useful work information and generate responses.

For voice-enabled demonstrations, this includes audio streamed during the call and transcripts used to provide the live conversation and related intake. If you choose to speak directly to Epimela, your browser requests microphone access. Prepared enquiries use a simulated caller.

Call transcripts and extracted service-request details can be saved in the demo or pilot workspace for review and follow-up. Audio may also be temporarily buffered on our server to recover missing transcription; the normal call-cleanup process removes those temporary files.

AI processing may include relevant customer messages, names, contact details, service addresses, photos, attachments and job context. Please use sample information in public demos.

6. Worst Call Challenge

The public challenge at epimela.com/challenge

The Worst Call Challenge is a public game: you describe a made-up difficult customer, AI voices play the customer and Epimela’s receptionist, and the call is graded. No account or microphone is needed. Please use made-up details only. We remove phone numbers, email addresses and street addresses from what you type, but that filter is not perfect.

We process what you type (the scenario, an optional made-up caller name, any lines you type), the call’s transcript, grade and synthetic audio, an optional email (it raises the daily limit and is used only to reply to a demo or pilot request) and, if you share a call, your share choice and any credit details. This text is sent to Google Gemini (sections 5 and 11). To limit abuse and cost we keep a salted one-way hash of your IP address, not the address itself. We do this to provide the game you asked for and for our legitimate interests in security and cost control; sharing is your choice.

Calls are private by default: only you can open them, with a key stored in your browser. Anyone with an unlisted link can open that call, and a featured call may be shown publicly, including on social networks. Authorised administrators can view calls to run the service and handle abuse. You can delete a call at any time. Private calls are also deleted automatically after 90 days (their audio after 14), and shared calls stay until you delete them. The challenge is not directed at children under 16.

7. Address verification

Geoapify

Where an Epimela workflow verifies or normalises an address, the address text may be sent to Geoapify for geocoding or address verification. This is used only when the relevant address feature is active. Public voice demos use staged addresses and do not invoke the normal address-verification tool.

8. Connected channels & service records

Customer conversations and work information

When a pilot business connects a communication channel such as WhatsApp, Epimela can process messages, contact identifiers, attachments and delivery information from that channel. The channel provider also processes information needed to deliver the conversation under its own applicable terms.

The pilot workspace can store customer contact details, service addresses, conversations, uploaded photos or files, job records, quotes, appointments and technician updates. This information is used to organise and carry out the business’s service work and is available to authorised users of that workspace.

9. Cookies & first-party analytics

Website and demo analytics

Epimela uses cookies or browser storage where technically necessary for authentication, session security and application operation. The public site also uses a temporary browser-session identifier for Epimela’s own usage analytics.

Epimela uses limited first-party analytics to understand how the website and demonstrations are used and to improve the MVP. We use our own analytics system, rather than Google Analytics or another third-party analytics service.

We may record pages or demo features used, timestamps, a temporary session identifier, technical event information, a masked IP address (the last part is dropped) and a general browser and device category (for example “Chrome on macOS, desktop”), which we also use to tell people apart from automated visitors such as link-preview tools and search crawlers. We do not perform an IP-to-location lookup ourselves. If our hosting or delivery infrastructure supplies country, region or city information with a request, we may also store those values; otherwise these location fields remain empty. We do not store the full IP address in our analytics records.

We do not use this analytics information for advertising, cross-site tracking or building advertising profiles, and we do not sell analytics data.

Where this processing involves personal data, our legal basis is our legitimate interests in understanding the use of Epimela, improving the service, identifying technical problems and preventing abuse, subject to applicable consent requirements for cookies and browser storage.

Analytics information is subject to the retention principles in section 10. We limit retention to what is reasonably necessary for these purposes; a fixed analytics retention period and automated deletion or aggregation schedule have not yet been established for the MVP.

During this MVP phase, we do not use advertising cookies or cross-site behavioural advertising technologies. If that changes, this notice and any required consent mechanism will be updated before those tools are enabled.

Part C

Rights & general information

10. Retention & security

How long information is kept

We keep personal data only for as long as reasonably necessary for the purpose for which it was collected, including providing the pilot, following up on an inquiry, maintaining account security, troubleshooting and meeting applicable legal obligations.

Simulation mode. Simulation is a separate test workspace for trying Epimela workflows. Users with the required permissions can delete simulation records themselves using the available deletion controls, or clear simulation customer, conversation, message, job and related records using the workspace reset control. This does not delete production records. We recommend using fictional customer details when testing.

Worst Call Challenge. Its retention periods are set out in section 6.

Production mode. Production is used for actual business operations and customer records. Retention and deletion depend on the business’s purposes, its instructions to us and applicable legal obligations. A simulation reset does not clear production data; production deletion requests must be handled separately by the responsible business or through our privacy contact.

We use access controls and encrypted HTTPS connections to protect information handled by Epimela. Authorised platform administrators can review demo feedback, applications and operational records for support and administration.

11. Providers & international processing

Where service providers process information

Hosting, AI, address-verification and connected-channel providers receive the information needed to supply their respective services. Hosting the application in Germany does not mean all third-party processing takes place in the EU or EEA.

Google’s Gemini API terms describe its handling of API content, including limited provider-side logging and processing in countries where Google or its agents maintain facilities. Provider-side retention is separate from records stored in Epimela.

You can contact us for information about the providers and international-transfer arrangements applicable to your pilot.

12. Your rights

Your data, your rights

Subject to applicable data-protection law, you may have rights to access, correct, delete or restrict the processing of your personal data, object to certain processing, and receive certain data in a portable format. Where processing is based on consent, you may withdraw that consent.

To make a privacy request, email [email protected].