1. Who this notice covers
Ezhara LLC operates YIKES, an AI-assisted dating text and screenshot analysis product. This draft explains the current app’s collection and use of information when you browse, create an account, submit a situation, or save a roster and history. It is not an adopted policy or a promise about features that are not available.
YIKES helps you reflect on conversations. It is not a dating or matchmaking service, a therapist, an emergency service, or a way to determine another person’s private intentions.
2. Information you provide
If you explicitly join the Sidebar waitlist, we save your account ID, account email at signup, consent version, signup time and team review status. No dating content is attached. Only your account and the authorized YIKES team can access your entry. This opt-in is for Sidebar access updates, not unrelated marketing; joining does not mean an email has been sent.
If you send beta feedback, we save your chosen type, optional message and screen/feature, account ID, submission date and team review status. No dating conversation, screenshot or current page content is automatically attached. Avoid including private messages, names, credentials or unnecessary personal information. Feedback is available to your account and the authorized YIKES team, not other users; it is not an emergency channel.
The app does not ask how you heard about YIKES and does not collect or store a self-reported acquisition source, referral link or UTM attribution. The team may track campaign origins outside the app using links or codes in its own social posts.
Account information includes your email address, authentication information handled by our account provider, and preferences such as display name, response style and onboarding state. Google sign-in, when used, involves Google and our account provider; the information available depends on that sign-in service.
You may submit messages, conversation excerpts, screenshots, slang, dating situations, relationship stage, a name or nickname, and what happened before. These may contain information about you and other people, including intimate or otherwise sensitive information. Saved roster information may include a person’s name, age, where you met, rank, status, trend, category ratings, flags, notes and a friend’s name or opinion.
When you choose to save results, your account can keep analyses, summaries, scores and factor breakdowns, receipts containing text excerpts and context, and Decode, Ask the Guys, Draft or Debrief history. Saved analysis payloads can contain the input text and context as well as generated output; saving a read is not necessarily saving only a score. Review what you submit and save.
3. Screenshots and AI processing
A screenshot is previewed on your device and transmitted to YIKES and the AI processing services for that request. The current YIKES application does not write raw screenshot image files to its saved-history database or an image-storage bucket. Optional private History stores generated Decode/Draft results only, not the full source message or screenshot; generated evidence and replies can still include brief excerpts or descriptions of submitted content.
Decode, Ask the Guys and Draft send the content and context needed for the request through Lovable AI Gateway to the configured OpenAI model service. Moving from Decode to Ask the Guys or Draft may send the original text, relationship context, person name and a summary of the earlier read. These are separate AI requests. Content is not automatically anonymized before transmission; crop or remove identifying details yourself.
Our AI requests ask the model service not to store the response using its available request setting. That setting is not proof of zero retention, no training use, or deletion by every processor. We have not yet verified all gateway, model-provider, hosting, diagnostic-log, backup, training-use or regional-processing terms. Do not submit information you cannot appropriately share with these processing services.
4. Why information is used
YIKES uses information to authenticate accounts, produce the requested analysis or reply, carry context between features, save the roster and history you choose to keep, provide preferences and history-based summaries, and process deletion actions. Private History is off by default; opting in archives future successful Decode and Draft generated results. It does not backfill earlier results, archive later edits, link entries to a roster person, or inject History into AI prompts.
The server also records AI-attempt metadata: account ID, feature, calendar month and start, active-lease and finish timestamps. These usage records do not contain submitted text or screenshot bytes. They enforce monthly allowances, short-window limits and one active request per account, including failed or cancelled attempts. Deleting saved content does not reset these allowances.
Hosting, authentication and AI services may process technical information such as network identifiers, timestamps, errors and request metadata as part of operating and securing their services. Application error handling avoids intentionally printing private submissions or returning raw provider errors; this is not a guarantee that all infrastructure or provider logs contain no personal information.
5. Accounts, guest mode and browser storage
Guests can browse and use browser-only example or roster data, but must sign in before invoking AI or saving private cloud history. Guest data is not a cloud backup and may be lost if site data is cleared or you change devices.
The app uses browser local storage for guest app state and authentication-session persistence, and session storage for a Decode text/context draft. Guest app state has no app-defined automatic expiry. Session drafts normally last for that browser session. Signing out should not be treated as clearing all browser copies; use your browser’s clear-site-data controls on shared devices.
These storage mechanisms support account access and continuity. This draft does not establish a complete inventory of hosting cookies, analytics, tracking technologies or advertising-related processing. Ezhara LLC must verify those services before making broader tracking or advertising claims.
6. Who receives information
Lovable Cloud provides the app’s account and private-data infrastructure; Lovable AI Gateway and the configured model service process AI submissions. Google is involved if you choose Google sign-in. Service operators may access information as permitted by their contracts and operational responsibilities. Your saved roster and history are not a public feed; database rules restrict ordinary account access to that account’s rows.
Sharing or copying a result outside YIKES puts that copy under your and the recipient’s control. Do not include another person’s identifying or sensitive information in shared results without an appropriate basis.
Ezhara LLC must confirm its vendor list, access procedures, legal-request practices and any business-transfer disclosures before adoption. This draft makes no verified sale-of-data, advertising, international-transfer, data-residency or regulatory-compliance claims.
7. Retention and deletion
Saved account data remains available unless you delete it; the current app has no automatic age-based deletion schedule for saved history or AI usage. Browser copies remain according to browser storage behavior and your clearing actions. This is a description of the app, not an assurance about provider logs or backups.
In You & Preferences, you can manage individual receipts and history from a person’s scouting report, remove roster people, delete all saved roster/history data while keeping your account, or delete your account. Private History lets you turn off future automatic archiving, open saved generated results, or delete them individually. Turning off new archiving keeps existing entries until deletion. Roster archiving is a status change, not deletion. Removing a roster person deletes associated saved receipts and analyses through the database relationships.
Delete all saved data removes roster people, receipts and saved analyses; it does not remove your login, profile preferences or quota-attempt metadata. Account deletion removes the active app records and usage metadata and requests deletion of the authentication account. The steps are not one indivisible transaction: if an error occurs, some steps may have completed and you may need to retry. Browser data is separate.
Beta feedback has no automatic expiry in the current app. Account deletion also removes these active records. To request earlier correction or deletion, contact the support and privacy address below. The owner must decide an appropriate feedback retention schedule before final adoption.
Sidebar waitlist entries have no automatic expiry in the current app. Account deletion removes your active waitlist entry; deleting only roster/history does not. For earlier withdrawal, correction or deletion, contact the support and privacy address below. The owner must decide a waitlist retention schedule before final adoption.
Deletion from the active app does not establish immediate erasure from operational logs, backups, previously shared copies, or third-party AI systems. Provider retention, legal exceptions and recovery windows must be confirmed before publishing a final policy. No specific deletion deadline or backup-expiry period is promised here.
8. Your choices and privacy requests
Use nicknames; crop names, faces, contact details and unrelated messages; submit only relevant excerpts; avoid unnecessary financial, health, identification or intimate information. You can use the app without saving an analysis, change stored preferences, and use the deletion controls described above.
For support, privacy inquiries and account-related requests, contact Ezhara LLC at yikesapp.support@gmail.com. Privacy rights, including access, correction, deletion, restriction, objection and portability, may apply depending on your location and circumstances. This draft does not limit those rights. Ezhara LLC must confirm how requests are verified and answered before adoption, including requests from people whose messages someone else uploaded. Do not send passwords or unnecessary sensitive information with a request.
The supplied privacy and support address is yikesapp.support@gmail.com. Owner items still open: confirm the address stays monitored, add any legally required business contact details, and establish the request-verification process. No other business address, jurisdiction or response deadline is claimed here.
9. Adults and third-party messages
YIKES is only for adults 18 or older. When you create an account, or before an existing account first uses AI, you are asked to confirm that you are 18 or older. This is self-attestation: YIKES does not independently verify age and does not collect a date of birth or identity documents. The app stores only your account ID and the time you confirmed. If you answer that you are under 18, no confirmation is stored and AI features stay blocked; you can still read these documents and delete your account and saved data. The AI servers refuse requests from accounts without a stored confirmation. Account deletion removes the confirmation record.
Do not submit sexual content involving minors, or messages and images you have no lawful right to disclose. A screenshot’s sender may not have agreed to AI processing. Permission to receive a message is not automatically permission to publish it or share it with processing services. If appropriate permission or another lawful basis is unclear, leave it out.
10. Security and updates
The current app verifies sign-in before AI requests, enforces database ownership rules and same-account history relationships, limits request/image sizes and AI output, and uses atomic usage checks. These reduce risk but do not guarantee security, prevent all abuse, or replace your own account and device protection.
This draft carries the preparation date above, not an effective date. Before adoption, Ezhara LLC must settle applicable locations and privacy obligations, verify service-provider terms and retention, keep the yikesapp.support@gmail.com contact channel monitored, and arrange legal review. A final notice should identify its effective date and explain how material changes will be communicated.