boyfrnd United States Privacy Notice

Who is responsible for the data

boyfrnd is operated by PROJECT82 LLC, an active entity. Its business address of record is 30 N Gould St, STE R, Sheridan, WY 82801, USA. The identified operator determines why and how covered personal information is processed for this service, subject to the limitations stated here. This notice is in effect as of the effective date stated in this document, on the operator's approval; United States counsel has not reviewed it. Legal notices may be sent to jin@project82.kr, and DMCA copyright notices to the designated agent Jinwon Jeon at dmca@project82.kr. Vendor facts are reconciled to live configuration and contracts as each one is verified.

Notice at collection: categories collected

boyfrnd is an adult AI companion service with proactive messages, memory, and relationship stages. Conversation, reaction, memory, safety, and relationship-stage records support the requested experience. boyfrnd sells the Plus subscription, monthly or annual, at the price shown before purchase; Plus grants no coins, and message replies cost no tickets or coins while it is active. One-time coin packs of 500, 1,100, 2,400, 6,500 coins are sold through the Apple App Store and Google Play in-app purchase systems managed via RevenueCat, and through Stripe web checkout where web sales are open. Without Plus, each message reply uses one free ticket if available and otherwise costs 8 coins. The service is for adults age 18 or older only, and training eligibility also begins at age 18. Minors and users whose adult status is unknown may not use the service or contribute data to training. Depending on use, categories may include account and contact details; age or birth-date data; device, log, and cookie data; conversation or call content; recordings and derived transcripts; character, memory, and preference data; safety reports; purchase and transaction records excluding full payment credentials handled by a store or payment provider; and support communications. A category not verified in the product data flow is not added to this notice by assumption.

Sources of personal information

We receive information directly from you, from your interactions with AI and safety features, from the device or browser you use, from app stores or payment services, and from service providers acting for the operator. We do not treat an unverified vendor inventory as a final public recipient list.

Purposes and authority for use

We use information to create an account, provide requested AI responses and continuity, classify age, personalize features, process purchases, detect abuse, investigate reports, secure systems, provide support, comply with law, establish or defend claims, and, for eligible adult data after valid notice, evaluate and improve models. Applicable consent, contract, legal-obligation, and legitimate-purpose requirements are honored by jurisdiction.

Service processing is separate from training

Operational processing may continue after a training opt-out when needed to generate replies, store conversations or requested memory, perform age and content-safety checks, handle reports, prevent fraud, secure accounts, complete payments, provide support, or meet legal duties. Training, fine-tuning, evaluation-dataset addition, and long-term pseudonymized retention for those purposes stop prospectively as described in the AI Data Use Notice.

Human review and labeling

Only a limited number of authorized personnel may review the minimum context needed for improvement quality evaluation or labeling. Improvement labeling views must never expose account or direct contact details. Operational support or safety review is a distinct limited-purpose process and does not make those details available for improvement labeling. Access, viewing, export, and deletion events are logged, and an external labeler may not be used until confidentiality, security, access, and deletion obligations are contractually verified.

Service providers and disclosures

Service providers may support hosting, AI inference, security, customer support, analytics, communications, or payments only under appropriate instructions and safeguards. Only service providers whose actual use is verified are listed below. A value not yet confirmed from contracts and consoles is not estimated and is shown as "To be confirmed".

| Provider | Service | Surface | Processing location | Retention | | --- | --- | --- | --- | --- | | Supabase | Authentication, database, storage, and server functions | Mobile app, Web, Server | United States (us-east-1, database and storage); server functions may run in the region closest to the caller | When an account is deleted, its conversations, messages, memories, relationships, scheduled messages, push tokens, user-created characters, wallet, reports, training data and other account data are deleted with it; in-app purchase records are kept de-identified without the user link; web (Stripe) payment records become eligible for deletion 5 years after the payment (earlier records without a recorded amount or payment time stay de-identified until the payment facts are confirmed and a period is set); safety and moderation records are kept without the user link and have no set deletion schedule; daily backups are kept for about 7 days | | Anthropic | Chat reply generation, moderation, and character authoring | Server | United States (data storage); requests may be routed for processing to select countries in the United States, Europe, Asia and Australia | Under the provider's default policy, inputs and outputs are deleted within 30 days of receipt or generation (if flagged for a usage-policy violation, inputs and outputs up to 2 years and trust-and-safety classification scores up to 7 years) | | Voyage AI | Embedding generation for memory recall: the text of your latest message, extracted memory sentences, and conversation summaries | Server | United States | Since 2026-10-09 23:25 (KST) the model-training opt-out applies, so under the provider's terms data is not stored after processing; data sent before then may continue to be used by the provider, for example to improve its models, under its terms | | RevenueCat | In-app purchase verification and subscription entitlements | Mobile app, Server | United States | For the term of the processing agreement (after it ends, return or destruction can be requested within 30 days, after which the provider may delete the data) | | Stripe | Web payments for subscriptions and coins (new checkout only when the sales gate is open), the billing portal, management of existing subscriptions, and subscription cancellation on account deletion | Web, Server | The United States and other countries where Stripe, its affiliates, and subprocessors process data | As long as needed to process the payment; Stripe keeps its transaction records under Stripe's privacy policy. | | Expo | Push notification relay, app builds (EAS), and over-the-air updates | Mobile app, Server | United States | Notification content is not stored and is processed only for the time needed to hand it to the Apple and Google push services; push tokens are kept as long as needed to send notifications (deleted when our Expo account is deleted); app build logs and artifacts 90 days, backups 90 days after creation | | Apple APNs and Google FCM | Push delivery to devices | Mobile app | The United States and other countries where Apple, Google and their subprocessors operate facilities (Firebase Cloud Messaging is a global service with no data-region selection) | Each push service keeps a notification until it is delivered to the device; undelivered notifications are discarded after that service's default period (about 4 weeks) | | Sentry (web) | Web error and outage diagnostics | Web | United States (Sentry US data region) | Error events are kept for 30 or 90 days depending on the provider plan | | Sentry (mobile app) | App error and outage diagnostics | Mobile app | United States (Sentry US data region) | Error events are kept for 30 or 90 days depending on the provider plan | | PostHog | Product analytics and session replay (all text masked on the web app; inputs masked on the landing page) | Web | United States (PostHog Cloud US) | Events are kept for 1 year (free plan) or 7 years (paid plans) depending on the provider plan | | Vercel | Hosting of the web app and landing page | Web | United States (server functions in iad1); static pages are served from Vercel's global edge cache | As long as needed to process the request; runtime logs are kept for 1 hour to 3 days depending on the provider plan (up to 30 days with the observability add-on) | | Google (social sign-in) | Social sign-in | Mobile app | The United States and other countries where Google operates facilities | As long as needed to process the sign-in. We receive only the sign-in result (such as the email address); Google keeps its own records under Google's privacy policy. | | Apple (Sign in with Apple) | Sign in with Apple | Mobile app, Server | The United States and other countries where Apple operates facilities | As long as needed to process the sign-in; Apple keeps its own records under Apple's privacy policy. |

We may also disclose information when lawfully required or necessary to protect rights and safety.

Cross-border processing

The operator is a United States company, so personal information from users outside the United States is processed abroad as the ordinary course rather than as an exception. The transfer is carried out as necessary to perform the service agreement with you, and is disclosed here rather than made subject to a separate consent. Data in transit is protected with TLS. Data at rest is encrypted by the processors that store it, as documented in their published service terms. Access is restricted by role, and database rows carry row-level security policies so that an authenticated request reaches only its own records. Each processor is engaged under a data processing agreement incorporated in its service terms. Transferred data is deleted without delay when an account is closed, except records a statute requires be kept, which are held separately for that statutory period and then deleted.

Information may also be processed by service providers outside the state or country where a user lives. The operator will verify each destination, recipient role, purpose, transfer mechanism, safeguard, and retention term. This notice does not substitute an assumed country or vendor for that required transfer record.

Retention criteria

Retention criteria include the time needed to provide an active account or requested feature, the sensitivity and volume of the data, safety and fraud needs, legal recordkeeping, dispute limitation periods, a valid preservation request, and the time required for secure deletion from backups. Training copies follow the additional eligibility, opt-out, and separability rules in the AI Data Use Notice rather than an unlimited retention period. For payments made on the web through Stripe Checkout, deleting an account removes the record's link to the account and keeps only the payment identifiers, amount, currency, status, and payment time for 5 years from the payment under the Korean e-commerce recordkeeping rule for payment records; after that period the record becomes eligible for deletion. Earlier payment records without a recorded amount or payment time are not automatically given this period and are kept in the same de-identified form until the payment facts are confirmed and a period is set.

Security safeguards

We use administrative, technical, and organizational measures proportionate to the data and risk, such as access restriction, logging, separation of operational and training stores, masking, and protected transmission where appropriate. No system is perfectly secure, so this notice does not promise absolute prevention of loss or unauthorized access.

State privacy rights and choices

Depending on residence and applicable law, you may request access, correction, deletion, or portability; opt out of certain sale, share, or targeted advertising activity; limit certain sensitive-data use; and receive equal service without unlawful retaliation. You may appeal a denied request and may use an authorized agent where permitted. This notice does not authorize the monetary sale of training data. A factual classification of any SDK disclosure as a sale, share, or targeted advertising event requires completion of the vendor audit, which is not complete.

Children, teens, and unknown ages

The service is for adults age 18 or older only, and training eligibility also begins at age 18. Minors and users whose adult status is unknown may not use the service or contribute data to training. All minor and unknown-age events are ineligible for model training, evaluation datasets, and labeling for improvement. If age information changes or indicates a minor, pending training material is removed or blocked under the AI Data Use Notice.

AI outputs and automated processing

Automated systems generate content, personalize continuity, classify safety risk, and help detect abuse. They may make mistakes and are not represented as human judgment. Where applicable law grants review or opt-out rights for a decision producing legal or similarly significant effects, the operator will provide the required process rather than relying on this general description.

How to make a privacy request

Privacy and deletion requests may be sent to jin@project82.kr. Requests may require proportionate identity verification, and an authorized agent may need to show authority.

Changes to this notice

We will date and describe material changes and provide prominent advance notice when required. New training terms apply only after the required versioned notice and never backdate authority. Earlier versions remain in revision history, and mandatory rights continue despite a policy change.