Loading…
An operational summary of data practices in the current Atmosphere Models application.
Atmosphere Models is a marketplace that helps models and nightlife venues discover each other, publish profiles, browse events, and manage applications and invitations. This summary explains what the application stores and exposes based on current product behavior.
This summary applies to the public website and authenticated marketplace features served by Atmosphere Models. It reflects application behavior documented in the product and API — not every possible deployment configuration.
When you create an account, the application stores the information you submit at registration, including your name, email address, password (stored using standard password hashing — not plain text), and whether you register as a model or club account.
After registration, you may add profile and marketplace content, including display names, bios, city and country, availability, interests, languages, event preferences, uploaded photos, club descriptions, venue details, website and social links you choose to publish, event listings, and optional messages attached to applications or invitations.
Club accounts may also store owner-only fields such as phone number and street address for profile management. Those fields are not exposed on public club discovery pages.
Model and club profiles appear in public discovery only when the profile is marked discoverable, the owning account is active, and the owner has verified their email address. Incomplete profiles created at registration are not listed publicly and are not reachable by public profile URLs.
Public model profiles include discovery fields such as display name, bio, city, country, availability, interests, portfolio media, and platform verification status. They do not include account email, phone, internal account identifiers, or private marketplace records.
Public club profiles include club name, description, city, country, website, social links you provide, media, and verification status. They do not include owner email, phone, or exact street address.
Published events shown in public discovery include event details and nested public club information (city and country — not private street address).
Signed-in use of the web application relies on session-based authentication (Laravel Sanctum SPA cookies), including CSRF protection for mutating requests. These cookies are used to keep you logged in and to secure account actions — not for third-party advertising profiles in the application code reviewed for this page.
The application may send transactional email for account verification, password reset, and related account messages. Email delivery depends on the mail configuration of the deployed environment.
When models apply to events or clubs send invitations, the platform stores those records and related statuses (for example pending, accepted, or declined). Engagements and ratings between participating accounts are stored so each party can view their own marketplace history according to API authorization rules.
In-app notifications inform account holders about relevant marketplace activity while signed in. Email verification is required before marketplace write actions such as applying, inviting, accepting or declining invitations, completing engagements, submitting ratings, and club event management.
The backend records a limited set of product analytics events (for example registration and certain marketplace lifecycle events) to operate admin reporting. These events are not intended to track arbitrary UI interactions, and analytics writes are designed not to block primary user actions.
Platform administrators can review reports, moderate accounts, and manage verification workflows. Accounts may be suspended or banned, which prevents sign-in and authenticated marketplace use.
User-generated text such as bios, descriptions, and messages is stored as plain text and rendered without executing HTML in the web client.
The current application phase does not include in-platform payments, subscriptions, KYC flows, or a general direct-messaging product. Arrangements between models and clubs outside the data described above are not processed by these marketplace features.
You can update profile fields and media through authenticated profile tools. Public visibility depends on profile completion, account status, and email verification as described above.
For account help or configured public support channels, see the Contact page.
The following items are not defined in the application configuration or codebase. They should not be assumed or invented here:
