Home / Trust & security

Built tobe trusted.

A plain description of what we collect, where it lives, who touches it and how it is protected. We list what we actually do and do not claim certifications we do not hold.

What we collect

  • Enquiry form: the name, email, organisation, industry, project description and preferences you submit, plus first-touch attribution (landing page, referrer, UTM tags) kept in your browser session and sent only with the form.
  • Newsletter: your email address, with a one-click unsubscribe in every message.
  • No advertising trackers. We do not set tracking cookies. If we enable analytics it will be a cookieless, privacy-friendly tool, and this page will say so.

Where it is processed

ProviderPurpose
VercelWebsite hosting and delivery
Turso (libSQL, AWS Mumbai region)Database for leads, subscribers and CRM records
ResendSending the emails you request or agree to receive

How we protect it

  • HTTPS everywhere with HSTS, a strict Content-Security-Policy and standard hardening headers.
  • Staff access is role-based. Roles are checked on every request and every action, and changes apply immediately.
  • Passwords are salted and hashed with bcrypt; two-factor authentication (authenticator app) is available and recommended for administrators.
  • Sign-in and form endpoints are rate-limited and protected against automated abuse. Admin actions are written to an audit log.
  • Marketing email always includes an unsubscribe link, honours a suppression list, and supports one-click unsubscribe.
  • Spam enquiries are kept for review for 90 days and then deleted automatically.

Your rights

You can ask us to access, correct or delete the data we hold about you, or to stop emailing you, by writing to connect@convoandconnect.com. We respond within a reasonable time and confirm when it is done. See our privacy policy and terms.

Reporting a vulnerability

If you believe you have found a security issue, email connect@convoandconnect.com with the details. Our contact is also published in security.txt. Please give us reasonable time to fix an issue before disclosing it, and do not access data that is not yours.

Accessibility

We aim for WCAG 2.2 AA: keyboard navigation, visible focus, sufficient contrast, reduced-motion support and descriptive labels. We have not yet completed a formal third-party audit. If something is hard to use, tell us and we will fix it.

What we do not claim

We do not currently hold SOC 2, ISO 27001 or similar certifications. When that changes, it will be stated here with the scope and date.