didka Security
We protect your data with strong encryption.
Encryption
Data Security
Protecting information
Auto-Mask
Privacy
Sensitive masking
GDPR
Compliance
Privacy
Backup
Recovery
Data protection
Strong Encryption
All recorded data is encrypted with strong algorithms. Keys are securely managed.
Secure Communication
All communications between Recorder and server are encrypted with secure protocols.
Auto Masking
Sensitive inputs like passwords, card numbers and private fields are automatically masked.
GDPR Compliant
didka is designed to meet GDPR standards. Users have the right to access and delete data.
Secure Infrastructure
Servers in secure datacenters with limited access. Regular backup and disaster recovery.
Audit Log
Complete logging of all access and changes. Team access logs viewable.
Team Access Management
Access roles (Admin, Editor, Viewer) with different permission levels.
API Key Management
Unique API keys with rotation capability. IP-based access restriction.
Security FAQ
Is Didka GDPR compliant?
Yes, Didka is compliant with privacy standards including GDPR and provides full data control. Users have the right to access, delete and export their data at any time.
How is user data encrypted?
Didka uses AES-256 for encryption at rest and TLS 1.3 for encryption in transit. Encryption keys are managed separately from the data they protect.
Is private deployment available?
Yes, On-Premise deployment is available for organizations that need full data control. Contact the sales team to size the infrastructure for your traffic.
Where is didka data hosted?
Data is stored in secure, access-limited data centers with continuous monitoring. Traffic between the tracker and the server is always encrypted.
Are passwords and card numbers recorded in session replays?
No, sensitive fields are masked automatically before a session is stored. You can choose no masking, text masking or full masking, and full masking also hides images on sensitive pages.
Does didka support two-factor authentication?
Yes, two-factor authentication is supported so a stolen password alone cannot open your account. Combined with role-based access it limits who can view recordings.
How is team access controlled?
Roles such as admin, editor and viewer define who can watch replays, change settings or export data. Every access and configuration change is written to an audit log.
How often is data backed up?
Backups run regularly and are stored separately from the production database so they can be restored after an incident. Recovery procedures are tested as part of the operations routine.
Does didka track users across other websites?
No, didka only records behavior inside the sites where you install the tracker. No data is shared with third parties and recordings are never sold or used for advertising.
Can I exclude certain pages from recording?
Yes, you can exclude URLs, disable recording on sensitive pages and set data retention periods per project. These settings can be changed at any time from the dashboard.