Love Meter Privacy Policy

Love Meter privacy covers account identity received through Google authentication, internal user identifiers, credit balances, payment references, transaction history, tool inputs, public result summaries, private AI readings, photo asset records, basic security logs, and support correspondence. Love Meter does not need your Google password and does not store complete payment card details. Stripe and PayPal process payment credentials under their own privacy terms.

Tool inputs vary. Love Meter privacy treats raw names and Love Oracle questions as private inputs even when a safe result link is public. Photo bytes and paid reports are private. Public fields are limited to a score or sign, couple type or secondary value, short explanation, tool type, algorithm or model version where appropriate, and share text. Love Meter privacy does not turn submitted photos into public profile content.

Love Meter processes information to create requested results, authenticate accounts, connect private readings to their owners, manage credits, verify payments, prevent duplicate charges, issue automatic credit refunds after model failure, secure the service, delete expired photos, answer support requests, and comply with applicable obligations. Love Meter privacy does not authorize using private inputs for unrelated public profiles or community features.

Anonymous name, FLAMES, and Love Oracle results receive a public token and separate claim secret. The token opens only safe result fields. The claim secret is stored in the browser and allows a later signed-in user to claim the result. This Love Meter privacy design avoids putting the secret in a share URL. If local browser storage is cleared before claiming, Love Meter may be unable to prove ownership of the anonymous result.

A Love Meter share link is public to anyone who has its unguessable token. Love Meter privacy therefore limits the response to display-safe result information. Raw names, Love Oracle questions, photo bytes, claim secrets, user identifiers, payment records, and complete AI reports are not returned by the public result API. Result pages are marked noindex and are excluded from the sitemap, but noindex is not an access-control mechanism.

Do not share a result link with someone who should not see the summary. A recipient can forward or capture anything displayed on a public page. Love Meter privacy cannot prevent a person from saving a share card after receiving it. The standard card avoids raw input names to reduce exposure. Deleting an account removes account-linked records, but copies previously downloaded or shared by other people may remain outside Love Meter.

Love Meter by Photo requires sign-in but does not persist submitted JPEG, PNG, or WebP bytes on the server. Love Meter privacy converts selected files to base64 in the browser and sends them directly through the authenticated request to the configured multimodal model. D1 stores only private workflow facts such as photo count and mode, never the image data. Public result responses never include the original image.

The browser may retain the selected base64 images in IndexedDB for up to 24 hours so a paid reading can continue after a payment redirect. This cache is local to that browser profile, is sent again only when generation starts, and is deleted after a successful report or expiration. Model providers receive image content only for the requested analysis. Love Meter privacy prompts restrict analysis to visible color, composition, styling, atmosphere, and emotional presentation.

Cloudflare hosts the Love Meter Worker, D1 database, and related infrastructure. Google provides authentication. Stripe and PayPal process one-time credit purchases. DeepSeek and OpenRouter process text prompts, and OpenRouter processes photos through configured multimodal models. Love Meter privacy requires sending providers the information needed for the requested operation, but each provider also operates under its own terms and privacy practices.

Love Meter may use operational analytics when configured to understand aggregate page use and reliability. Advertising scripts load only when their public configuration is enabled. Love Meter privacy does not intentionally place complete private readings, raw Love Oracle questions, or photo object keys into public analytics events. Browser, network, and provider logs may still contain technical metadata such as timestamps, request paths, error codes, and IP-derived security information.

Love Meter stores payment provider, internal payment ID, provider transaction references, selected credit pack, expected amount, currency, status, timestamps, and idempotency information. This data supports amount validation, webhook processing, credit entry, refund investigation, and fraud prevention. Love Meter privacy does not include storing a complete card number, security code, or PayPal password.

Credit transactions record additions, spending, and refunds with amounts, descriptions, and links to related payments or readings. A reading uses an idempotency key so repeated requests do not repeatedly deduct credits. When generation fails, Love Meter records a corresponding credit return. Love Meter privacy retains financial and transactional records as reasonably necessary for accounting, security, dispute handling, and legal obligations.

Love Meter keeps account-linked results, readings, credits, and transaction history while the account is active or as needed to provide the service. Photo bytes are not retained server-side. A browser-only IndexedDB cache expires after 24 hours and is removed sooner after successful paid photo generation. Security, payment, or legal records may need a different retention period. Love Meter privacy aims not to retain private content longer than its product purpose requires.

Signed-in users can delete their account from Profile. Account deletion removes account-linked credits, private readings, result inputs, and authentication data according to the implemented deletion workflow. Browser-cached photos can be removed by clearing site data and are automatically cleared by the app after success or expiration. Contact contact@lovemeter.xyz if self-service deletion is unavailable or for another Love Meter privacy request.

Love Meter uses authenticated authorization checks, unguessable tokens, claim secrets, browser-local photo caching, webhook signature verification, amount validation, and database idempotency. Photo bytes are sent only inside authenticated analysis requests and are not written to the application database or server-side file storage. These safeguards support Love Meter privacy but cannot make any internet service perfectly secure. Use a trusted device, protect your Google account, avoid forwarding private reading links, and report suspected unauthorized access.

Depending on location, you may have rights to access, correct, delete, restrict, or object to certain processing. Contact Love Meter with a specific privacy request and the account email involved. Love Meter privacy requests are reviewed with the account and service context needed to respond safely. Love Meter may update this Privacy Policy when features, providers, laws, or practices change. Material Love Meter privacy updates will be posted on this page with a revised date.