This Privacy Policy explains how Obey The Light ("OTL," "we," "us," or "our") handles information when you use obeythelight.com and related account, sign-in, Premium, Saved Training, progression, Community, optional connected-device, and product-analytics features.
Local media contents stay on your device during normal playback. OTL does not upload the contents of videos, photos, or local audio merely because you select them for playback or connect a Local Media Library. Uploaded profile pictures are different, and Saved Trainings may store limited file references or metadata needed to restore local selections, as described below.
1. Information we collect
Account and sign-in information
If you create or use an account, we process information needed to operate and secure it, including your email address, email-verification status, account identifiers, session information, authentication-method information, and related timestamps. Password accounts use password-derived authentication data rather than requiring OTL to store your plaintext password.
If you sign in with or connect Google or Patreon, we receive information needed to authenticate or link the account, such as the provider account identifier, email address and verification information, and other identity information the provider supplies for that purpose. OTL stores provider-link information needed to recognize the connection.
Saved Trainings and local media references
If you use Saved Trainings, we store the Training name and configuration needed to restore it. Depending on what you save, this can include Trainer selection, timing and playback settings, Task settings, Yellow Light, visual and audio effects, Lovense settings, soundtrack selections, ending settings, media Tags, appearance settings, and user-entered lines supported by a feature.
The contents of local media files are not uploaded as part of Saved Trainings. OTL may, however, store limited local-media references or metadata needed to reconnect a Saved Training to files on your device, such as folder or relative file names, playlist order, file size, or last-modified information. Because those names can themselves be sensitive, Shared and Community Training snapshots are designed to omit local file references.
Activity, Stats, achievements, and progression
For signed-in users, OTL stores account-linked gameplay and progression records used to provide Stats, achievements, XP, levels, streaks, leaderboards, and progression integrity. These records can include a progression timezone, Training activity and timestamps, active or credited duration, completion information, configuration-derived dimensions such as Trainers, Tags, Tasks, or endings, earned achievements and XP awards, and records used to prevent the same activity from being credited more than once.
Some achievements also depend on account-linked actions such as using, revising, importing, or sharing Trainings. These progression records are separate from the aggregate product analytics described below.
Account-linked session records can also include clip and Task counts, time in each light, soundtrack and metronome usage, planned and actual endings, and source Training or share attribution. These records are stored separately from Saved Trainings and public-profile visibility.
Community and public information
Community participation is optional. If you enable a public profile, OTL may display your username, profile picture, selected title and username style, and player level. Community profiles and leaderboard participation are off by default. On a public profile, Progress details → Hidden still shows player level but hides additional progression. Partial adds total XP, achievement count, highest rank, and applicable mastery summary. Full also shows individual achievement ranks and titles. Detailed personal Stats, email addresses, internal account identifiers, and activity timestamps are excluded from public profiles. The separate Show on leaderboard choice can make your username, cosmetics, level, and ranking or XP information visible there, even with progress details Hidden.
If you publish a Training to Community discovery, OTL stores and displays the public Shared Training snapshot and publication state. Ratings are stored with the rating account and Shared Training so averages can be calculated and ratings can be changed later.
Sharing creates a snapshot of the Training name and settings accessible to anyone with its link, subject to feature-access restrictions. A Training can be published anonymously without a public Community profile. Unpublishing removes Community discovery but leaves the link usable. Making your profile Private hides the profile and changes attribution without revoking existing links. Revoking a link stops future access through it but does not erase copies already imported into other accounts.
If you upload a profile picture, OTL receives and stores a processed image used on account and Community surfaces. Active uploaded images are accessible to anyone with their image URL, even when your Community profile is Private. Replaced or account-deleted profile images may remain in cleanup storage until deletion succeeds, but are no longer eligible for normal public serving once retired.
If you submit a Community report, OTL stores the reporter account, reported profile or Training, selected reason, optional details, and review status and timestamps. Moderation records may also include internal notes and restrictions applied to a profile or Training.
Because OTL is an adult service, Saved Training settings, gameplay progression, connected-device use, and Community activity may reveal intimate or sensitive preferences. Do not save or publish information you do not want stored on OTL's servers or, where applicable, displayed publicly.
Premium and Patreon information
We store information needed to determine whether an account has Premium, such as entitlement source, entitlement identifiers, expiration or revocation information, and Premium-session records. Access codes are verified using one-way cryptographic representations; OTL is designed not to retain the plaintext code as the stored credential.
If you connect Patreon for Premium, Patreon provides information needed to identify your Patreon account and determine whether your membership qualifies. This may include Patreon user and membership identifiers, campaign information, membership status, charge status, entitled amount, and entitled tier identifiers. OTL does not receive your full payment-card number from Patreon.
Optional Lovense connection
If you connect Lovense, OTL processes temporary pairing identifiers and verification tokens, device identifiers, the reported device name or nickname, connection state, and your selected device. OTL sends vibration strength, pattern, timing, and Stop commands through Lovense's service to Lovense Remote. Pairing uses a generated identifier and the generic label "OTL player" instead of your OTL username or email address, but OTL associates the connection with your account. Your browser also requests the pairing QR image from Lovense.
For the Lovense XP bonus, OTL stores account-linked timing intervals for server-acknowledged gameplay commands and the resulting XP awards. These timing records do not contain device identifiers or a history of strengths or patterns. Saved and Shared Trainings can include your chosen Lovense settings, but do not include pairing credentials or device identifiers.
Local Media Library information
If your browser supports the Local Media Library and you choose to connect a folder, the browser may store a directory handle and related local metadata so OTL can reconnect to files on that device. The actual contents of those files remain local unless you separately choose a feature that explicitly uploads a file, such as a profile-picture upload.
Library clip reports
If you report a Library clip, OTL stores the clip identifier, report reason, optional details, light state, clip index when supplied, an anonymous report-session identifier used to group duplicate reports, and review status and timestamps. Community moderation records can also include review decisions, moderator notes, and profile or Training restrictions. Report records are separate from aggregate product analytics.
Minimal product analytics
OTL records aggregate daily counts for a small set of analytics events, including landing-page views, adult-entry acknowledgements, completion of the required Green Light and Red Light media-selection step, session starts and completions, account creation, Premium interest, Patreon click-throughs, Premium activation, and return visits. If a link to OTL includes utm_source, utm_medium, utm_campaign, or utm_content values, OTL records short normalized campaign labels so we can compare promotional efforts.
Aggregate analytics events do not include filenames, local file paths, account identifiers, email addresses, Saved Training contents, selected media Tags, Trainer or Task selections, user-entered custom lines, ending choices, or other intimate configuration details. OTL stores them as aggregate counts by date, event name, and promotional campaign labels rather than as a per-user analytics history. These limits apply to aggregate analytics, not to separate Saved Training, progression, or report records.
Technical and security information
Like most online services, requests to OTL may involve technical information such as IP address, request metadata, browser information, timestamps, and error information. OTL uses some of this information for security, abuse prevention, rate limiting, troubleshooting, and service operation. The aggregate product-analytics table described above does not store IP addresses or browser identifiers.
2. Cookies and local browser storage
OTL uses first-party cookies needed for account and Premium sessions and uses short-lived state to secure provider sign-in and linking. OTL also uses browser storage for local functionality such as remembering Local Media Library access, the adult-entry acknowledgement, a temporary unsaved session configuration so setup can survive a page reload within the same browser session, and a simple first-seen/return-day marker used to count return visits. That analytics marker is not a random user identifier and is not sent to OTL as an identifier. The temporary unsaved configuration remains in browser session storage and is not included in OTL's product analytics.
OTL also uses localStorage for account-specific pending progression events so activity can be retried after a delivery failure. Library clip reporting uses a browser-session identifier for duplicate-report handling. Clearing browser storage can remove pending records and local preferences; it does not delete records already saved to your account.
OTL does not currently use third-party advertising cookies, third-party analytics trackers, or cross-site behavioral advertising on the site. Because we do not currently use the site for cross-site behavioral advertising, a browser "Do Not Track" signal does not change the site's behavior at this time.
3. How we use information
- Provide, secure, and maintain accounts and authentication.
- Save and restore Trainings, settings, Stats, achievements, XP, levels, and streaks.
- Operate optional Community profiles, leaderboards, Training publication, ratings, reports, and moderation.
- Provide optional Lovense pairing and device control and calculate usage-based XP.
- Determine and restore Premium eligibility and verify Patreon membership when requested.
- Send account-verification and password-reset emails.
- Measure aggregate onboarding and session usage so we can improve the product.
- Prevent abuse, enforce rate limits, troubleshoot failures, and protect the integrity of progression and the Service.
- Comply with legal obligations and enforce our Terms where applicable.
4. Service providers and third parties
OTL currently relies on Cloudflare for hosting, networking, database, object storage, and security infrastructure; Resend for transactional account email; Google when you choose Google authentication; Patreon when you choose Patreon authentication, account linking, or membership billing; and Lovense when you choose to connect a device. OTL's minimal product analytics are stored in OTL's own Cloudflare-hosted database rather than sent to a third-party analytics or advertising platform.
Google and Patreon are separate services and handle their own accounts under their own policies. Patreon also controls Patreon purchases, billing, renewals, and cancellation. Linking or unlinking a provider inside OTL changes its connection to OTL; it does not itself delete the third-party account or cancel a Patreon membership.
Your browser also requests fonts from Google Fonts and can load Library video embeds from RedGIFs. These external services receive requests needed to provide their content, which may include your IP address and browser/request information. Google sign-in, Patreon, Google Fonts, and RedGIFs operate under their own privacy and storage policies; their processing is separate from OTL's aggregate analytics.
Lovense operates its app, device services, and related accounts under its own Privacy Policy. Disconnecting it in OTL does not delete information held by Lovense.
We do not currently monetize OTL by selling users' personal information to advertisers.
5. Retention
We retain account information, Saved Training configurations, activity/progression records, and related Community records to operate your account and the service. Deleting an individual Saved Training removes it from your active collection but marks its stored configuration as deleted rather than immediately erasing it. An existing share is a separate snapshot and can remain accessible until revoked. Unpublishing or revoking access does not itself erase every stored record or a recipient's imported copy.
We retain account-linked information for as long as reasonably necessary to operate the account and provide the relevant features, unless you delete it, delete the account, request deletion, or we are required or permitted to retain information for security, fraud prevention, dispute resolution, legal compliance, or backup integrity. Session, token, report, moderation, security, and operational records may have different retention periods.
When a profile picture is replaced or its account is deleted, OTL retires the stored image from normal use and attempts to delete the object; a cleanup record may remain until deletion succeeds. Aggregate analytics counts may be retained to compare product performance over time because those rows do not contain an analytics user identifier.
Lovense pairings expire after 24 hours. You can remove OTL's saved pairing using Disconnect. Connection expiry or disconnection does not erase saved configurations, usage timing records, or earned XP; those follow the account-data retention and deletion practices above.
6. Your choices
- You can use features that do not require an OTL account without creating one.
- You can manage connected sign-in methods where available; OTL may require at least one usable method to remain connected.
- You can remove individual Saved Trainings from your active collection, unpublish Community Trainings, or revoke share links. These controls have different effects, as explained above.
- You can keep your Community profile private or make it public, choose how much progression detail a public profile shows, and separately choose whether to join leaderboards.
- You can replace or reset an uploaded profile picture.
- You can disconnect a Local Media Library and clear OTL site data stored by your browser.
- You can switch Lovense off or disconnect its pairing. See Support for connection controls and Safety for stopping output.
- You can permanently delete your OTL account from Account using the Delete account trash icon at the bottom. Deletion requires typing GOODBYE; if the account has a usable password sign-in method, it also requires the current password.
- You may request access to or correction of account information, or request assistance with deletion, by contacting us.
Self-service account deletion removes the OTL user record and account-linked records that depend on it, including Saved Trainings, owned share snapshots, sessions, activity and Stats, XP, achievements, and other progression data, Community profile data and account-backed ratings or reports, provider links, and Premium entitlements. Associated profile pictures are retired for deletion as described above. Account deletion does not remove aggregate analytics counts that do not identify an account, media files that exist only on your device, anonymous Library clip reports, recipient-owned imported Trainings or other copies someone else made, or accounts and memberships operated separately by third parties. For other privacy requests or if self-service deletion is unavailable, email support@obeythelight.com. We may need to verify that you control the relevant account before acting on a request.
7. Security
We use technical and organizational measures intended to protect account information, including secure session cookies, password hashing, provider-token verification, origin checks, request limits, rate limiting, and encrypted HTTPS transport. No online service can guarantee absolute security.
8. Adults only
OTL is intended only for adults who are at least 18 years old and at least the age of majority where they live. We do not knowingly offer the Service to minors. If you believe a minor has created an account or provided information to OTL, contact us promptly.
9. International use
OTL is operated online and may be accessible from multiple jurisdictions. Privacy rights and legal requirements vary by location. We may restrict availability where necessary, and nothing in this Policy limits rights that cannot legally be waived in your jurisdiction.
10. Changes to this Policy
We may update this Privacy Policy as OTL changes. The effective date above will be updated when the Policy changes materially. If a change materially affects how account information is handled, we may provide additional notice where appropriate.
11. Contact
Privacy, account, and support requests: support@obeythelight.com.