Privacy Policy - Vibes'n'Feels

Version 2026-10-07. This policy explains the data used by Vibes'n'Feels and the current service providers. Contact support@vibesnfeels.app with privacy questions.

1. Data we use

Identity: an authentication user ID, public username, 18+ confirmation, accepted Terms version and optional confirmed email and Avatar.
Vibes: processed JPEG photos and MP4 videos (including recorded sound when present), JPEG posters for videos, emotion, refinement, optional note, selected coordinates, framing and creation or expiry times.
Interactions: Friendship request usernames, status and timestamps; mutual Friend relationships; private nicknames you assign to current Friends; Feels; Discuss messages; mentions; reports; blocks; notification preferences and delivery state.
Cloud sync is unavailable. In Settings > Account & data > Backup and restore, create a ZIP containing all your completed Vibes saved on this device, processed photos or videos, previews, exact saved coordinates, notes, feelings and available camera originals. It does not include Friends, Feels, discussions, credentials or other people's Vibes.
Operations and safety: request metadata, moderation results, evidence, rate-limit attempts, errors and security records.
Vibe views: your account ID, the Vibe ID and the time we first record your view of that Shared Vibe. Repeated views do not add records or change that time.
Discuss message views: your account ID, the message ID and the time we first record your view. Repeated views do not add records or change that time. Current Chat participants see only the aggregate count, not who viewed a message.
Product analytics: app sessions and foreground engagement, normalized logical screens, a limited set of completed product actions, app version, platform, OS, device model and the local setting values listed in Settings. Firebase associates these data with a random app-instance/device identifier and may derive approximate location from the IP address. We do not send your account ID, email, username, Vibe or Friend IDs, text, photos, videos, audio, emotions, refinements or captured coordinates to Analytics.

2. Data that stays local

Vibes'n'Feels does not ask for or store your birth date. The service stores only your confirmation that you are 18 or older and when it was made. Vibes'n'Feels does not upload camera originals. Personal Vibes use app-managed local storage. Manual backups include exact coordinates and available camera originals in an unencrypted file. Vibes'n'Feels does not upload that backup. A destination you choose may store it under its own terms. Automatic gallery saving is off by default and adds the Photo Vibe camera original or the Video Vibe camera recording after a new Vibe is created. Save to gallery from your own Photo Vibe uses the original when available or the displayed local version otherwise; from a Video Vibe, that manual action saves the processed MP4. Gallery saving does not upload that saved file to Vibes'n'Feels.

3. How data is used

We use this data to:

Provide mutual Friends, Map, Feed, sharing, Feels, Discuss, notification, account, local backup, restore and deletion features.
Moderate content, investigate reports, enforce blocks and temporary restrictions, and prevent abuse.
Maintain availability, diagnose errors and secure authentication and storage.
Communicate account codes, service messages and support responses.
Exclude Shared Vibes you have already viewed from future Friends and Community notification summaries. Existing notification history is not rewritten. Vibe view records are not shown to other users and are not used for ranking.
Show current Chat participants an aggregate unique-view count for each Discuss message without exposing viewer identities.
Understand aggregate product use, engagement and retention and improve the app. Analytics is not used for advertising, attribution, cross-company tracking or decisions about a specific account.

4. Service providers

These providers may also process technical data such as IP address, request metadata and device or delivery identifiers under their own terms.

Supabase provides authentication, database, Storage and Edge Functions and processes the account and product data needed for those features.
Railway hosts the server-side processor for Video Vibes selected for Friends or Everyone. It receives the processed MP4, optional Note and account, Vibe and operation identifiers through the service, prepares a JPEG poster, sampled frames and audio for screening and returns output media and screening results through Supabase.
OpenAI Moderation receives a processed JPEG for a Photo Vibe selected for sharing or an Avatar, and sampled JPEG frames from Video Vibes selected for sharing. It receives a submitted username or optional Vibe Note when applicable. It receives a Discuss message only when automatic checks are enabled for that Chat. For a Video Vibe selected for sharing that has audio, OpenAI Transcription receives extracted audio. If the transcript contains text, OpenAI Moderation also receives that text. These requests do not include your actor ID, email or Vibe coordinates.
Expo receives the Expo push token, notification title and body, and product IDs or routes needed for delivery, then forwards the notification through Apple Push Notification service or Firebase Cloud Messaging. Feel and Friendship copy may include public usernames. Discuss push copy is generic and does not include the Discuss message or Vibe image.
Postmark receives the recipient email and account or service-email content. Operational moderation alerts contain case metadata and operator instructions, not reported content or reporter identity. Cloudflare Turnstile processes anti-abuse challenge data and the resulting token for signup, sign-in recovery and the neutral existing-email recovery fallback during account creation.
MapTiler receives style and tile requests for map areas viewed plus the app User-Agent. Vibes'n'Feels does not construct a dedicated captured-Vibe-coordinate payload for MapTiler.
Google Firebase Analytics processes the bounded product analytics described above as our service provider. Advertising identifiers, ad personalization, automatic native screen names and Vibes'n'Feels account identifiers are disabled or not supplied.

5. Visibility and retention

Vibes shared with everyone are visible to app users for 24 hours unless removed earlier. If the author enables Friends continuation, the same Vibe remains visible only to the author and current mutual Friends for up to 2 more days after the public period.
Vibes shared with Friends are visible for 3 days only to their author and current mutual Friends. Ending or blocking the Friendship removes access immediately.
Pending Friendship requests expire after 30 days. A Friendship remains until either person removes it, one person blocks the other, or an account is deleted. Limited request-attempt and resolved-request records may be retained for abuse prevention and service integrity.
A private nickname you assign to a Friend is visible only to your account. It is deleted when you clear it, the Friendship ends, either person blocks the other, or either account is deleted.
Personal Vibes remain in app-managed local storage until you delete them, remove the app data or lose the device.
Logging out clears local account data, including backup files inside the app. Deleting the app or losing the device can also lose local Vibes. Signing in does not download Vibes. Copies saved outside the app are under your control and remain after account deletion.
For a recorded Video Vibe report, private evidence includes both the JPEG poster and MP4; for a Photo Vibe, it includes the published JPEG. That evidence and the moderation case may be retained for 90 days after the most recent report.
Discuss and moderation audit records may be retained beyond Shared Vibe expiry for safety, integrity and dispute review.
Vibe view records survive audience changes and are removed when the Vibe or the viewing account is deleted, or by scheduled cleanup after 72 hours from the Vibe's creation, when it can no longer be shared.
Discuss message view records are removed with the message or the viewing account.
Firebase Analytics event and user-property data follows the configured Google Analytics retention controls. Deleting a Vibes'n'Feels account does not identify or selectively remove the anonymous Firebase app instance because Vibes'n'Feels does not connect that instance to the account.

6. Account deletion

Delete account removes the application identity, ends Friendships and pending requests, and starts permanent cleanup of owned database and Storage content. Storage is drained before the underlying authentication user is hard-deleted. A reporter reference may be removed from retained moderation audit rather than deleting the audit itself.

Backup files saved outside the app are not removed by account deletion. Delete them yourself at their chosen destinations.

7. Your choices

Keep Vibes Personal, delete individual Vibes and manage notification preferences.
Choose whether to automatically save the Photo Vibe camera original or Video Vibe camera recording to your system photo library after creating a new Vibe. You can manually save your own Photo Vibe's original when available or its displayed version; manual saving from your own Video Vibe adds the processed MP4. Automatic saving is off by default; add-only gallery access is requested only after your explicit action.
Accept or decline incoming Friendship requests and remove existing Friends.
Block and unblock users from Settings.
Create a recoverable account, log out and remove local account data, or permanently delete the account.
Turn anonymous usage analytics on or off in Account and data. Turning it off stops future collection on this installation; previously collected anonymous data follows the retention controls above.
Manual backup and restore transfer your own local Vibes using the supported ZIP format. They do not export account, social or moderation records. Contact support with a verified request about any access or portability rights that apply to you.

8. Changes

This policy may change as the product, providers or legal requirements change. Material Terms changes use versioned in-app review. The current public policy will also be made available on the product website before external alpha.