Opening page…
Legal
This policy explains what LovelyBone Games receives, why it is used, where it is stored, and the choices available to you.
Last updated October 11, 2026
Patreon processes membership payments. LovelyBone receives only the account and membership information needed to identify an eligible supporter and provide site benefits.
01
This policy covers lovelybonegames.com, its member accounts, community, browser previews, and related LovelyBone services that link to this page. LovelyBone Games is the controller of the personal information described here.
The service is intended only for adults who are at least 18 and have reached the legal age for adult content where they live. It is not directed to children. If information from an underage person is discovered, it will be removed.
02
Patreon connection. When you connect Patreon, Patreon provides a stable Patreon user identifier, profile name, profile image URL, and membership information such as membership status, entitled tier or amount, relationship start date, and follower state. The Patreon profile name and image become the starting identity on your LovelyBone member card. LovelyBone does not request your email address, connected social accounts, or payment details.
LovelyBone account. We create an internal account and profile identifier and store your display name, avatar choice or uploaded avatar, member number, tier and access status, points, badges, notification preferences, account status, and relevant dates. You can replace the initial Patreon profile name and image with the display name and avatar you choose in My LovelyBone.
Launch Crew gift. We record successful membership verification, qualification before the campaign deadline, and redemption of the one-time thank-you gift. A qualified reservation remains available after a membership downgrade or departure, but collecting it requires an active, verified LovelyBone membership. Account deletion removes the reservation and account-owned points and cosmetics. A limited pseudonymous used-gift record remains while the reward program operates to prevent the same Patreon identity claiming the gift again.
Cloud game saves. When TGIF ELITE reports that cloud saves are active, LovelyBone stores the synchronized Heartframe save collection, game and save-format versions, slot names and timestamps, story checkpoint identifiers, progress variables, rollback history, persistent unlocks, and integrity and revision metadata. The save is connected to your internal LovelyBone account ID, not exposed on your public profile, and is used only to synchronize and restore your game progress.
TGIF playthrough history. We store whether your account began a free TGIF web playthrough or entered as a verified paid player, together with the game identifier and date. This essential account record keeps the appropriate continuation menus consistent after upgrades, membership changes, and device changes. Joining Patreon as a free member alone does not record a free playthrough. The private member-management console shows an existing free-playthrough entry registration separately from actual story-play reports. Registration does not establish how far you played or whether you are online. This record does not contain dialogue, choices, or save contents and does not depend on analytics consent.
TGIF free-play stage counts. Independently of your optional analytics choice, LovelyBone counts recorded free story starts, observed visits to the end of free access, clicks on its membership button, and actual story play with verified paid access after a free start. Each stage is counted once per internal account and game. These first-party account-linked records appear only as aggregate counts in the owner’s game-access console. Owner and test accounts are excluded. The stage requests contain only a fixed event category, without dialogue, choices, names, variables, URLs, or save contents. Identity comes from your existing LovelyBone session. Reporting failures do not interrupt gameplay.
TGIF account progress. TGIF ELITE records your signed-in account’s first observed story play, latest recorded play date, highest story update reached and a short scene identifier such as s082. The same summary includes a cumulative count and latest date of recorded returns made with verified free membership. A return is inferred when a story report follows at least 30 minutes without a report; it is not an exact visit measurement. Existing play dates provide the baseline, but earlier return counts are not reconstructed. These records apply to free and paid members, including players using device-only saves, independently of your optional website analytics choice. One progress summary per account and game appears in the private member-management console alongside any existing cloud-save summary. Reports run at most once per minute during visible, prepared main-story play; title visits, downloading, menus, hidden tabs and replay scenes do not update this progress. It is a recorded summary, not a live online indicator. We do not upload device-only save contents, dialogue, choices, names or variables, or collect play duration or session timelines for this summary. Owner and test accounts are excluded, and reporting failures do not interrupt gameplay. We also retain anonymous daily totals of recorded players, new recorded players and returning free players for 30 UTC calendar days. These totals contain no daily account identifiers or session logs and remain anonymous when an account is later deleted.
Daily free and paid counts. We break anonymous daily player and new-player totals into free and paid groups using verified membership when a story report is accepted. To avoid duplicates within each group, the existing account-progress summary keeps only the latest UTC day counted for free play and for paid play. Later membership changes do not reclassify earlier activity. These breakdowns add no session timelines or daily account lists.
Community activity. We store posts, comments, reactions, in-site notification events, blocks, reports, moderation decisions, and images you choose to upload. Public-facing profile details and contributions are visible to the relevant community audience.
Security and operation. We process session tokens in hashed form, request details needed to protect forms and sessions, and technical error or audit records needed to operate, troubleshoot, and secure the service.
03
We use information to connect your Patreon membership, determine access, provide account and community features, award points and badges, display your chosen profile, deliver requested files, keep sessions secure, prevent repeat reward claims, moderate content, investigate abuse, maintain the service, and comply with legal obligations.
We do not sell personal information. We do not use member data for third-party behavioral advertising.
04
Where data-protection law requires a legal basis, processing is carried out as necessary to provide the service you request, based on your choice to connect Patreon or submit content, for LovelyBone's legitimate interests in operating and securing the service, and when needed to meet a legal obligation. You may disconnect or delete your LovelyBone account, subject to limited records that must or may lawfully be retained.
05
Your chosen display name, avatar, member rank, badges, posts, comments, reactions, and timestamps may be shown to other eligible members. Do not post private information you do not want other members to see. Reports, blocks, and moderation notes are not displayed as public profile content.
In-site notifications tell an eligible member when another visible member likes their post or comment, or replies to their post. Notification events are private to the recipient, are filtered when members block each other or related content is unavailable, and are not sent by email, browser push, or an operating-system notification service.
06
LovelyBone uses Patreon for membership authentication and eligibility. The website uses Cloudflare-based hosting and storage, including D1 for structured account, cloud-save metadata, and community data and private R2 storage for synchronized save payloads, uploaded images, and protected media. These providers process data under their own security and privacy terms to deliver their services.
Information may also be disclosed when reasonably necessary to comply with law, protect users or the service, investigate abuse, or establish and defend legal claims. We do not give service providers permission to use LovelyBone member data for their own advertising.
07
TGIF uses an essential first-party cookie to remember a signed-out visitor’s 18+ confirmation for 30 days in that browser. It records only the confirmation, does not verify identity or age, and does not grant membership or gameplay access. We do not collect a date of birth for this prompt.
The site uses an essential secure session cookie to keep signed-in members authenticated. Cloudflare also processes basic request, security, cache, error, and bandwidth information to deliver and protect the site and provide aggregate operational metrics. Browser games may store saves, settings, and progress locally on your device. Clearing browser data, using private browsing, or changing devices can remove that local information.
Blog likes use a separate functional browser token with a maximum lifetime of one year. The token is random, stored in a secure HttpOnly cookie, and stored by LovelyBone only as a SHA-256 hash. It is used solely to remember whether that browser liked a published article. Blog likes are not connected to Patreon, LovelyBone member accounts, IP addresses, user-agent strings, points, notifications, or community activity. Clearing the cookie resets that browser's like memory.
The homepage trailer uses YouTube's privacy-enhanced player. The player is not loaded and no request is made to YouTube until you press Play. Playing the trailer or opening its YouTube link sends your browser to Google's services, which may process request information and use storage under Google's privacy policy. This is separate from your LovelyBone analytics choice.
Google Analytics runs on public pages to measure visits, traffic sources, approximate device and location information, and engagement such as time spent and scrolling. In the EEA, United Kingdom, and Switzerland, analytics storage remains denied until you allow analytics cookies, and Google receives only cookieless measurement pings. Elsewhere, public-page analytics may use cookies unless you select Essential only. Cookieless pings may include the public page path and title, timestamp, referrer, browser and device information, screen resolution, consent state, and network information used during transmission. Google states that Analytics does not store or log IP addresses.
Analytics is not enabled on admin, account, profile, private community, or game-save routes. Advertising signals and ad personalization are disabled, and LovelyBone does not send Patreon identifiers, member profile details, game saves, community content, or form text to Google Analytics. You can change the analytics choice below at any time. Selecting Essential only removes LovelyBone's Google Analytics cookies and does not affect essential site functions. TGIF ELITE clearly reports when its browser-local saves are also synchronized to the player's private LovelyBone account. The site does not use third-party advertising cookies.
TGIF free-play stage counts, playthrough history, and the basic account-progress summary use authenticated first-party requests to LovelyBone independently of the optional analytics choice. Selecting Essential only still controls Google Analytics as described above. The stage collector does not read or change that choice and does not assert analytics consent.
The public TGIF age-entry and player pages use the same Google Analytics property and browser analytics choice to measure page visits and ordinary page engagement. Their reported page address is /tgif/, without query strings or membership details. This is separate from the basic account-progress summary above.
08
Account and community information is generally kept while the account remains active or while it is needed to provide the service. Eligible raw community notification events are kept for no more than 180 days and are limited to the newest 500 per recipient. Session records expire or are revoked. Uploaded files that are replaced or deleted are removed from active storage when cleanup completes.
Deleting an account removes the member profile, access state, TGIF playthrough-history, conversion-stage and play-progress records, synchronized cloud game saves, points, badges, uploaded profile media, and active session. Browser-local saves remain on each device until the player removes that site data. Authored community text is erased and the contribution is marked as deleted so conversations remain understandable. Limited pseudonymous reward-use records, moderation tombstones, security records, backups, or records required by law may remain only as long as reasonably necessary for those purposes.
09
Depending on where you live, you may have rights to request access, correction, deletion, restriction, portability, or objection, and to withdraw consent where consent is the basis for processing. You may also have the right to complain to your local data-protection authority. LovelyBone will not discriminate against you for exercising an applicable privacy right.
You can update or delete your LovelyBone profile from My LovelyBone. Full steps and the effects of deletion are available on the account-deletion page.
10
LovelyBone and its service providers may process information in countries other than your own. Where required, appropriate contractual or legal safeguards are used for cross-border processing. Mandatory protections in your jurisdiction remain available to you.
11
Reasonable technical and organizational measures are used to protect information, including secure cookies, hashed session tokens, access controls, request validation, restricted administration, and private storage bindings. No online service can guarantee absolute security. If you believe an account or the service has been compromised, contact LovelyBone promptly and do not include passwords or payment details.
12
This policy may change as the website, games, or legal requirements develop. The date above identifies the current version. Material changes will be presented through the site or the relevant supporter channel when appropriate.
For privacy questions or a request you cannot complete through your account, contact LovelyBone through the official Patreon page from the Patreon account connected to the site.
Contact LovelyBone on Patreon ↗