Your Data, Your Rules. No Surprises.
In the gaming world, data is currency. At diglino.pro, we treat your privacy with the same respect we have for a well-optimized build. This isn't legalese—it's our playbook for protecting your information.
What We See, What We Store
Transparency is a design principle, not a footer note. Here’s the exact data we collect and the specific reason for each piece.
Key Terms
- Anonymous Identifiers
- Random strings we use instead of your email to track which apps you review, without knowing who you are.
- Aggregate Data
- Patterns from thousands of users (e.g., "70% of mobile gamers prefer dark mode"), which can never be traced back to you.
Account Information
- Email address (for subscriptions and updates)
- Username (your public handle on diglino)
- Encrypted password (using bcrypt hashing)
Purpose: To identify you, secure your account, and send you the reviews you asked for.
Usage & Behavior
- Pages viewed, time on site, click paths
- App review ratings and comments
- Device type (mobile vs. desktop)
Purpose: To improve our review algorithms and understand what content helps you make decisions.
Technical Data
- IP address (for basic security)
- Browser version (for compatibility)
- Referring site (how you found us)
Purpose: To maintain site security, diagnose technical issues, and ensure our reviews look correct on your device.
Things We NEVER Collect
- Your phone's unique IMEI number
- Precise location data (GPS)
- Your contacts or friend lists
- Any data from your other apps
This is a hard line. We don't build profiles for ad sales.
The Engineering Trade-Offs
How we balance functionality with your privacy—like tuning a character build.
Transparency Log: Last updated June 2026
Analytics vs. Identification
We use Matomo, a self-hosted analytics tool, not Google Analytics. This means your visit data stays on our server in Warsaw, not shared with third parties. The trade-off? We can't easily sync data with our ad partners (because we don't have any).
Feature vs. Friction
We could offer a "single sign-on" with social media, but we don't. Why? It creates a data pipeline we can't control. The trade-off: You have to type an email. The benefit: Your gaming history isn't linked to your Facebook profile.
Support vs. Scalability
We don't use chatbots that harvest conversation data. Our support is human. The trade-off: Response times can be slower during peak traffic. The benefit: Your privacy question is answered by a person, not a data-mining AI.
Your Controls. Your Data.
GDPR gives you powers. Here’s exactly how to exercise them on diglino.pro. No forms hidden in footers.
Access & Portability
Article 15 & 20
Want to see everything we have on you? We'll export it in a clean CSV file. This includes your review history, account details, and technical logs.
Request Your DataRectification
Article 16
Made a typo in your username? Need to correct an email? We'll fix it within 48 hours. No questions asked for simple corrections.
Request CorrectionErasure
Article 17
The "Right to be Forgotten." If you delete your account, your personal data is wiped from our primary database. Anonymized review data (ratings without your name) may remain for editorial integrity.
Restriction & Objection
Articles 18 & 21
You can object to our processing for marketing purposes. You can ask us to stop processing your data while we verify a request. We'll pause and notify you.
Object or RestrictQuestions We Ask Ourselves
These aren't just questions from regulators. They're the checks we run before launching any new feature that touches user data.
Is this the minimum data required?
We challenge every data point. If we can provide the same service without it, we don't collect it. Example: We don't require your birth year to show you game reviews.
Can a user opt-out without breaking the site?
Essential cookies only. Marketing and analytics can be fully disabled in our Cookie Center. The site will still function, just without personalization.
Who has access to the raw data?
Only two senior engineers have raw database access. It's logged and audited. No marketing team, no third-party analysts.
What happens if we're acquired?
Our user data is not an asset in a sale. Any M&A deal would require the acquiring company to honor this policy, or provide a clear exit for users.
Are we compliant with regional laws?
We follow GDPR as our baseline. For Polish users, we also comply with UODO (Urząd Ochrony Danych Osobowych) guidance. We monitor EU and US state law changes.
How do we handle data breaches?
We have a 72-hour notification protocol. If your data is compromised, you'll hear from us directly, not first from a news site.
Our Privacy Officer
For all requests regarding your data, access, or questions about this policy, contact our designated Data Protection Officer.
ul. Nowy Świat 1
00-001 Warszawa, Poland
Supervisory Authority
Should you need to lodge a complaint, you have the right to contact the Polish Data Protection Authority (UODO). We encourage you to contact us first to resolve any issues.
PRIVACY IS A PROCESS, NOT A POLICY
Ready to Review Your Data?
Export, correct, or delete. It's your right, and we make it straightforward.
Email Our Privacy OfficerResponse time: Under 24 hours on business days.