AES-256 encryption everywhere
Every byte is encrypted in transit (TLS 1.3) and at rest (AES-256). Database, file storage, and backups all encrypted.
Security & Compliance
Every PropOS account is encrypted, audited, and role-segregated by default. Compliance with Loi 09-08 (Morocco), GDPR (EU), and Code de Commerce retention is built into the product, not stapled on.
Every byte is encrypted in transit (TLS 1.3) and at rest (AES-256). Database, file storage, and backups all encrypted.
A syndic sees their buildings. A resident sees their unit. Enforced by Firebase security rules and re-checked on every server action.
Every state change writes an audit log entry with actor + timestamp + before/after. AGM presidents can review the full trail.
AI calls go through our backend. Your resident names, addresses, and financial figures never appear in third-party logs.
No Google Analytics, Meta Pixel, or hotjar on /pricing, /features, /contact. Only first-party privacy-respecting analytics.
Database and file storage backed up daily, retained for 30 days. RPO ≤ 24h, RTO ≤ 4h on Professional and SmartSyndic plans.
Legal & regulatory
PropOS is built by Moroccan engineers who read the laws. Here's how each regulation maps to a concrete feature you can see in the product.
Article 7 right of access (one-click JSON export), Article 8 rectification, Article 9 erasure (30-day soft delete). Local CNDP registration in progress.
AGM workflows, syndic election traceability, account-of-charges format, Mise en Demeure compliance with article 36 — built into the data model.
For Moroccan buildings with EU residents or owners abroad: full GDPR rights (access, rectification, erasure, portability), DPA available on request, no transfer to non-adequacy countries.
Accounting records (invoices, transactions, AGM minutes) retained for 10 years per Moroccan Code de Commerce. Audit log preserved separately even after a user requests account deletion.
Frequently asked
Firebase / Google Cloud, region europe-west1 (Belgium) by default. We can configure other regions on enterprise plans. No data leaves the EU/Morocco corridor unless you enable a third-party integration that requires it (and you control which).
No engineer or support agent can read raw database contents in normal operation. Production access requires a break-glass procedure that is logged and reviewed weekly. Customer support cases never include resident PII unless you explicitly share it.
Your data is yours. Export to JSON/CSV from /settings/security. We retain accounting records for 10 years (legal minimum) but PII is deleted within 30 days of cancellation. No lock-in.
Yes — responsible disclosure at security@propos.app. Critical vulnerabilities get a same-day acknowledgement. We publish CVE-style advisories for any incident affecting customer data.
PropOS uses Firebase Authentication; passwords are stored as scrypt hashes (industry-leading slow function), salted per user. We never see the cleartext password. Optional 2FA via TOTP.
We log the action (which feature called the AI), the actor, and the timestamp — never the prompt content or response content. OpenAI/DeepSeek's own policies apply to what they store on their side; both offer zero-data-retention modes that we use by default on enterprise plans.
Report a vulnerability
Email security@propos.app with a description and reproduction steps. We acknowledge within 24 hours, fix critical issues within 7 days, and credit you in our public advisory log if you want.
Please do not file a public GitHub issue or contact support — security reports stay private until a fix is shipped.
What we consider in scope
Coordinated disclosure window: 90 days before public CVE.
See the security model in action. Start a free 30-day trial — no card.