Lovingly Alpha Privacy Notice
Last updated: 2026-10-22
This notice explains how Lovingly, LLC (Lovingly, we) handles information in the invitation-only Alpha of the Lovingly Business Operating System through LUMA (Alpha). It covers information about the participating business, its authorized user and people whose information the business makes available through Alpha. It should be read with the Alpha Testing Agreement.
This notice applies to Alpha. Lovingly’s corporate website privacy policy covers visits to the corporate website; separate Lovingly product agreements and notices continue to apply to those products. This notice does not make Alpha part of a business’s existing Shop agreement.
Information Alpha handles
Account and billing information: the authorized user’s name, work email, sign-in and account records; business identity, website and selected location; Alpha eligibility and acceptance records; and subscription status. A card is required to complete the $0 Alpha enrollment. Stripe collects and holds card details through its hosted Checkout and may verify the card with its issuer. Lovingly receives payment-method and billing status needed to manage the Alpha account, not the full card number. Collecting the card does not authorize a later paid charge.
Business and connected-source information: information supplied by the business; its website homepage and About Us page, plus public website information checked during ongoing work, such as published hours; and information read from the one Google Business Profile location it connects, including existing unanswered and new reviews, replies, profile details and permitted current performance information.
Conversations and work: messages and instructions sent to LUMA, answers, business facts and memory, generated content, proposed or authorized actions, approvals, results and feedback, subject to the Google content limits described below.
Usage and diagnostics: events about use of Alpha; errors, logs, prompts, model inputs and outputs, tool calls and execution traces needed to operate, secure, troubleshoot and evaluate the service. These records can contain portions of Business Content, not just technical metadata, subject to the Google content limits described below.
Support and research: emails to the Alpha inbox, corrections, deletion and access requests, and notes from group or one-on-one feedback discussions.
We receive this information from the participating business and its user, connected services the user authorizes, the business’s public website, and our own operation of Alpha. Please provide only personal information needed for an authorized Alpha task.
Why we use it
We use Alpha information for the following purposes:
1. Run and support Alpha: manage accounts, answer requests, carry out authorized work, secure the service, fix problems and restore service.
2. Learn from Alpha: review use, results, errors and feedback to evaluate and improve the service.
3. Develop permitted general learnings: develop insights that do not reasonably identify a participant, reveal its confidential information or use source information whose terms prohibit that use. We exclude Google Business Profile API content and restricted derivatives. Alpha is a small group, so removing names alone may not make a finding nonidentifying.
If we propose to publish learnings drawn from information in a business’s account, we will obtain that business’s separate permission before publication, even if the proposed learnings would not reasonably identify it. We will also obtain separate permission before publishing its name, logo, quote, screenshot, identifiable result or endorsement. Permission does not override applicable law or source restrictions.
Operation, support, internal evaluation and product improvement are part of the Alpha relationship. There is no general switch that turns off internal product evaluation while continuing to use Alpha. Publication is a separate choice: declining publication permission does not end participation. We do not sell identifiable Alpha customer information.
Google Business Profile information is subject to Google’s rules. We use it for the selected business’s Alpha work, not for unrestricted aggregation or generalized learning. Google account connection and permission for specific actions or eligible standing review-reply delegation are handled separately from acceptance of the Alpha Testing Agreement.
Who may receive or review it
Assigned engineers and authorized support or security responders may review relevant conversations, business information and diagnostic records to operate, repair, evaluate and improve Alpha. Engineers may correct operating data when needed to restore or fix the service; actions on your connected accounts still require your permission. Alpha involves close human observation and troubleshooting. Other participating businesses do not receive access to your information.
We use service providers for identity and sign-in, hosting and storage, Stripe-hosted payment collection, AI model processing, Google connection, diagnostics, analytics, email delivery and support operations. They receive information needed for their assigned function. Actions you authorize may be sent to Google and become public under your business’s name. Google handles published content under its own terms. We may disclose information when disclosure is required by law or reasonably necessary and lawful to protect rights, safety or security.
We do not permit our AI model providers to train their general foundation models on Alpha customer content. Lovingly’s own use of information to evaluate and improve Alpha is described above.
How long we keep it
Retention depends on the information, its source and why it is needed. Google Business Profile information has stricter source limits.
We process Google review content and published review replies for current authorized work without retaining copies in saved conversations, Daily Briefs, business memory, work history or diagnostic records. We retrieve the current review and published reply directly from Google when needed, including when investigating a disputed action. Google content may change or become unavailable; we do not maintain a historical archive of that content.
Any temporary processing copy of that content, and any permitted copy of other Google Business Profile information, is kept only for a purpose and duration Google’s rules permit, never more than 30 days. That maximum does not authorize retaining review content or published review replies as diagnostic history.
At present, Alpha’s application database and diagnostic traces do not have a general automatic expiration period. Non-Google account, conversation, business-history and diagnostic records may therefore remain after Alpha access ends until they are deleted under an applicable request or an adopted retention rule, subject to legal, security and source-specific limits. Ending Alpha or disconnecting Google does not by itself delete every record.
We may continue internal evaluation and product improvement using information we may lawfully retain, subject to confidentiality, deletion requests and source restrictions. Publication remains subject to separate permission as described above. We may keep limited records needed to document acceptance, billing, security, incidents, approvals or actions where permitted or required, without retaining the Google content excluded above. We will explain any such limits when handling a deletion request.
Your choices and requests
To request deletion, access or correction of your data, email help@support.lovingly.ai. Alpha has no in-product data-deletion control. We handle applicable privacy requests as required by law. The Alpha Testing Agreement’s two-business-day commitment concerns review of emailed requests, not completed resolution, and does not change applicable legal rights or deadlines.
You can manage automatic review-reply permission in Settings → Authority, including requiring approval or narrowing or turning off a current standing delegation. A change made there applies to queued replies as well as new work and does not wait for email review.
You can remove your Google Business Profile connection through Settings → Connections → Manage. Disconnecting removes the Google permissions granted for Alpha and stops work through that connection. We also remove those permissions when Alpha access ends. Disconnecting or ending Alpha does not itself delete your saved Alpha data or information held by Google. Source-specific retention limits still apply.
You may decline a request for permission to publish learnings from your account without ending your Alpha participation.
Security and changes
We use measures intended to protect Alpha information and restrict access to authorized work. No online service can promise perfect security. Please tell us promptly at help@support.lovingly.ai if you believe an Alpha account or connection has been compromised.
We will notify affected participants of a confirmed compromise of their Alpha information in accordance with applicable law.
We may update this notice as Alpha changes. We will post the current version and provide additional notice or obtain new acceptance when a material change requires it. Before accessing a new type of Google user data or using Google user data in a way or for a purpose not previously disclosed, we will update this notice, notify you and obtain your consent. Any new use must still comply with Google’s restrictions. The date at the top will show when the published notice takes effect.
Contact
Lovingly, LLC
Attn: Privacy Request
169 Madison Ave STE 69244
New York, NY 10016
Alpha support and privacy requests: help@support.lovingly.ai