effective date: march 6, 2026 | last updated: october 18, 2026
introduction
Hatch Labs Holdings LLC ("Hatch Labs," "we," "us," or "our") operates cutting-edge tools for human connection and verification. we are committed to protecting your privacy and being transparent about how we collect, use, and share your information.
key information:
- company: Hatch Labs Holdings LLC (Delaware LLC, EIN 39-2892314)
- address: 701 Tillery Street, Suite 12, Austin TX 78702
- contact: contact@hatchlabs.com
- ceo: Amanda Bradford
by using our services, you agree to the collection and use of information as described in this privacy policy.
1. information we collect
1.1 information you provide directly
account registration information:
- full legal name
- email address
- phone number
- date of birth
- gender identity
- location (city, state)
- profile photos
professional information:
- educational background and degrees
- current employer and job title
- industry and work experience
- professional achievements
- career aspirations
identity and income verification (required)
through our integration with Plaid, we collect the following information as a condition of joining our platform:
identity verification data:
- full legal name verification
- date of birth verification
- address verification
- government-issued id validation
- social security number verification (as required by Plaid)
financial account information:
- bank account information and balances
- income verification data
- employment verification
- asset verification data
- transaction history (limited to verification purposes)
note: all financial data collection is processed through Plaid, Inc., a trusted financial services partner. for information about how Plaid handles your data, please review Plaid's end user privacy policy.
1.2 information collected automatically
usage information:
- app usage patterns and feature interactions
- time spent on different sections
- profile views and connection activities
- search queries and filters used
- device information (type, operating system, browser)
technical information:
- ip address and location data
- device identifiers
- log files and error reports
- cookies and similar tracking technologies
- session information
2. how we use your information
2.1 primary service functions
membership verification and approval:
- verify your identity and professional status
- confirm income and asset information for membership eligibility
- maintain platform quality and exclusivity
- prevent fraud and ensure community safety
platform operation and matching:
- create and maintain your profile
- provide matching and connection services
- facilitate communication between members
- personalize your experience and recommendations
3. Plaid integration and financial data
3.1 Plaid partnership
Hatch Labs uses Plaid, Inc. to verify your identity and financial information as a requirement for membership. Plaid is a trusted financial technology company that enables secure connections to your financial institutions.
what Plaid collects:
- account information (account numbers, routing numbers, balances)
- identity information (name, address, phone number, email)
- transaction data (limited to verification purposes)
- income and employment information
how Plaid protects your data:
- bank-level security with 256-bit encryption
- multi-factor authentication required
- SOC 2 Type II compliance
- regular security audits and monitoring
4. how we share your information
4.1 we do not sell your information
we do not sell, rent, or trade your personal information to third parties for their marketing purposes. your data is valuable to us because it helps us provide better services to you, not because we profit from sharing it with others.
4.2 service providers and business partners
we share information with trusted service providers who help us operate our platform:
infrastructure and technical services:
- Supabase: database hosting and management (SOC 2 compliant)
- Plaid: identity and financial verification services
- Cloudflare: content delivery and security services
- github: code repository and deployment services
5. text messaging (sms)
Hatch Labs Holdings LLC operates the IHerebyCommit (I Hereby Commit) text messaging program for users of iherebycommit.com.
- opt-in only: we only send text messages to people who opt in through an optional, unchecked sms consent checkbox on the signup form at iherebycommit.com. consent to receive texts is not a condition of signup or purchase.
- message types: account notifications, verification codes, study check-ins, insights, matches, event updates, and occasional offers.
- frequency and cost: message frequency varies. message and data rates may apply.
- opt out and help: reply stop to any message to opt out at any time. reply help for help, or email contact@hatchlabs.com.
- no sharing: no mobile information will be shared with third parties or affiliates for marketing or promotional purposes. mobile phone numbers and sms opt-in data and consent are never shared with or sold to any third parties.
full program details are in the IHerebyCommit terms and IHerebyCommit privacy policy. questions: contact@hatchlabs.com.
6. data retention and deletion
6.1 retention periods
active account data:
we retain your personal information for as long as your account is active and you continue to use our services.
financial verification data:
we retain financial verification data for a minimum period required by financial service regulations, typically:
- identity verification records: 5 years after account closure
- income verification records: 3 years after account closure
- anti-fraud data: 7 years after account closure
6.2 account deletion
upon account deletion:
- profile information deleted within 30 days
- financial verification data deleted within 30 days (subject to legal requirements)
- messages and communications deleted within 30 days
- anonymous usage analytics may be retained
7. your privacy rights
7.1 access and portability
you have the right to request information about what personal data we have collected about you, including categories of information, sources, and purposes for collection.
7.2 california consumer privacy act (ccpa) rights
if you are a california resident, you have additional rights under the ccpa:
- right to know: request specific information about how we collect, use, and share your personal information
- right to delete: request deletion of your personal information
- right to opt-out: opt out of the sale of your personal information (note: we do not sell personal information)
- right to non-discrimination: we will not discriminate against you for exercising your rights
8. security measures
8.1 technical safeguards
data encryption:
- all data encrypted at rest using AES-256 encryption via Supabase
- all data in transit protected with tls 1.2 or higher encryption
- database-level row security to limit data access
- encryption key management through secure cloud infrastructure
access controls:
- multi-factor authentication required for all critical system access
- role-based access control with principle of least privilege
- regular access reviews and immediate deactivation upon termination
- administrative access logging and monitoring
9. changes to this privacy policy
we may update this privacy policy to reflect changes in our services, business practices, or applicable laws. for significant changes:
- email notification to active users at least 30 days before changes take effect
- prominent notice on our website and platform
- clear explanation of what has changed and why
- opportunity to review and accept new terms
CASA assessment in progress
document version: 1.0
effective date: march 6, 2026 | next review: march 6, 2027
purpose and scope
this information security policy establishes the framework for protecting Hatch Labs Holdings LLC's information assets, systems, and data. this policy ensures the confidentiality, integrity, and availability of information and supports compliance with applicable legal, regulatory, and contractual requirements.
company overview:
- legal entity: Hatch Labs Holdings LLC (Delaware LLC, EIN 39-2892314)
- primary product: amandaslist — a verified membership network for high-achieving professionals
- address: 701 Tillery Street, Suite 12, Austin TX 78702
- contact: contact@hatchlabs.com
- ceo: Amanda Bradford
1. access control and identity management
1.1 user access management
- principle of least privilege: users are granted minimum access necessary to perform their job functions
- role-based access control (rbac): access permissions are assigned based on predefined roles and responsibilities
- regular access reviews: user access is reviewed quarterly and adjusted based on role changes or termination
multi-factor authentication (mfa)
mandatory mfa is required for:
- all critical systems (Supabase, Google Workspace, Mercury Bank)
- user access to Plaid link for identity verification
- administrative access to any system containing user data
- remote access to company resources
1.2 account management
- unique user accounts for each individual
- strong password requirements (minimum 12 characters, complexity requirements)
- account lockout policies after failed login attempts
- immediate account deactivation upon termination or role change
- shared accounts are prohibited
2. data classification and handling
2.1 data classification levels
- public: information intended for public disclosure (marketing materials, public website content)
- internal: information for internal business use (internal policies, business plans)
- confidential: sensitive business information requiring protection (user data, financial information)
- restricted: highly sensitive information requiring the highest level of protection (authentication credentials, encryption keys, sensitive personal data, financial account data)
personal data protection
given amandaslist's collection of personal and financial data through Plaid:
- all personal data classified as confidential or restricted
- financial account data classified as restricted
- identity verification data classified as restricted
- special handling procedures for financial data per applicable regulations
3. encryption standards
3.1 data encryption at rest
- primary database: AES-256 encryption via Supabase hosted postgresql
- minimum standard: AES-256 encryption for all databases containing personal or financial data
- key management: encryption keys managed by Supabase with industry-standard key rotation
- scope: all user data, financial data from Plaid, identity verification data, and business-critical information
3.2 data encryption in transit
- minimum standard: tls 1.2 or higher for all data in transit
- implementation: tls 1.3 where supported, with perfect forward secrecy
- api communications: all api calls to third-party services (Plaid, Supabase) use tls 1.2+
- web application: https enforced with hsts headers
- certificate management: automated certificate renewal via Cloudflare
4. incident response procedures
4.1 incident response team
- incident commander: ceo (Amanda Bradford)
- technical lead: development team lead (currently ceo)
- external resources: cybersecurity consultant (as needed)
- legal counsel: external legal counsel (as needed)
4.2 response procedures
- detection and analysis (0-1 hour): identify and verify the incident, assess scope and potential impact
- containment (1-4 hours): immediate containment of the incident, prevent further damage
- eradication and recovery (4-24 hours): remove threat and vulnerabilities, restore systems
- post-incident activities (24-72 hours): lessons learned review, update policies, prepare incident report
communication and notification
- internal notification within 2 hours of confirmed incident
- customer notification per applicable regulations (ccpa, etc.)
- regulatory notification as required by law
- vendor notification for third-party service impacts
5. vulnerability management
5.1 vulnerability assessment
- automated dependency scanning via github dependabot
- regular security assessments of critical systems
- third-party security testing annually or after major changes
- continuous monitoring for new vulnerabilities
5.2 patch management
- critical security patches applied within 72 hours
- high-priority patches applied within 7 days
- regular patches applied within 30 days
- emergency patching procedures for zero-day vulnerabilities
6. third-party vendor management
Plaid
identity/financial verification
SOC 2 Type II compliant
Supabase
database/backend
SOC 2 compliant
Cloudflare
cdn/security
enterprise-grade protection
github
code repository
automated security scanning
6.1 vendor requirements
- SOC 2 Type II compliance preferred for critical vendors
- contractual security requirements and liability provisions
- regular security assessments and compliance verification
- incident notification requirements
- data processing agreements (dpa) where applicable
7. business continuity and disaster recovery
7.1 backup and recovery
- database backups: automated daily backups via Supabase with point-in-time recovery
- application code: version control and automated deployment pipelines
- configuration data: infrastructure as code with version control
- recovery testing: quarterly backup restoration testing
7.2 business impact analysis
- critical business functions identified and prioritized
- recovery time objectives (rto) and recovery point objectives (rpo) defined
- dependencies on third-party services documented
- alternative processing capabilities identified
8. compliance and legal requirements
8.1 regulatory compliance
- SOC 2 Type II: alignment with SOC 2 principles for service organizations
- california consumer privacy act (ccpa): privacy rights for california residents
- state privacy laws: compliance with applicable state privacy regulations
- financial data protection: compliance with financial data protection requirements
8.2 audit and assessment
- annual security assessment by qualified third party
- internal security reviews quarterly
- compliance audits as required by regulations
- documentation retention for audit purposes
9. employee security requirements
9.1 security awareness training
- annual security awareness training for all personnel
- specialized training for developers and administrators
- phishing awareness and testing program
- security policy acknowledgment required
9.2 acceptable use
- approved use of company systems and data
- prohibition of unauthorized software installation
- personal use limitations and guidelines
- social media and public communication guidelines
10. policy governance
10.1 policy review and updates
- annual review: complete policy review and update cycle
- triggered reviews: updates based on incidents, technology changes, or regulatory changes
- approval process: ceo approval required for all policy changes
- communication: policy changes communicated to all affected personnel