Section 01Introduction
EmoPulse ("we," "our," or "us"), established in the European Union, is committed to protecting your privacy. This Privacy Policy explains how our emotion AI platform handles your information in compliance with the EU General Data Protection Regulation (GDPR) and other applicable data protection regulations.
This policy covers the website at emopulse.app and the public demos linked from it. EmoCity (emo.city) and the Clinic Stack have their own privacy policies, and enterprise deployments are covered by a written agreement.
Section 02Data Controller
The data controller responsible for your personal data is:
For data protection inquiries, contact us at info@emopulse.app.
Section 03How Each Version Handles Data
Your data is handled differently depending on which version you use:
3a. On-Device Version (the product default, and the Biometric Signature demo)
All biometric and emotional analysis runs entirely on your device:
- Camera, microphone, and biometric data never leave your device
- The face models (MediaPipe) load once from our own servers and then run locally
- No internet connection is needed once the page and the models have loaded
- No data is transmitted, stored on servers, or accessible to EmoPulse
- Works in air-gapped and offline environments
You can check this yourself: open the browser's network panel on Biometric Signature. After the page and the models load, the scan makes no further requests.
3b. Public Dashboard Demo (emopulse.app/dashboard)
The dashboard is a demo, and it sends data on purpose so we can see how the engine behaves and improve it. The camera and microphone are still processed in your browser.
- While a scan runs, the page sends the computed numbers to our server (ai.emopulse.app) every few seconds: for example stress, energy, focus, heart rate, blink and yawn counts, gaze, voice level and pitch, the emotion label and micro-expression counts
- It never sends video, audio or images
- Each record is stored in our server logs with the time and a shortened one-way hash of your IP address and browser type. Your name, email address and readable IP address are not stored with these numbers
- If you use the assistant chat, your message and the current numbers go to our server and to a third-party language model provider (see Section 10), which writes the reply. The conversation is kept in server memory for up to one hour and is not written to our logs
Starting a scan on the dashboard means you agree to this. If you want nothing to leave your device, use the on-device version (Biometric Signature).
3c. Server-Side Mode (Enterprise & Defence)
For enterprise, healthcare, and defence clients who choose server-side processing:
- Data processing occurs on dedicated servers under a separate Data Processing Agreement (DPA)
- All data is encrypted in transit (TLS), and at rest where the agreement requires it
- Server deployments can be on-premise, private cloud, or air-gapped - as required by the client
- Data retention, access controls, and deletion policies are defined per contract
- No data is shared with third parties without explicit client authorization
Important
Server-side processing for a customer runs only under a written agreement. The public dashboard demo is the one place on this website that sends numbers by default, and both this policy and the dashboard page say so.
Section 04Data We Process (On-Device Only)
In on-device mode, EmoPulse analyzes the following data types - all processed entirely on your device:
- Camera Feed: Used for facial expression analysis, heart rate detection (rPPG), micro-expression detection, gaze tracking, and neural mesh mapping. Never recorded or transmitted.
- Microphone Input: Used for voice emotion analysis (pitch, tone, speech patterns, emotional contagion). Never recorded or transmitted. Microphone access requires your explicit permission before activation.
- Biometric Data: Heart rate (BPM), stress levels, cognitive load, authenticity score and the other parameters the dashboard shows. Heart rate variability (HRV) and breathing rate are in development and not shown yet. Calculated locally and stored only on your device.
Section 05Data We Do NOT Collect
We want to be clear about what we do NOT do in on-device mode:
- We do NOT record video or audio
- We do NOT send camera or microphone data to any server
- We do NOT store facial images or voice recordings
- We do NOT share biometric data with third parties
- We do NOT use your biometric data for advertising or profiling
- We do NOT sell your data to anyone, ever
- We do NOT use your data to train AI models
Section 06Data We May Collect
On this website we may collect the following:
| Data Type | Purpose | Legal Basis (GDPR) |
|---|
| Computed scan numbers from the dashboard demo (no video, audio or images) | Analysing and improving the engine | Your explicit consent when you start a demo scan (Art. 6(1)(a), Art. 9(2)(a)) |
| Assistant chat messages (dashboard demo) | Writing the reply | Consent (Art. 6(1)(a)) |
| Page views: page address, referring page, browser type, a random per-tab ID | Counting visits to improve the website | Legitimate interest (Art. 6(1)(f)) |
| IP address (server and hosting logs) | Security & abuse prevention | Legitimate interest (Art. 6(1)(f)) |
| Email address and messages you send us | Answering you | Legitimate interest (Art. 6(1)(f)) |
Section 07AI Model Downloads
EmoPulse uses face models (MediaPipe) that run locally on your device. Your browser downloads them from our own servers when the page opens and keeps them in its cache. During this download:
- Only the AI model files are transmitted to your device - no user data is sent back
- After download, models operate fully offline
- No personal or biometric data is transmitted during the model download process
Section 08Consent for Camera & Microphone
EmoPulse requires explicit user permission before accessing your camera or microphone. You can:
- Grant or deny camera and microphone access at any time through your device settings
- Use EmoPulse with camera only (no microphone) - voice analysis will be disabled
- Revoke permissions at any time - EmoPulse will continue to function without biometric analysis
Voice Data Notice
In certain jurisdictions, voice data may be classified as biometric data requiring explicit informed consent before collection. EmoPulse processes voice data only after you grant microphone permission, and audio never leaves your device. The dashboard demo sends only voice numbers (level, pitch and a voice emotion label) together with the other scan numbers. No voice recordings are stored.
Section 09Cookies & Website Tracking
The EmoPulse website (emopulse.app) sets no cookies of its own and uses no advertising or third-party trackers.
- Page counter: a small script of ours counts page views. It keeps a random ID in your browser's session storage, which is deleted when you close the tab, and sends the page address, the referring page and your browser type to our server. Your IP address is not stored in readable form.
- Assistant chat: works without cookies.
- No advertising cookies: We do not use any advertising or tracking cookies.
Our hosting provider and our server keep standard request logs (IP address, browser type, time) for security.
Section 10Third-Party Services
We use the following third-party services:
- Vercel: Website hosting - receives standard HTTP request data (IP, user agent)
- Language model providers (dashboard assistant chat only): Groq, Google Gemini, SambaNova, NVIDIA, Cerebras and OpenRouter. When you write in the chat, we send your message and the current scan numbers to one of them to write the reply. They never receive images or audio.
- Google Fonts: Typography assets loaded from CDN
Each third-party service operates under its own privacy policy.
Section 11Data Retention
- On-device biometric data: Stored only for the duration of your session, or until you delete it through app settings. We have no access to this data.
- Dashboard demo numbers: Kept in our server logs, without your name or a readable IP address, until we delete them.
- Assistant chat: Kept in server memory for up to one hour, not written to our logs.
- Page counter data: Kept without a readable IP address, until we delete it.
- Enterprise/server data: Retention defined per Data Processing Agreement with each client.
Section 12International Data Transfers
In the on-device version no personal data is transferred anywhere. Our server (ai.emopulse.app) is in the United States, so the dashboard demo numbers, chat messages and page counts are processed there, and the language model providers listed in Section 10 may process chat messages in the United States. Where personal data leaves the European Economic Area (EEA), we rely on the transfer safeguards our providers offer under the GDPR, such as Standard Contractual Clauses (SCCs).
Section 13Children's Privacy
EmoPulse is not intended for unsupervised use by children. Age restrictions vary by jurisdiction:
- European Union: Users must be at least 16 years old (or the minimum age set by their EU member state, which may be as low as 13)
- United States: Users must be at least 13 years old (in compliance with COPPA)
- Other jurisdictions: Users must meet the minimum digital consent age in their country
We do not knowingly collect personal data from children below the applicable age threshold. If you believe a child has provided us with personal data, please contact us at info@emopulse.app and we will delete it promptly.
Section 14Your Rights Under GDPR
If you are located in the European Economic Area, you have the following rights:
- Right of access (Art. 15): Request a copy of any personal data we hold about you
- Right to rectification (Art. 16): Correct inaccurate personal data
- Right to erasure (Art. 17): Request deletion of your personal data
- Right to restriction (Art. 18): Request restriction of processing in certain circumstances
- Right to data portability (Art. 20): Receive your data in a structured, machine-readable format
- Right to object (Art. 21): Object to processing based on legitimate interest
- Right to withdraw consent: Withdraw consent at any time without affecting prior processing
To exercise any of these rights, contact us at info@emopulse.app. We will respond within 30 days.
You also have the right to lodge a complaint with your local data protection supervisory authority within the European Union.
Section 15Security
We implement appropriate technical and organizational measures to protect your data:
- On-device version: Biometric data never leaves the device
- Encryption: All data in transit uses TLS
- Access control: In the on-device version nobody at EmoPulse can see your data. The dashboard demo numbers on our server are open only to our own team
- Regular security reviews: We conduct periodic security assessments of our platform
- Minimal data: The demo sends numbers only, never video, audio or images
Section 16Changes to This Policy
We may update this Privacy Policy from time to time. When we make significant changes, we will:
- Update the "Last Updated" date at the top of this page
- Notify registered users by email (if applicable)
- Display a notice in the application
Our core commitment: video and audio stay on your device in every version, and the on-device version sends nothing at all.
Section 17Contact Us
If you have questions about this Privacy Policy or want to exercise your data protection rights:
Summary
All analysis happens on your device: we never see your face or hear your voice. The on-device version sends nothing. The public dashboard demo sends computed numbers to our server so we can analyse and improve the engine. Enterprise clients who choose server-side processing get a written Data Processing Agreement.