Scope and who may use the site
This policy applies to the Love at First Fright website and its dating and social community features. It covers visitors as well as signed-in members.
Love at First Fright is an 18-and-older community. You must be at least 18 to create a member profile. A birth date that shows you are under 18 cannot be saved.
Information we handle
Account and authentication
When you sign up or log in, you provide an email address and password. Supabase processes those credentials for authentication, email confirmation, sign-in, sign-out, and password recovery. Love at First Fright receives the account identifier and session credentials needed to keep you signed in; the site does not place your password in a member profile.
Profile information
To create a profile, you provide a display name, full date of birth, and location. You may also add a biography, what you are looking for, favorite genres, up to five favorite movies, a built-in avatar, or a custom profile photo. Custom photos are uploaded to Supabase Storage and their public file URLs are saved with the profile.
Your full birth date is stored to enforce the age requirement and calculate your age. The discovery feature returns the calculated age—not the birth date—to other members.
Social and event activity
The service records likes and passes, mutual matches, connection requests and responses, accepted connections, event responses, and the time those records were created or changed. If you select “Going” for a published event, your display name and profile image can appear in that event’s attendee preview. Aggregate “Going” and “Interested” totals are also shown.
Private messaging stores the conversation participants, message text, sent time, and read time. Messaging is limited to accepted connections. Group discussions store the group, author, post text, publication status, and posting time. Published discussions show the author’s display name and are available to members of that group; group moderators or owners can remove posts.
Reports, blocks, and safety
If you report a member, the service stores who reported whom, the selected reason, optional details, the report’s status, and relevant timestamps. Reports are not exposed to ordinary members. If you block someone, the service stores the blocking relationship and time. Your own blocked-members list is available to you; the blocked member is not shown that list.
Browser storage and technical requests
After authentication, the site stores your Supabase session—including access and refresh tokens—in your browser’s local storage under love-at-first-fright-session. It uses that session to restore your login and removes it when you sign out locally or when restoration fails. The application code does not set cookies. We use Vercel Web Analytics for aggregate public-page visitor and page-view statistics and counts of signup form opens, accepted signup requests, signup confirmation prompts, signup sessions created, saved profiles, group joins, and saved event responses. Action events contain only fixed names, without form values or member, group or event identifiers. It does not use analytics cookies. Our integration removes URL query parameters and fragments, excludes staff review and moderation pages, and does not attach names, account IDs, messages, survey answers, or profile details to analytics events.
Like any web service, the site and the services that deliver it receive ordinary request information needed to return pages, images, and API responses, such as the requested URL and network connection information. Analytics helps us understand which public pages people use and which device types visit the site. It does not provide a named visitor list. See Vercel’s analytics privacy information.
Who can see what
Published event details and aggregate RSVP totals are available without signing in. For members marked “Going,” the attendee preview also makes the display name and profile image available on the public event view. Uploaded profile-photo files use public URLs.
Member discovery can show your display name, calculated age, location, biography, profile image, interests, favorite genres, and favorite movies. Accepted connections can also be visible from member profiles. Your exact birth date and account email are not returned in discovery profiles.
Account credentials and your exact birth date are not displayed to other members. Likes and passes are available only through the account-specific matching flow. Connection requests are limited to the members involved. Messages are limited to conversation participants, subject to blocking and connection controls. Group discussions are visible to members of the relevant group. Block lists and reports are restricted as described above.
Supabase receives the account, profile, storage, social, safety, event, and messaging data needed to provide its authentication, database, and file-storage services. Vercel is configured to build and host the website and therefore delivers site files and requests.
Choose profile and message content with care. Other people may save or share information they are allowed to see, outside the controls of this site.
How information is used
- create, authenticate, recover, and maintain member accounts;
- enforce the 18-and-older requirement and calculate age without showing the full birth date;
- create profiles and help signed-in members discover people with shared interests;
- record likes, passes, matches, connections, event responses, messages, group memberships, and discussion posts;
- display published events, attendance totals, and “Going” attendee previews;
- operate reporting, blocking, moderation, and community-safety controls;
- provide session continuity, password recovery, and core site functionality; and
- protect the service and enforce the Community Guidelines.
We do not use member information for targeted advertising. Aggregate page statistics are processed by Vercel as described above.
Service providers and third-party links
Supabase provides authentication, the database API, and profile-photo storage. Vercel is configured as the website’s build and hosting platform. Information is sent to these providers as needed to run those parts of the service.
The movie library and event pages may show externally hosted images and links to services such as TMDB, movie information pages, studios, streaming providers, trailers, event organizers, and ticket sellers. Following a link takes you to another service under its own privacy practices. Loading an externally hosted image can also send the host the ordinary technical information associated with that image request. Love at First Fright does not receive the information you later choose to give those third parties through their sites.
Retention, deletion, and privacy requests
Profile, social, event, safety, message, group membership, and discussion records remain stored so the relevant features can operate. The current implementation does not set a fixed deletion period. Removing a connection does not delete the existing conversation or messages. Blocking removes connection, match, and like/pass records between the two members, but existing conversation and message records remain stored and are unavailable through the blocked relationship.
Signed-in members may request account deletion from Account Settings. The account remains active while the request is reviewed, and the request may be cancelled before completion. To ask about access, correction, deletion, or another privacy concern, use the contact method below. A request may require enough information to identify the account and confirm that it belongs to you. We may retain limited information where reasonably necessary for safety, dispute resolution, legal compliance, backups, or records involving other members.
You can edit your profile from My Profile, change an event response, manage blocks from your profile, sign out to remove the saved session from that browser, and use your browser controls to clear local storage. Because custom profile photos use public URLs, avoid uploading an image you do not want accessible by URL.
Tester feedback and partner shopping
The optional beta survey stores your answers, optional nickname, a random response identifier, and submission time in Supabase for staff review. It does not require an account or ask for your email. Avoid including sensitive personal information. Moderators and administrators can review and export responses to identify improvements. If you supply a nickname or identifying details, your response may identify you.
Downloaded answer files and replies imported into the feedback review page are processed in that browser tab and are not uploaded to our server by the import tool. Exported files contain the answers you included. You control where you share them. Ask Contact & Support about deleting a survey response and provide its response identifier if available.
Marketplace purchases take place on the vendor’s website under its privacy, payment, shipping, and return policies. Tracked links or codes may allow a vendor or affiliate service to attribute a purchase and calculate our commission. We do not collect payment card details or shipping addresses through the partner marketplace.
Security practices and limitations
The application uses authenticated sessions, Supabase Row Level Security and restricted database functions to limit access to profile, social, messaging, block, and report data. Browser requests use a publishable key rather than a secret service key. The application checks profile-photo file type and size and writes each upload to a path derived from the signed-in account.
No online service can promise absolute security. Keep your password and device secure, sign out on shared devices, and do not share session links or credentials. If you believe an account or message creates a safety risk, use the reporting and blocking tools described in the Community Guidelines & Safety.
International visitors
Love at First Fright is available over the internet, and its hosting and Supabase services may process information where their systems operate. The current repository does not identify a specific business location or offer region-specific privacy settings. If local law gives you privacy rights, you may raise a request using the method below.
Changes to this policy
We may update this policy as the service and its data practices change. The “Last updated” date at the top will show when this page was most recently revised. Review the current page for the latest description before continuing to use the service.
How to contact us about privacy
For a privacy question or data request, visit Contact & Support or email support@loveatfirstfright.app. Signed-in members may also use the Report control for member-specific concerns. Do not include passwords or session credentials.