Security & Data Protection | MaschinMind
Hosting, access controls, encryption, backups and data protection at MaschinMind.
Concrete information for your security review. This overview distinguishes implemented controls, recorded verification and service commitments agreed in your contract.
Information reviewed: 20 September 2026. Infrastructure evidence: August 2026; this is not a live infrastructure audit.
Where are the data hosted?
Our recorded configuration places the API on Render in Frankfurt and the PostgreSQL database on Neon in AWS Frankfurt. Independent backups use a private Cloudflare R2 bucket with EU jurisdiction. Supporting processing, including provider support and service metadata, may involve locations outside the EEA; EU hosting does not mean that every processing activity takes place exclusively in the EU.
How is access separated?
Customer organisations are logically separated. The application checks organisation membership and permissions on the server. Roles control access to functions and records. Platform administration has privileged access; the support workflow records the reason, expiry and start/end of support sessions. Operational history records actors and relevant events.
How are accounts protected?
Passwords are stored as bcrypt hashes. Authentication sessions expire and logout revokes the current session. TOTP multi-factor authentication and recovery codes are implemented for the platform owner. Customer administrators and operators do not currently have a self-service MFA activation flow. MFA is not represented as mandatory for all accounts.
Are data encrypted?
Public application connections use HTTPS/WSS. Render provides managed TLS for public endpoints. Neon states that database data are encrypted at rest with AES-256 and connections use TLS 1.2 or later. Independent database backups are additionally encrypted with age before upload. These are transport and storage protections, not end-to-end encryption.
How do backups work?
A daily encrypted backup job is configured. Recorded controls specify a private EU R2 destination, a 30-day object lock and lifecycle deletion after 90 days for database backups. A local status record reports a successful run on 14 September 2026. Continuous daily execution has not been independently verified in this review; the automation depends on a Windows workstation.
Has recovery been tested?
On 16 August 2026, an encrypted R2 backup was downloaded, decrypted, integrity-checked and restored into a separate Neon test branch. The recorded database recovery drill passed. Documented recovery objectives are RPO 24 hours and RTO 4 hours, with RTO measured from the documented decision to start disaster recovery. These objectives are not a measured guarantee of continuous compliance; applicable commitments are defined in the customer agreement.
Can we export or delete data?
Authorised administrators can export organisation data as JSON, including document content encoded as Base64. Export and removal of a test operator’s identifying name and email were verified in production on 15 August 2026. This does not establish immediate deletion from all records and backups. Contact us to agree export handling, retention and deletion requirements before transferring an export.
What availability is promised?
The application provides service and database health checks. No monthly uptime percentage is guaranteed by this overview. Support, availability commitments and any service credits are governed by the applicable customer agreement.
DPA, providers and security questions
DPA documentation exists for pilot and SaaS agreements and is completed for each customer. Our supplier records cover Render, Neon and Cloudflare; the applicable list must also reflect any email or other services enabled for the deployment. Request the applicable DPA, provider information or report a security concern at privacy@maschinmind.com.