Security

How we keep your data safe

Security is not an afterthought at Amridata. Here's exactly what we do to protect your account, your files, and your data.

Protections

Security measures in place

✓
HTTPS everywhere
Transport
All traffic between your browser and Amridata is encrypted using TLS. HTTP requests are automatically redirected to HTTPS.
✓
Bcrypt password hashing
Authentication
Passwords are never stored in plain text. We use bcrypt with a high cost factor (12), making brute-force attacks impractical even if our database were compromised.
✓
CSRF protection
Forms
Every form submission is protected by a unique CSRF token. Tokens are rotated on use and regenerated on session start.
✓
SQL injection prevention
Database
All database queries use PDO prepared statements with parameterized inputs. We never interpolate user input into SQL strings.
✓
XSS prevention
Output
All user-supplied content is HTML-escaped before rendering. Content Security Policy headers further restrict script execution.
✓
Secure session management
Sessions
Sessions use HttpOnly, SameSite=Lax cookies. Session IDs are regenerated after login and periodically during an active session to prevent session fixation.
✓
Rate limiting
Brute force
Login attempts, password resets, and contact form submissions are rate-limited to prevent brute-force and spam attacks.
✓
Upload validation
Uploads
Uploaded files are validated against allowed MIME types and extensions. Files are stored outside the web root and served through a controlled download endpoint — not directly from a public URL.
✓
API key isolation
API Keys
Third-party API keys (including the Gemini AI key) are stored in server-side environment variables and never sent to the browser. All API requests are proxied through the server.
✓
Security headers
Headers
HTTP response headers include: Content-Security-Policy, X-Frame-Options (deny), X-Content-Type-Options, Referrer-Policy, and Permissions-Policy.
✓
Directory listing disabled
Server
Apache directory listing is disabled. Only files explicitly served by the application are accessible.
✓
Sensitive files blocked
Server
.env files, .git directories, and composer files are blocked at the server level and cannot be accessed via HTTP.
Your uploaded data

What happens to files you upload

✓
Stored securely
Uploaded files are stored in a non-public directory on the server. They are not accessible via a direct URL — the application controls all file access and enforces ownership.
✓
Never shared
Your data is never shared with other users, sold to third parties, or used for advertising purposes.
✓
AI data minimization
AI requests include dataset structure, statistics, sample values, and up to five sample rows rather than the full uploaded dataset.
✓
Automatically deleted
Temporary sessions: 24 hours. Free Account: 30 days after last access. You can also delete any dataset immediately from the dashboard.
Responsible disclosure

Found a vulnerability?

If you discover a security vulnerability in Amridata, please report it responsibly. Do not publicly disclose the issue until we've had a chance to investigate and fix it.

Contact us through the contact form with a subject line starting with "Security: " and a description of the vulnerability, the steps to reproduce it, and the potential impact. We will acknowledge your report within 48 hours.

Report a vulnerability →