How Cresva handles your data
Cresva, Inc., 131 Continental Dr, Suite 305, Newark, DE 19713, USA.
Your data
Your data is stored in a database encrypted at rest by Neon (AES-256) and in files encrypted at rest by Vercel. The access tokens for the platforms you connect are encrypted again by Cresva with AES-256-GCM. Everything is served over TLS 1.2 or 1.3. Our cache is encrypted in transit but not at rest, so it holds no personal data of your customers.
Every request is checked against your role in the brand and company it reads, so one customer's data is not served to another. Pooled figures other brands see carry no brand, company or person, need at least 5 brands from 3 companies, and use only sources whose platform terms allow it.
Changes to your accounts
Cresva reads your ad and store accounts and can make changes in them through each platform's own API, at the autonomy level you choose. At Recommend only it changes nothing. At Ask first every change waits for your approval. At Safe actions, changes that can be undone run on their own, and a change that cannot be undone always waits for a person. At every level, anything that could raise spend above what you approved asks first.
Signing in
Sign in with Google, Google Workspace included, Microsoft, a passkey or a link sent to your email.
A passkey or a Google or Microsoft account that enforces its own second factor protects sign-in. Requiring multi-factor sign-in for everyone in a workspace is not available yet.
Single sign-on through your own identity provider (SAML or OIDC, for example Okta or Microsoft Entra ID) and SCIM user provisioning are not available yet.
Where it runs
The application runs on Vercel and the database runs on Neon, and both hold SOC 2 Type 2 attestations. Cresva has no SOC 2 or ISO 27001 report of its own.
Reporting a security issue
Write to hello@cresva.ai. The disclosure page says what we promise and what is in scope.
Service status
Uptime and incidents are published on the status page.