Security Overview
Safiq handles passports, financial proof, family records, and other sensitive administrative material. This page summarizes the security controls and product boundaries Safiq relies on today.
1. Authentication
Safiq uses secure sign-in flows such as email/password, Google, Apple, and Supabase Auth where configured. Protected backend routes require valid user authorization before they can access account-scoped data.
2. Document storage
The document vault keeps uploaded files scoped to the signed-in user and authorized product flows. Backend cleanup removes stored document paths during account deletion.
3. Payments
Safiq does not store raw payment card details. Payment handling is delegated to providers such as Stripe, PayPal, Apple, or Google depending on platform and purchase flow.
4. Data minimization and deletion
Safiq collects the data needed to support relocation workflows, subscriptions, support, and security. Signed-in users can delete their account directly inside the app, and public deletion guidance is available through the account deletion page.
5. User best practices
- Use a strong password and protect the email account tied to Safiq.
- Upload only documents you need for the workflow you are preparing.
- Review AI-generated or summarized output before sharing it with an authority or third party.
- Delete outdated files you no longer need in the workspace.