1. Scope and contact
Operator: Operator identity awaiting owner confirmation. Mailing address: Mailing address awaiting owner confirmation. Privacy and support email: Privacy contact awaiting owner confirmation.
This policy describes the adult Fit Fluffy Guy beta. Operator details and jurisdiction-specific requirements must be confirmed before public launch. Questions or requests can be submitted to the privacy contact above once configured; signed-in members can use the Privacy page for export and deletion requests.
2. Information collected and sources
You provide your name, email, age or age range, eligibility attestations, height, weight, measurements, goals, activity, food preferences and reported allergies, training access, check-ins, adherence, and optional support messages. We store your account, consent history, program records, photos, generated four-view physique images, videos, and reports.
Authentication stores password hashes, session records, verification records and, where enabled, protected multi-factor authentication records. Requests supply browser/device information, IP-derived security identifiers and operational logs. Hosting providers may see your IP address. We do not request precise geolocation, contact lists, or background camera access. File uploads are selected by you. Photo metadata is removed when images are re-encoded; originals remain private while awaiting review or confirmed cleanup.
The current beta collects no card details or subscription payments. No Stripe account is integrated. No advertising pixels or nonessential analytics are intentionally enabled.
3. Purposes and legal bases
We use information to provide and secure accounts, save assessments, produce general-wellness meal and training plans, record progress, review uploads, create requested AI videos, investigate failures, send service emails, and fulfill privacy requests. Plans are not medical decisions or eligibility decisions for employment, credit, insurance, or healthcare.
Where GDPR applies, ordinary account processing may rely on performance of a contract; proportionate security processing on legitimate interests; required records on legal obligations; and optional photo/provider processing on consent. Health-related or other special-category information may require a separate explicit-consent basis. Counsel must confirm the applicable Article 6 and Article 9 bases before offering service in those regions. Consent may be withdrawn for future optional processing without undoing prior lawful processing. We do not claim HIPAA certification or universal GDPR/CCPA compliance.
4. Service providers and disclosures
Hostinger hosts the application and MySQL account/program database. Cloudflare R2 stores private uploads and output media. Cloudflare Turnstile processes browser/security signals to deter automated abuse. Resend receives email addresses and transactional email content. Runware and its selected model providers receive the approved front, back, left and right reference photos, necessary generation instructions, and limited goal context for the image-and-video workflow you request. Seedream generates the canonical front, then matching right, back and left views. Kling receives that finished four-view set to animate one fixed physique. Photo URLs are temporary or server-mediated, not public galleries.
When configured, Sightengine receives sanitized uploaded photos to screen for nudity and inappropriate content. Only uploaded images are screened; no video moderation, age verification, identity verification or model-training feedback submission is enabled. Without credentials, or when screening is inconclusive or unavailable, photos remain locked for an authorized review. The upload form requires your 18+ and photo-rights declarations; these are not verification of age, ownership, angle or anatomy. Administrative private-media access requires MFA, recent verification, a recorded purpose and an audit record.
We do not sell personal information, share it for cross-context behavioral advertising, or use your photos in public marketing without separate permission. We may disclose minimum necessary information to comply with lawful obligations, protect users or security, or an approved service successor subject to notice and applicable safeguards. Provider retention, training-use settings, subprocessors and data locations must be contractually verified; we cannot promise that our deletion API deletes every vendor copy immediately.
5. Private media and AI
Photos and generated media are private by default. Member access is scoped to the owning account and uses short-lived signed links or authenticated server delivery. Do not share these links. Upload only yourself, with appropriate opaque coverage, no nudity or sexual content, no children, and no other people. A reviewer may reject unsuitable or unclear photos and request replacements.
The initial and final AI videos are optional, approximate visualizations. They may contain incorrect anatomy or motion and are not measured body composition or guaranteed outcomes. No new video is generated for each check-in. Report a defective result in the dashboard. Beta reports do not automatically create a paid retry. Declining provider processing prevents new video generation, not access to ordinary account features.
6. Retention and deletion
Unclaimed intakes expire after the configured intake lifetime (currently 24 hours); scheduled cleanup removes expired intake content and associated private objects. Completed cleanup is recorded only after storage deletion succeeds, and failed items are retried. Temporary upload reservations expire after 30 minutes. Rejected photos and originals replaced by sanitized copies are queued for confirmed deletion. Processing depends on the scheduled workers running successfully, so expiry is not a guarantee of instant erasure.
Active account and challenge history is retained to provide the service until account or media deletion is requested, subject to necessary lawful exceptions. Ready data-export archives expire after seven days. Verified account deletion removes associated active-system records and private media through a retryable worker. We minimize retained operational evidence and unlink identifying fields where applicable; a narrowly scoped budget identifier may be retained to prevent beta quota evasion. Backup and vendor copies follow the verified provider schedule, which the operator must establish before public launch. We will explain any lawful retention exception in response to a request.
7. Choices and privacy rights
Use the signed-in Privacy controls to request a machine-readable export, delete media, withdraw future Runware processing consent, or request account deletion. Contact support for correction, access difficulties, objections, restriction, portability, an appeal, or an authorized-agent request. We verify identity proportionately and do not ask for passwords or unnecessary identity documents by email.
Depending on residence and applicable law, you may have rights to know/access, correct, delete, port data, withdraw consent, restrict or object to processing, limit certain sensitive-data uses, opt out of sale/sharing, appeal, and complain to a regulator. We do not discriminate for exercising a protected right. Since we do not sell or share information for advertising, no sale/sharing opt-out is needed for those activities; Global Privacy Control signals will not be used to enable prohibited processing. Response deadlines and lawful exceptions depend on the applicable law, rather than this policy extending those deadlines.
8. Security, transfers and incidents
Controls include private storage, account-scoped authorization, password hashing, administrator MFA and recent verification, bounded uploads, sanitization, shared rate limits, content-security policy, audit records, and secret separation. No service can guarantee complete security. Report suspected unauthorized access to the configured support contact. We investigate, contain incidents, and provide notices where required by applicable privacy and consumer-health breach laws.
Providers may process data outside your state or country. The operator must verify their locations and lawful transfer mechanisms before enabling regions that require additional safeguards. Availability of this beta is not an assurance that all international legal requirements have been satisfied.