IntimID Privacy Policy

Your privacy is our highest priority. Learn how we protect your most sensitive health information with industry-leading security measures.

Last Updated: July 2025

Privacy-First by Design

IntimID was built from the ground up with your privacy as the core principle. We believe that your sexual health information is among the most personal data you have, and it deserves the highest level of protection.

🔒

Hybrid Privacy Architecture

Health data stays encrypted on your device only. Account management and verification use secure cloud services with technical controls preventing linkage to your health information.

🛡️

HMAC-SHA256 Encryption

Your sensitive health data is protected with HMAC-SHA256 encryption with authentication and secure random initialization vectors.

🌐

Secure Cloud Services

We use Supabase for account management and partner verification. Only your email address and anonymous IntimID are stored in cloud services - never your health data.

👤

Pseudonymous Privacy

Your email creates an account, but your unique user ID is never linked to your email or personal data.

0
Health Data Sharing
100%
Local Health Storage
HMAC-SHA256
Encryption Standard

1. Information We Collect

Account Information

IntimID requires email address registration to create and maintain your account. We implement a pseudonymous system with the following technical safeguards:

  • Your email is stored separately from all health-related data
  • A cryptographically generated, anonymous user identifier is created for your account
  • Technical and administrative controls prevent linking your user ID to your email
  • All health data is exclusively associated with your anonymous user identifier
  • Email is retained only for account authentication and recovery purposes

Information We Do Not Collect

IntimID is designed with privacy by design principles. We do not collect, store, process, or transmit:

  • Personal identifying information beyond email address
  • Health test results or medical information on our servers
  • Sexual activity data or partner information on our servers
  • Precise location data or GPS coordinates
  • Device advertising identifiers or fingerprinting data
  • Behavioral analytics or usage tracking linked to personal identity
  • Biometric data (processed locally only)

Local Device Storage

The following sensitive information is processed and stored exclusively on your device using platform-specific secure storage (iOS Keychain/Android Keystore):

  • STD test results and dates
  • Sexual activity logs and risk assessment data
  • Partner verification information (encrypted)
  • Health analytics and trend calculations
  • Application preferences and settings
  • Biometric authentication templates

Technical Telemetry (Limited)

For application stability and security purposes only, we may collect minimal, non-personal technical information:

  • Application crash reports (anonymized, no personal data)
  • General usage statistics (aggregated, non-identifiable)
  • Security incident detection (for fraud prevention)

Important: Any technical data collected is processed separately from your account information and cannot be linked to your identity or health data.

2. Data Storage & Security

Data Storage Architecture

IntimID uses a hybrid privacy architecture designed to maximize both security and functionality:

  • Local Health Data: All STD test results, sexual activity records, and personal health information are encrypted and stored exclusively on your device using HMAC-SHA256 encryption.
  • Cloud Account Management: Your email address and anonymous IntimID are stored securely on Supabase cloud services for account functionality and partner verification.
  • Technical Separation: Your health data and account information are kept separate by design - your anonymous IntimID cannot be linked back to your email address or personal identity.
  • No Health Data Transmission: Your sensitive health information never leaves your device and is never transmitted to our servers or any third-party services.

Encryption Standards

  • HMAC-SHA256 Encryption: Health data encrypted with HMAC-based authenticated encryption using cryptographically secure random initialization vectors
  • Local Secure Storage: Device-specific encrypted storage using Flutter Secure Storage with hardware security module integration where available
  • Authentication Security: All encrypted data includes authentication tags to prevent tampering and ensure data integrity
  • Key Management: Master encryption keys generated using cryptographically secure random number generation and stored in device secure storage

Cloud Service Providers

  • Supabase: Provides account authentication, user management, and partner verification services. Supabase is SOC 2 Type II compliant and uses industry-standard security practices.
  • Data Minimization: Only essential account data (email address and anonymous IntimID) is stored in cloud services
  • Geographic Location: Supabase servers are located in secure data centers with appropriate data protection regulations

Data Isolation & Access Controls

Multiple technical safeguards prevent unauthorized access:

  • Health data isolated from other applications using platform security features
  • Biometric authentication required for application access
  • Automatic session timeouts and application locking
  • Local data excluded from device backup systems by default
  • Administrative controls preventing employee access to health data

Data Retention

We maintain different retention policies for different data types:

  • Email addresses: Retained while account remains active
  • Authentication data: Retained for account security purposes
  • Health data: Stored locally only, controlled by user
  • Technical logs: Retained for 30 days maximum, then automatically deleted

3. How We Use Information

Email Address Usage

Your email address is used exclusively for the following purposes:

  • Account creation and authentication
  • Password reset and account recovery
  • Critical security notifications (breach notifications, suspicious activity)
  • Legal compliance notifications (policy changes, regulatory requirements)

Limitations: Your email is not used for marketing, user profiling, behavioral tracking, or any commercial purposes beyond account management.

Health Data Processing

All health-related data processing occurs exclusively on your device:

  • Risk assessment calculations performed using local algorithms
  • Health trend analysis computed on-device
  • Testing reminders and scheduling managed locally
  • Partner verification processed using cryptographic protocols

Anonymous Group Features

When participating in group sessions or partner verification:

  • Only temporary, anonymous session identifiers are transmitted
  • No personal health data leaves your device
  • Session data automatically expires within 24 hours
  • Cryptographic protocols prevent participant identification
  • Group data cannot be correlated with individual accounts

4. Third-Party Services & Integrations

Healthcare Provider Integration

Optional clinic and healthcare provider integrations operate under strict privacy controls:

  • Integration requires explicit user consent for each data sharing instance
  • Users control which specific information is shared
  • QR code scanning processed locally without data transmission
  • Healthcare providers bound by separate privacy agreements
  • Integration can be revoked at any time

Third-Party Services

IntimID minimizes third-party dependencies to protect your privacy:

  • Analytics: No third-party analytics or tracking services
  • Advertising: No advertising networks or tracking pixels
  • Cloud storage: No third-party cloud storage of personal data
  • Social media: No social media integrations or sharing

Platform Dependencies

Certain platform-level services are required for application functionality:

  • App stores: Installation and update distribution (Apple App Store, Google Play)
  • Push notifications: System-level notification services (when enabled)
  • Biometric authentication: Platform-provided biometric services

Note: These services operate under their respective privacy policies and are beyond our direct control.

5. Your Rights & Controls

Data Control Rights

You maintain comprehensive control over your information:

  • Access: View all data associated with your account
  • Modification: Edit or correct any stored information
  • Deletion: Permanently delete your account and associated data
  • Portability: Export your health data (future feature)
  • Restriction: Limit processing of specific data types

Account Deletion

You may delete your account at any time with the following effects:

  • Email address and authentication data permanently deleted within 30 days
  • Health data remains on your device until manually deleted
  • Anonymous user identifier rendered inactive immediately
  • No recovery possible once deletion is confirmed

Limitations on Data Recovery

Due to our privacy-by-design architecture:

  • We cannot recover health data if you lose device access
  • We cannot provide health data to third parties (including family members)
  • We cannot transfer data between devices (current technical limitation)
  • We cannot decrypt health data without your biometric authentication

7. Contact Information & Updates

For privacy-related inquiries, data requests, or concerns about this policy:

Data Protection Officer: privacy@obsilion.com
Technical Support: support@obsilion.com
Legal Inquiries: legal@obsilion.com
Mailing Address:
Obsilion Privacy Officer
[Physical address to be provided upon incorporation]

Policy Updates

This privacy policy may be updated to reflect:

  • Changes in legal requirements or regulatory guidance
  • New features or technical capabilities
  • Enhanced privacy protections or security measures
  • User feedback or operational improvements

Notification of Changes

Material changes to this policy will be communicated through:

  • Email notification to all registered users (30 days advance notice)
  • In-app notification before policy takes effect
  • Updated policy posted on our website with change summary
  • Version history maintained for transparency

Effective Date & Governing Law

Effective Date: July 2025 (upon application launch)

Last Updated: July 2025

Governing Law: This policy is governed by the laws of [Jurisdiction to be determined based on incorporation location], without regard to conflict of law principles.

Severability

If any provision of this privacy policy is found to be unenforceable or invalid, that provision will be limited or eliminated to the minimum extent necessary so that this policy will otherwise remain in full force and effect.

Our Privacy Commitment

We pledge to maintain IntimID as a privacy-first application with pseudonymous accounts, subject to applicable legal requirements. Your sensitive health information deserves the highest level of protection achievable through current technology.

No Data Commercialization

We will not sell, rent, or commercialize your personal data, except as required by law.

🚫

Limited Data Linking

We implement technical controls to prevent linking your health data to your email address.

🔒

Local-First Architecture

Health data processing occurs on your device whenever technically feasible and legally permissible.