Information Harvest & Context
Our approach to data collection is surgical, not exhaustive. We distinguish between information necessary for app functionality and surplus diagnostic data. When you interact with Digavo applications, we may process technical identifiers, including Device IDs and localized IP addresses, to ensure server-side performance across Italy’s diverse network infrastructure.
We do not collect sensitive personal identifiers unless explicitly provided during a support inquiry or account creation. Our systems are optimized to minimize latency—especially for rural regions in Italy where data caps are a reality—by processing as much logic locally on your device as possible.
Method Note
Our evaluation approach uses a 'Privacy Pulse' methodology—every 60 days, we audit our data retention caches. This ensures we don't hold artifacts longer than necessary for the current app version. If a feature is deprecated, its associated data paths are severed immediately.
User Queries: Data Integrity
Do you sell my gaming habits to third parties?
Under no circumstances. Your interaction patterns remain internalized within Digavo to improve UX for the Italian market only.
How is my data protected on public Wi-Fi?
We utilize TLS 1.3 encryption for all data in transit between our mobile applications and our Rome-based servers.
Where is the data physically stored?
We rely on EU-located servers, primarily in Italy and Germany, to comply with strict GDPR localization requirements.
Can I request a full data dump?
Yes. Under GDPR Article 15, you may contact our legal desk for a machine-readable port of your data.
Is payment info stored on Digavo servers?
No. All Italian payment methods (Satispay, PostePay) are handled via encrypted tokens by our gateway partners.