Privacy Policy

1. Scope and operator responsibility

This policy applies to IMMIOOO accounts, voluntary immigration profiles, AI conversations, community activity, professional applications and policy-alert preferences. The organization deploying this platform is the data controller for its production service and must publish its registered legal name, physical address, privacy contact and any required EU, UK or local representative before public launch.

Local privacy rights remain unaffected by this policy. No single document can guarantee compliance in every country; deployment-specific legal, hosting, transfer and processor review is required.

2. Data we collect and data we refuse to require

• Account data: name, email, hashed password, role, plan and account status.
• Voluntary profile data: nationality, residence, age range, education, occupation, work experience, language, broad family and budget ranges, objectives and destination preferences.
• User content: questions, AI responses, community posts, comments, reactions, reports and professional credentials.
• Technical data: session identifiers, security events, review records and limited abuse-prevention logs.
• We do not require passport numbers, national identity numbers, bank statements or sensitive document uploads for ordinary registration or AI use. Do not submit them through free-text fields.

3. Why we use data and legal bases

We use account data to provide secure authentication and perform the service contract. Voluntary profile and pathway data are processed with consent for information exploration. Community posts are processed to provide the requested public forum. Security, audit and anti-abuse records support legitimate interests and legal obligations. Professional credentials are processed for the requested verification and to protect the public.

Where GDPR or UK GDPR applies, consent can be withdrawn at any time without affecting prior lawful processing. Where another jurisdiction requires a different basis, the deployment operator must document it before enabling the relevant processing.

4. AI and DeepSeek processing

When you use Immigration AI, your question and the relevant structured policy records are sent to the configured DeepSeek API to generate a response. The API key is held server-side. Signed-in conversations are stored so you can revisit or delete them; public visitor conversations are not attached to an account.

IMMIOOO does not use private conversations or immigration profiles for advertising and does not intentionally use them to train its own models. Any provider-side processing, retention or training controls must be verified under the production DeepSeek enterprise terms before launch. Do not enter sensitive identifiers or documents.

5. Sharing and international transfers

We share data only with service providers needed to operate the requested service, with public professional regulators when verification is requested, with other users when you deliberately publish community content, and where legally required. We do not sell personal information.

DeepSeek and hosting providers may process data in other countries. Before production use in a restricted region, the operator must assess transfer mechanisms, data-residency needs and government-access risks, and must offer a regional configuration or disable the affected feature where an adequate lawful transfer cannot be established.

6. Retention and deletion

• Accounts and voluntary profiles: while the account is active or until you delete them.
• Sessions: up to 30 days unless signed out or expired.
• Private AI conversations: until you delete the conversation or account.
• Community contributions: until deleted through account deletion or a moderation process; legal holds may apply.
• Contact and complaint records: ordinarily up to 24 months, subject to dispute and legal needs.
• Policy versions and professional verification decisions: retained for provenance and public-protection audit, with personal data minimized.
• Security and audit logs: retained only as long as proportionate to security and legal obligations. The production operator must implement and document scheduled deletion jobs.

7. Your rights and controls

Depending on location, you may have rights to access, correct, export, delete, restrict or object to processing, withdraw consent, and complain to a regulator. The dashboard provides profile deletion, JSON export, optional-consent controls and account deletion. Other requests can be submitted through Contact & complaints.

We may need proportionate identity verification before completing a request. We will not require excessive identity documents for ordinary requests.

8. Security and breaches

The implementation uses password hashing, HttpOnly SameSite session cookies, role checks, ownership checks, rate limiting, data minimization and security headers. Production deployment must add HTTPS, encrypted backups, secret rotation, monitoring, patching, least-privilege operations and an incident-response process.

No system is perfectly secure. Suspected breaches must be assessed and notified to regulators and affected people within applicable local deadlines.

9. Children and changes

The service is not directed to children under 16. Where local law sets a different digital-consent age, that stricter rule applies. Do not create an account without required parental authorization.

Material changes to this policy should be announced with a new effective date and, where required, fresh consent. Historical policy versions should be retained by the operator.