Skip to content
Prosvera AI

Security

This page describes how Prosvera AI approaches application security, data isolation, access control and operational practices for the marketing site and the hosted application at platform.prosvera.space.

Last updated: 22 September 2026

1. Security principles

Prosvera is designed as a multi-tenant B2B SaaS product. Security goals include protecting customer workspace data, limiting access to least privilege, keeping secrets out of client code, and reducing the risk of automated abuse in prospecting workflows.

  • Organization-scoped tenancy for workspace data.
  • Human approval before outreach is sent from campaigns.
  • TLS for data in transit on public endpoints.
  • Role-aware access inside the application where roles are configured.

2. Application and tenancy

Authenticated product traffic is served from the application environment. Customer records, campaign state and organization settings are intended to be isolated by organization identifiers so one workspace cannot read another’s data through the normal product APIs.

Marketing pages on prosvera.space are public informational content. Authenticated workspaces live on the platform hostname. Do not treat marketing pages as a control plane for production credentials.

3. Authentication and sessions

  • Users authenticate with credentials associated with their account.
  • Sessions are established after successful sign-in and should be kept confidential on shared devices.
  • Organization owners can manage membership for their workspace.
  • We recommend unique passwords and careful handling of invite links.

4. Data in transit and at rest

Public web traffic is protected with HTTPS/TLS. Application databases and object storage are hosted in the selected cloud or infrastructure environment with access restricted to service roles. Encryption at rest depends on the underlying provider defaults and our deployment configuration.

5. Secrets and integrations

API keys for discovery, contact and email providers are stored as organization or environment secrets for server-side use. They are not intended to be exposed in public marketing pages or client-side bundles. You remain responsible for rotating keys you supply and for the security of third-party accounts you connect.

6. Network and infrastructure controls

  • Services are deployed behind reverse proxies / load balancers in typical production setups.
  • Administrative access to hosts and dashboards is limited to authorized operators.
  • Backups and recovery procedures follow the infrastructure provider’s capabilities and our operational runbooks.
  • Dependency and container images are kept under versioned deployment practices.

7. Application safeguards relevant to prospecting

  • Draft outreach is held for human approval before send.
  • Campaign and suppression settings in the product are meant to reduce unwanted messaging.
  • Provider calls are made from the server side using configured credentials.
  • Rate limits and plan quotas reduce runaway automation against third-party APIs.

8. Logging, monitoring and incident response

We retain operational logs needed to run and debug the Service, investigate abuse, and respond to incidents. If we become aware of a security incident that materially affects your workspace data, we will notify affected account owners as required by applicable law and our incident process.

9. Customer responsibilities

  • Protect account passwords and workspace invite links.
  • Grant least-privilege access to teammates.
  • Configure third-party providers securely and rotate compromised keys.
  • Review AI drafts before approval and respect consent / unsubscribe rules.
  • Report suspected unauthorized access promptly via Contact.

10. Vulnerability reporting

If you believe you have found a security vulnerability in Prosvera, please report it through the Contact page with enough detail for us to reproduce the issue. Do not publicly disclose exploit details before we have had a reasonable chance to investigate and remediate.

11. Subprocessors and third parties

Hosting, email, analytics and data providers may process limited technical or customer data as needed to operate the Service. Those parties are bound by their own security and contractual terms. See the Privacy Policy for categories of processing.

12. Continuous improvement

Security controls evolve with the product. This page summarizes current practices for customers and prospects; it is not a warranty or certification statement. Formal SOC/ISO reports, DPAs or questionnaire responses can be requested through Contact when available for your plan.