SOC2C

Is this your company? Buyers are checking Neosync here. Claim neosync.dev free to control the listing, earn the badge buyers trust, and see who's evaluating you.

Claim free
Neosync logo

Neosync

Trust level
Listed
Unverified

Sourced from public information. Not yet verified by the company.

Neosync is SOC 2 Type II compliant.

Framework
Auditor
Last report
Renewal
View official trust center ↗

About

Open Source Anonymization and Synthetic Data For Developers

Compliance & infrastructure

Hosting
AWS
Data handled
Customer personally identifiable informationEmployee personally identifiable informationCredit card informationPersonal health information

Documents

2

Subprocessors

12
  • A
    Amazon Web Services · Cloud provider
  • D
    Datadog · Cloud monitoring
  • G
    GitHub · Version control
  • G
    Google Workspace · Identity provider
  • S
    Slack · Collaboration
  • L
    Linear · Collaboration
  • N
    Notion · Collaboration
  • R
    Rippling · Employee management
  • V
    Vanta · Security
  • V
    Vercel · Engineering
  • C
    Calendly · Collaboration
  • Z
    Zoom · Collaboration

Compliance leadership

The person who leads Neosync's SOC 2 isn't listed yet. Claim this profile to add it.

Penetration test

Unknown. Neosync's penetration test vendor isn't listed yet.

Claim this profile to add it.

This listing is partial

6/11 details · 55%

SOC2C shows the verified essentials. 5 details are not yet provided by the company. Trust centers list more, so we invite the owner to fill the gaps here.

  • Auditorraises trust
    Add the CPA firm that issued your SOC 2 so buyers can verify who signed it.
  • Report dateraises trust
    Add your most recent report period so buyers see how current your SOC 2 is.
  • Renewal date
    Add your renewal window so buyers know your coverage is active.
  • Other certifications
    List your other frameworks (ISO 27001, HIPAA, PCI DSS) the way your trust center does.
  • Security controls
    Confirm key controls (encryption, MFA/SSO, annual pen test, BCP/DR) buyers screen for.
Claim free to control your listing

Verify your work email to take ownership, earn the badge buyers trust, and add the details that win deals.

Frequently asked

Is Neosync SOC 2 compliant?
Neosync is SOC 2 Type II compliant. On SOC2C this listing is Listed.
Is Neosync SOC 2 Type I or Type II?
Neosync is SOC 2 Type II compliant. A Type II report covers how security controls operated over a period (typically 3 to 12 months), a stronger signal than a point-in-time Type I.
Can I use Neosync's SOC 2 for a vendor risk assessment?
Yes. Neosync's SOC 2 status, frameworks, auditor, and renewal timing are on SOC2C for vendor risk and security reviews. Request the underlying report through SOC2C to complete your third-party risk file.
Is Neosync penetration tested?
Neosync hasn't listed its penetration testing on SOC2C yet. SOC 2 Type II programs typically include periodic third-party penetration tests; the company can add who performed theirs.
Can I get Neosync's SOC 2 report?
Neosync's SOC 2 report is available on request. Request access through SOC2C and we coordinate the company-side NDA and delivery.

Answers published by Neosync

Reproduced from Neosync's own trust center. These are the company's statements about its security practices — SOC2C has not tested or verified them, and they may have changed since we last read the page. Check the source ↗

Do you encrypt data at rest?
Yes, all data that we persist is encrypted at rest. Data that is stored in AWS is encrypted using AWS KMS.
Where can I find information about Neosync's uptimes and downtimes?
We recommend checking out our Status Page. This will give you the ability to subscribe for updates, view uptimes, be informed of any outages, and view historical data.
Where are your servers located?
Neosync's servers are located in AWS, with options for data residency in the US or EU regions.
How does Neosync handle secrets?
Encryption keys are managed via AWS Key Management System (KMS). KMS stores key material in Hardware Security Modules (HSMs), which prevents direct access by any individuals, including employees of Amazon and Neosync. The keys stored in HSMs are used for encryption and decryption via Amazon’s KMS APIs. Application secrets are encrypted and stored securely via AWS Secrets Manager, Parameter Store, and as Kubernetes Secrets (encrypted with KMS) and access to these values is strictly limited.
I found a security bug.
If you found a security bug, please email security@neosync.dev