Data Processing Policy
Last Updated: March 6, 2026
This Data Processing Policy describes how Stanley Williams ("Data Controller," "we," "our," or "us") processes personal data in connection with the Vibe mobile application and website (the "Service"). This document serves as an internal policy and as a transparency measure for users and partners.
1. Data Controller Information
The data controller responsible for the processing of personal data is:
2. Categories of Data Subjects
We process personal data relating to the following categories of data subjects:
- Registered Users: Individuals who create a free account to use the Service, including those who authenticate via Google, Apple, email/password, or other supported methods.
- Premium Subscribers: Registered users who subscribe to Vibe Premium through in-app purchases (Apple App Store) or Stripe, gaining access to enhanced features.
- Guest Users: Individuals who use the Service without creating an account. Limited data (such as session-level location queries) may be processed temporarily but is not retained.
3. Types of Personal Data Processed
Account Data
- Email address
- First and last name
- Username
- Profile picture URL
- Authentication provider identifiers (Google ID, Apple ID)
- Hashed passwords (for email/password accounts only)
- Email verification status
Location Data
- Geographic coordinates (latitude and longitude) provided during venue searches
- City and region identifiers derived from search queries
- Location data is collected only when actively using search features and with user permission
Usage Data
- Search queries and search history
- Favorited venues and venue interactions (views, clicks, saves)
- Taste profile data (cuisine preferences, ambiance preferences, feature weights)
- Venue lists created by users
- Quiz responses and personalization preferences
- Notification preferences
Payment Metadata
- Stripe customer ID (for web-based subscriptions)
- Subscription status, plan type, and expiration dates
- RevenueCat subscriber identifiers (for in-app purchases)
- We do not store credit card numbers, bank account details, or other direct payment instruments
4. Processing Activities and Purposes
| Processing Activity |
Purpose |
Lawful Basis |
| Account registration and authentication |
Provide access to the Service |
Contract performance |
| Venue search and location processing |
Deliver core search functionality |
Contract performance |
| Taste profile and personalization |
Improve venue recommendations |
Legitimate interest / Consent |
| Favorites and lists management |
Enable users to save and organize venues |
Contract performance |
| Search history storage |
Allow users to revisit past searches |
Legitimate interest |
| Subscription and payment processing |
Manage premium subscriptions |
Contract performance |
| Email communications |
Account verification, password resets, service updates |
Contract performance / Legitimate interest |
| Analytics and service improvement |
Understand usage patterns to improve the Service |
Legitimate interest |
5. Data Retention Schedule
| Data Type |
Retention Period |
Notes |
| Account data |
Duration of account + 30 days |
Deleted within 30 days of account deletion request |
| Location data (search queries) |
Session-based or up to 90 days |
Not retained beyond active search history |
| Search history |
Duration of account |
Users can clear search history at any time |
| Favorites and lists |
Duration of account |
Deleted with account |
| Taste profile data |
Duration of account |
Users can reset preferences at any time |
| Payment metadata |
Duration of account + 1 year |
Retained for billing dispute resolution and legal compliance |
| Email verification tokens |
24 hours |
Automatically expired |
| Password reset tokens |
1 hour |
Automatically expired |
6. Sub-Processors
We engage the following third-party sub-processors to assist in delivering the Service. Each sub-processor processes data only as necessary for its designated purpose:
| Sub-Processor |
Purpose |
Data Processed |
Location |
| Google Maps Platform |
Venue search, geocoding, place details, photos |
Location coordinates, search queries |
United States |
| Stripe |
Payment processing for web subscriptions |
Customer ID, subscription metadata |
United States |
| RevenueCat |
In-app purchase management (iOS) |
Subscriber ID, purchase history |
United States |
| Neon (PostgreSQL) |
Primary database hosting |
All persistent user data |
United States |
| Replit Object Storage |
File and media storage |
User-uploaded files, profile images |
United States |
| YouTube Data API |
Influencer content integration |
Public video metadata (no user data shared) |
United States |
7. Security Measures
We implement the following technical and organizational measures to protect personal data:
Technical Measures
- Encrypted database connections (TLS/SSL)
- Passwords hashed using bcrypt with appropriate cost factor
- JWT-based authentication with secure token management
- OAuth 2.0 and OpenID Connect for third-party authentication
- HTTPS encryption for all data in transit
- Input validation and sanitization on all API endpoints
- Rate limiting on authentication endpoints
Organizational Measures
- Access to production data is restricted to authorized personnel only
- Database credentials are stored as environment variables, never in source code
- Regular review of access permissions
- Principle of least privilege applied to all system access
8. Data Breach Procedures
In the event of a personal data breach, we will:
- Detection and Containment: Immediately investigate and contain the breach upon discovery.
- Risk Assessment: Evaluate the nature, scope, and potential impact of the breach on affected individuals.
- Notification to Authorities: Where required by applicable law (e.g., GDPR Article 33), notify the relevant supervisory authority within 72 hours of becoming aware of the breach.
- Notification to Individuals: Where the breach is likely to result in a high risk to individuals' rights and freedoms, notify affected users without undue delay, providing clear information about the nature of the breach and steps they can take to protect themselves.
- Documentation: Maintain a record of all breaches, including facts, effects, and remedial actions taken.
- Remediation: Implement corrective measures to prevent recurrence.
9. Data Transfer Mechanisms
Personal data is primarily processed and stored in the United States. For users located outside the United States (including in the European Economic Area), data transfers are conducted in accordance with applicable data protection laws.
We rely on the following mechanisms to ensure adequate protection for international data transfers:
- Standard Contractual Clauses (SCCs) where applicable with sub-processors
- Data Processing Agreements with all sub-processors
- Adequacy decisions where available
- Ensuring sub-processors maintain appropriate security certifications (e.g., SOC 2, ISO 27001)
10. Employee Access Controls
Access to personal data is governed by strict internal controls:
- Role-Based Access: Access to user data is granted only to personnel whose role requires it for the operation or maintenance of the Service.
- Authentication: All access to production systems requires multi-factor authentication.
- Audit Logging: Access to sensitive data is logged for accountability and review.
- Credential Management: All production credentials (database passwords, API keys, secrets) are managed through environment variables and are never committed to version control.
- Periodic Review: Access permissions are reviewed periodically and revoked when no longer necessary.
- Separation of Environments: Development and testing environments use separate credentials and do not contain production user data.
11. Data Subject Rights
Individuals whose data we process have the right to:
- Access: Request a copy of the personal data we hold about them.
- Rectification: Request correction of inaccurate or incomplete data.
- Erasure: Request deletion of their personal data.
- Data Portability: Receive their data in a structured, commonly used, machine-readable format (JSON).
- Restriction: Request restriction of processing under certain circumstances.
- Objection: Object to processing based on legitimate interests.
To exercise any of these rights, users may contact us at the email address below or use the data export feature available within the Service.
12. Changes to This Policy
We may update this Data Processing Policy from time to time to reflect changes in our data processing practices, sub-processors, or applicable legal requirements. Material changes will be communicated through the Service or by updating the "Last Updated" date above.