External legal review required before public launch.This operational draft is intentionally written from the current Caspentra data architecture. The contracting legal entity, jurisdiction-specific lawful bases, final retention periods and formal privacy contact must be confirmed before deployment to real customers.
Privacy

Privacy Notice

Caspentra is designed to coordinate high-trust business setup, investment and company-management workflows. That can involve contact details, business information, account records and, after engagement, identity or corporate documents. This notice explains the intended handling model in plain language.

Information Caspentra may handle

  • Website and intake data: name, email, telephone/WhatsApp number, country, business activity, goals, timing and information you choose to include in an enquiry.
  • Account data: authentication identifiers, profile details, company membership and security events.
  • Case data: company information, tasks, status, advisor messages, compliance items and service-delivery records.
  • Documents: identity, corporate, employment, banking-readiness or other records requested for an agreed service. Access is intended to be role-controlled.
  • Billing data: invoices, payment status and reconciliation references. Card credentials are intended to remain with the selected payment provider rather than Caspentra.
  • Technical data: security, reliability and error metadata required to operate and protect the platform. Optional marketing analytics remain disabled until configured with an approved consent model.

Why information is used

Information is used to respond to enquiries, assess requested services, create and administer client workspaces, coordinate agreed professional or operational work, manage documents and deadlines, communicate about active cases, issue invoices, protect the platform, prevent abuse and meet applicable legal or compliance obligations.

Service providers and professional partners

Caspentra may use infrastructure, authentication, hosting, email, payment, document-security, analytics or professional-service providers where necessary for the agreed service. Access should be limited to what the provider or responsible professional needs. Final launch documentation must identify material processors/subprocessors and any relevant international data-transfer arrangements.

Case-specific legal, tax, immigration, banking or other regulated conclusions may be escalated to the appropriately responsible professional or partner. Caspentra does not treat AI output as a substitute for required professional review.

Retention and deletion

Data should be retained only for the period required to deliver the service, maintain legitimate business and compliance records, resolve disputes and satisfy applicable legal obligations. Final retention periods and deletion procedures must be approved before production launch.

Your choices and requests

Depending on applicable law and the relationship with Caspentra, you may have rights relating to access, correction, deletion, restriction, objection, portability or withdrawal of consent. The final notice will publish the formal privacy contact and any jurisdiction-specific rights or complaint route.

Security approach

The platform architecture uses private document storage, role-based authorization, server-controlled privileged operations, short-lived document links, staff MFA controls and a malware-scanning boundary. No security system eliminates all risk; production claims will be limited to controls that have actually been deployed and verified.

Return to Caspentra