Privacy & Data Handling

Moveo One is designed with privacy, transparency, and compliance at its core.
We believe analytics should empower better user experiences — not compromise user trust.

This page explains how Moveo One handles data, what is collected, and how developers can maintain full control over privacy.

---

Overview

Moveo One operates under a privacy-first design principle:

• Only the minimum required data is collected to generate insights
• All user data is anonymized or pseudonymized at rest
• Developers retain control over what data is sent
• Moveo One complies with GDPR, CCPA, and HIPAA

---

What Data Moveo One Collects

Category	Examples	Purpose
Behavioral events	Clicks, taps, scrolls, screen views, navigation	Understanding flow, engagement, friction
Session metadata	Duration	Aggregation and segmentation
Predictive signals	Model scores, dwell time, hesitation	Generate real-time UX insights
Custom properties (optional)	e.g., plan type, experiment ID	Developer-defined attributes for analysis

🔒 No personal or sensitive data (names, emails, payment info) is required by default.
Developers can choose to anonymize all custom properties through SDK.

---

What Moveo One Does Not Collect

❌ No raw keystrokes
❌ No screenshots or visual screen capture
❌ No personal identifiers unless explicitly provided

These restrictions are enforced by SDK design — preventing accidental data leaks.

---

Data Ownership

• You (the customer) remain the sole owner of your collected data.
• Moveo One acts as a data processor, not a data controller.
• Data is stored and processed only within the selected region (EU or US).
• You can request export or deletion of your data at any time.

---

Regional Data Hosting

Region	Default Storage	Availability
EU	Frankfurt, Germany (GCP)	Default for EU-based orgs
US	Iowa, USA (GCP)	Optional for US orgs
Private Cloud / On-Prem	Customer-defined	Enterprise plan

---

Data Retention

• Predictive model training data: aggregated and anonymized
• Request to delet user sessions and/or data are permanently erased within 24 hours

---

SDK Privacy Controls

All SDKs (Web, iOS, Android, Flutter etc) are open sourced and published on Github Repository

---

Data Export & Deletion

Currently the data deletion is supported over explicit request thorugh an email to 📧 privacy@moveo.one

Soon supported: You can delete or export user data at any time via the API or dashboard.

API Examples

# Export user data
curl -X GET https://api.moveo.one/v1/users/export?userId=user_123 \
  -H "Authorization: Bearer YOUR_TOKEN_HERE"

# Delete user data
curl -X DELETE https://api.moveo.one/v1/users?userId=user_123 \
  -H "Authorization: Bearer YOUR_TOKEN_HERE"

✅ Example response:

{ "status": "deleted", "userId": "user_123" }

---

Compliance & Certifications

Standard	Status	Notes
GDPR	✅ Compliant	Data hosted in EU regions by default
CCPA	✅ Compliant	Supports data deletion and export rights
HIPAA	⚙️ Available	Optional BAA for enterprise deployments
SOC 2 Type II	🚧 Planned	Target Q3 2026 certification

---

Data Encryption

• All data is encrypted in transit (TLS 1.2+) and at rest (AES-256)
• API keys and tokens are hashed and never stored in plaintext
• Predictive model data uses feature-level obfuscation

---

User Consent

You can integrate Moveo One with your existing consent flow.

Example:

if (userConsented) {
  MoveoOne.enableTracking();
} else {
  MoveoOne.disableTracking();
}

---

Developer Tips

✅ Recommended

• Anonymize user IDs unless you need cross-session tracking
• Always disclose analytics usage in your product’s privacy policy
• Use Moveo’s SDK options to disable tracking in sensitive contexts (e.g. payment screens)

❌ Avoid

• Sending PII in event names or property keys
• Using custom properties to encode private data

---

Contact

For compliance or data protection questions, contact our DPO team: 📧 privacy@moveo.one