Data Ownership
You retain all rights, title, and interest in your raw event data.
// Example export trigger
POST /api/v1/export
{ "ownership": "client" }
POST /api/v1/export
{ "ownership": "client" }
Terms of Service
This document governs your use of datavo.pro. It is written with clarity and precision, reflecting our commitment to transparency. By accessing our analytics platform, you agree to these terms.
GDPR Compliant
Data Residency: EU
Transparent Pricing
Our Data Philosophy: No Hidden Agendas
We built datavo.pro because we were tired of opaque analytics platforms. Our terms reflect that core belief: you own your data, you control your stack, and you should never be surprised by a fee or a limitation.
This document is not just legal boilerplate. It's a reflection of how we operate. If you find a clause that feels unjust, tell us. We’re engineers and analysts first, lawyers second.
Core Principles
Effective Date: 01/2026Scope of Service
We provide analytics infrastructure, not game design or marketing strategy.
- Real-time aggregation
- Custom event tracking
- Retrospective cohort analysis
- Raw data access (via API)
Liability Framework
Our service is a tool. We are not liable for your business outcomes.
Direct Damage
Capped at 12 months of service fees.
Indirect Consequential
Excluded. Read: we don’t cover lost revenue.
Acceptable Use & Prohibitions
We enforce a strict but reasonable acceptable use policy to ensure platform stability and data integrity for all clients. These rules are based on real incidents and hard constraints.
Category
Required Behavior
Consequence of Violation
Data Volume
Manage rate limits
Adhere to API rate limits (documented per tier). Batch events
efficiently. No spam-flooding endpoints.
1st offense: Warning & rate throttling.
2nd: Account suspension (72h).
3rd: Termination.
2nd: Account suspension (72h).
3rd: Termination.
Privacy & GDPR
Protect user data
Do not collect PII (Personally Identifiable Information) without
explicit, auditable consent. Anonymize data streams.
Immediate suspension. Mandatory audit. Potential data purge
request from user.
Security
Secure access
Maintain secure API keys. Report security vulnerabilities
immediately. Do not attempt penetration testing without written
permission.
Key revocation. Account lock. Legal reporting for malicious
intent.
Field Notes: A Real-World Boundary
Scenario: An indie developer in Hamburg, "PixelForge," wanted to track user sentiment by logging chat messages sent through their in-game mail system. They assumed our platform would handle the storage and analysis of this text.
Conflict: Upon review, this violated Section 4 (Privacy). Chat logs contain potential PII and private conversations. Our automated flagging system suspended their data pipeline for 24 hours.
Resolution: PixelForge worked with our support to refactor their implementation. They now only log metadata (e.g., "message sent," "recipients") and hash identifiers. The raw text remains on their own servers, ensuring GDPR compliance.
Lesson: Our terms are built on real edge cases. What seems like a minor tracking event can cross a legal line. When in doubt, anonymize.
Key Criterion
Ask: "Could a user be identified directly from this data stream?" If yes, you need explicit consent.
// Don't track
{ user_id: "123", chat:
"secret_plan.txt" }
// Do track
{ user_hash:
"a1b2", event: "msg_sent" }
Final Provisions & Amendments
These terms are subject to change. We will notify users of significant updates via email and a dashboard banner 30 days prior to effect. Any continued use of the service after the effective date constitutes acceptance of the new terms.
Governing Law: These terms are governed by the laws of the Federal Republic of Germany. Disputes shall be resolved in the courts of Berlin, Germany.