Request early access

Privacy Policy

Last updated: October 9, 2026

1. OVERVIEW AND ROLES

USLY LLC (“USLY”, “we”, “our”, “us”) provides websites, booking and business software for service businesses. This Policy describes information handled when you visit USLY’s own website, contact us, create an account, or use a USLY-powered service.

USLY determines the purposes and means of processing for its own website, accounts, billing, security, and Platform Analytics. When a business uses USLY to handle its clients’ bookings, files, or messages, that business generally determines the purpose of that processing and USLY provides the service on its behalf.

This Policy is a description of our current practices, not a statement that every privacy law applies in every situation.

2. WHO WE ARE

USLY LLC
1047 Rodeo Way, Unit 5
Sacramento, CA 95819, USA

Email: [email protected]

If your request concerns a business using USLY, that business may need to answer it. We will help route or support the request where appropriate.

3. INFORMATION WE HANDLE

  • Account and workspace data: name, email, login and security records, workspace details, roles, settings, and support communications.
  • Service data: information submitted for bookings, client management, forms, messages, uploads, digital products, or other features selected by a business.
  • Billing data: subscription, order, transaction, and payment-status records. Stripe processes payment-card details; USLY does not store full card numbers.
  • Contact and lead data: information you enter in a USLY contact or launch-interest form, together with limited source and request context used for response, security, and attribution.
  • Security and operations data: server and edge records that may include an IP address, timestamp, request route, browser or device information, error information, and authentication or abuse-prevention events.
  • Optional Platform Analytics: the minimized first-party data described below, only after an explicit choice to accept.
  • Tenant Analytics: minimized tenant-site activity, consent evidence, and approved booking, purchase, payment, and refund statistics when a business enables the feature.

4. OPTIONAL PLATFORM ANALYTICS

Platform Analytics measures visits and interactions on approved USLY marketing pages and whether a separate USLY launch-interest form was submitted. It is first-party, optional, and off until you select Accept.

After acceptance, USLY creates a pseudonymous handle tied to the exact website origin. Analytics may record closed page, section, call-to-action, demo, scroll, form-attempt, and lead-created event keys; coarse direct/internal/external referrer categories; and campaign labels authored by USLY.

The analytics records do not contain raw URLs or queries, raw referrers, IP addresses, user-agent strings, contact details, form values, advertising click IDs, or a Django session identifier. The separate contact form may still process the information you submit and its own limited request context.

The handle works for at most 24 hours and becomes unusable after 30 minutes without accepted activity. Raw analytics rows expire within 90 days. Consent-choice evidence and suppressed aggregate reports may remain for up to 25 months. Low-volume campaign details are hidden.

Declining, closing the notice, pressing Escape, scrolling, navigating, or submitting a form does not grant consent. You may later use Privacy choices to withdraw. Withdrawal stops future collection; a separate verified request may be needed to delete earlier records. A strict Global Privacy Control or Do Not Track signal keeps this optional analytics off under USLY’s product policy.

USLY does not use Platform Analytics for targeted advertising, sale or sharing of personal information, cross-site tracking, eligibility or pricing decisions, sensitive inferences, individualized profiles, or AI/model training.

5. TENANT ANALYTICS

A business using USLY may enable Tenant Analytics for its own public website. The business determines the limited measurement purpose and is generally the controller or business. USLY operates Tenant Analytics for that business as its processor or service provider. USLY keeps its separate account, billing, security, support, and Platform Analytics purposes outside this tenant-controlled analytics purpose.

Optional website measurement. Browser-based Tenant Analytics is off until a visitor selects Allow analytics. After permission, USLY may issue a pseudonymous handle limited to the exact tenant-site origin and record approved visit, page-area, campaign, booking-step, and purchase-step event keys. Approved website activity may be connected to an authoritative booking or purchase outcome for aggregate reporting.

Before a choice, a campaign link may place one opaque campaign code in the current tab's temporary session storage for no more than 30 minutes. It is not a visitor identifier or event, sends no analytics request, and is deleted on use, decline, withdrawal, expiry, or a tenant boundary.

Operational and money statistics. A business may use its ordinary booking, order, payment, and refund records to count completed outcomes even when browser analytics is off. When money reporting is enabled, Tenant Analytics may prepare aggregate statistics from successful payment and refund amounts, currency, and the approved transaction purpose. It does not connect an outcome to an unconsented browser journey, combine currencies, or provide accounting, tax, or financial advice.

Tenant Analytics is designed not to store names, contact details, form entries, message content, raw URLs or queries, raw referrers, IP addresses, user-agent strings, advertising click IDs, full payment-card or bank details, medical records, diagnosis or treatment information, or health histories. Excluding direct names does not make every record anonymous.

The exact-origin handle expires after 45 days without accepted activity or 90 days from issue, whichever happens first. An individual visit becomes inactive after 30 minutes without accepted activity and lasts no more than 24 hours. A pre-choice opaque campaign code remains only in the current tab for no more than 30 minutes. Raw minimized visits and events remain for no more than 90 days. Booking, purchase, payment, refund, consent, governance, and aggregate records remain for no more than 25 months under their applicable lifecycle. Detailed security rejection records remain for no more than 7 days, network tokens for no more than 24 hours, and minimized security counters for no more than 30 days.

Keeping analytics off does not affect browsing, booking, or purchasing. Global Privacy Control is a hard deny. Do Not Track keeps optional browser measurement off until an explicit choice; Allow analytics may enable this first-party measurement when no hard prohibition applies. If Do Not Track appears after a grant, collection stops and requires a new explicit choice. Withdrawal stops future browser collection; deletion is a separate verified request. The business is the first contact for tenant-controlled records, and USLY assists the business where appropriate.

USLY does not sell Tenant Analytics data or use it for cross-context behavioral advertising, cross-site tracking, cross-tenant or individual profiles, eligibility or pricing decisions, or AI/model training. An authorized business user may separately instruct USLY to share aggregate reports with a connected assistant as described below.

Tenant Analytics is limited to non-clinical beauty businesses. It is not a medical-record system, is not authorized for medical records, clinical workflows, diagnoses, treatments, or health histories, and is not offered under a HIPAA business associate agreement. USLY does not promise to continuously inspect or medically classify all customer content.

6. CONNECTED ASSISTANTS (MCP)

You may connect an assistant, such as ChatGPT, to USLY through the Model Context Protocol (MCP). You sign in with USLY, choose the sites to share, and approve the requested permission groups. These may cover service and category images, VIP images, portfolio content, SEO settings, and aggregate analytics. Each request remains limited by the connection's permissions and your current access to the selected site. New sites or permissions require a new authorization.

Information exchanged. USLY receives the specific tool inputs and attachments sent by the connected assistant, not your full conversation history. Inputs may include search text, site and content identifiers, proposed text and SEO changes, publication choices, image display settings, and attachment identifiers, download addresses, filenames, file types, and image bytes. Results sent back may include site names and subdomains, selected content and its identifiers, descriptions, image URLs and ALT text, publication and display settings, SEO previews, and the status of requested changes. Authorized results can include unpublished content. This exchange lets the assistant carry out and discuss the actions you request.

Image attachments. USLY downloads and validates the submitted image, including its format, size, dimensions, and download address. Accepted images are stored as original files; validation does not strip embedded metadata. Images uploaded for these website features use public content-delivery URLs. A draft or unpublished item's image may therefore still be accessible to someone with its direct URL. Remove private information, including embedded location metadata, before submitting an image you intend to use publicly.

Analytics sharing. Sharing analytics requires the analytics permission and acceptance of the Tenant Analytics Connected Agent Addendum for the selected sites. USLY then sends the aggregate reports you may currently access, including metric definitions, reporting periods, time zones, freshness, and suppression or availability states. This permission also allows the assistant to request and check preparation of Today's report. It does not expose individual visitor records or raw events, activate browser analytics, or authorize model training. USLY keeps the accepted agreement version and time and the existing report-access audit records.

Connection and operational records. We keep the account-to-connection relationship, selected sites, permissions, authorization and revocation information, and records needed to prevent repeated content changes or recover their results. File-management records help track uploads, attachment status, and safe cleanup. Limited MCP diagnostics record tool names, outcomes, error categories, and attachment hostnames when available. These tool diagnostic events exclude full download URLs, file contents, and raw tool inputs. We use these records to control access, protect the service, troubleshoot failures, and carry out authorized actions.

Your controls and the recipient. You can review and revoke a connection in Your connections in USLY. Revocation stops further access through that connection; it does not undo completed changes, erase uploaded files or connection records, or retract data already sent to the assistant. The assistant and its provider are recipients you select. Their own terms, privacy policies, and account settings govern their use and retention of received copies; they are not made a USLY-selected analytics processor merely by your connection. See Retention and Choices & Rights for deletion requests.

7. WHY WE USE INFORMATION

  • Provide, configure, support, and improve requested services.
  • Authenticate users, protect accounts, prevent abuse, diagnose failures, and maintain availability.
  • Process subscriptions, orders, payments, refunds, and accounting records.
  • Respond to inquiries and send service, booking, billing, or support communications.
  • Measure USLY marketing performance when Platform Analytics consent is active.
  • Provide a business's limited Tenant Analytics reports under its instructions when that feature is enabled.
  • Comply with applicable legal obligations and establish, exercise, or defend legal claims.

Depending on the context and applicable law, these activities may rely on performance of a contract, consent, legitimate interests, or a legal obligation. Consent is the basis selected by USLY for optional Platform Analytics.

8. SMS AND COMMUNICATIONS

If you choose appointment-related SMS, USLY may process a phone number, consent choice and timestamp, opt-out state, message status, and booking context needed to send the requested transactional messages.

USLY does not sell or share mobile numbers or SMS opt-in data for third-party marketing. A business you interact with receives the information needed to provide its service. Messaging providers process delivery data on our behalf.

See the SMS Terms for messaging-specific details.

9. PROVIDERS AND DISCLOSURES

We disclose only the information reasonably needed for a provider to perform its function. Current provider categories include:

  • AWS for application hosting, databases, storage, backups, logs, and email infrastructure.
  • Cloudflare for DNS, content delivery, TLS, and edge security.
  • Stripe for subscriptions, connected commerce, and payment processing.
  • Twilio and communications providers when messaging features are used.
  • OpenAI or other feature-specific providers only when an enabled AI feature requires processing of submitted content.
  • The business whose USLY-powered service you intentionally use.

When you connect an assistant, we also send the authorized tool results to that assistant and its provider at your direction, as described in Connected Assistants. Publicly used website content and images may be accessed by website visitors and others with their public URLs.

We may also disclose information when reasonably necessary to comply with law, protect people or the service, investigate abuse, complete a corporate transaction, or establish or defend legal claims.

USLY does not sell personal information and does not share it for cross-context behavioral advertising.

10. COOKIES AND LOCAL STATE

  • Essential cookies support login sessions, CSRF protection, security, and requested site functions.
  • Platform Analytics handle is a Secure, HttpOnly, same-site, host-only cookie created only after acceptance. It expires within 24 hours and cannot be used on another origin.
  • Tenant Analytics handle is a separate Secure, HttpOnly, same-site, host-only cookie created only after acceptance on an enabled tenant site. It expires after 45 days without accepted activity or 90 days from issue, whichever happens first, and is limited to that exact origin and tenant purpose.
  • Display-only browser state remembers whether this tab showed an accepted, declined, or withdrawn choice. It is not durable legal evidence and cannot authorize server collection.

You can use the on-page Privacy choices control or browser controls. Blocking essential cookies may prevent requested features from working.

11. SECURITY

USLY uses measures selected for the size and risk of the service, including encrypted connections, network restrictions, access controls, application authorization, backups, logging, rate limits, and data minimization. No system is completely secure.

Report a suspected security or privacy issue to [email protected]. Please do not email passwords, payment-card details, health information, or other unnecessary sensitive data.

12. RETENTION

We keep information only while it is reasonably needed for the purpose described, an active service, security, accounting, dispute resolution, or an applicable legal obligation. Retention differs by record type.

  • Platform Analytics raw visits, events, and closed handle shells: no more than 90 days.
  • Platform Analytics security detail: up to 7 days; minimized counters: up to 30 days.
  • Platform Analytics consent evidence, access audits, released-hold evidence, and aggregate reports: up to 25 months under their specific lifecycle.
  • Tenant Analytics raw minimized visits and events: up to 90 days.
  • Tenant Analytics exact-origin handle: 45 days without accepted activity or 90 days from issue; individual visits: 30 minutes without accepted activity or 24 hours absolute.
  • Tenant Analytics booking, purchase, payment, refund, consent, governance, and aggregate records: up to 25 months under their specific lifecycle.
  • Tenant Analytics detailed security rejection records: up to 7 days; network tokens: up to 24 hours; minimized security counters: up to 30 days.
  • Backups may retain a deleted record until the configured restore window expires. Analytics deletion tombstones are replayed after a restore so matched records are not silently revived.
  • Account, transaction, booking, communication, and business records follow their operational and applicable legal needs.
  • Application and MCP diagnostic logs in AWS CloudWatch have a configured retention period of 14 days. AWS completes physical deletion asynchronously after expiry. This period applies to these log groups, not to the separate database records described below.
  • MCP connection, authorization, and content-operation records are stored in USLY's database separately from diagnostic logs. They retain the selected sites and permissions, consent evidence, and information needed to prevent repeated operations. These records do not currently have a fixed automatic deletion period. Revoking access or expiring a credential does not delete them. Contact us to request review and deletion of records associated with your account or site.

Uploaded files. Businesses manage the images attached to their site content and choose when to replace or remove them using the available site controls. Clearing, replacing, or deleting an image from a site removes its attachment reference; it does not immediately erase the stored original. Our target is to remove eligible unreferenced images from active storage within 15 days after their last attachment is removed or replaced. This is a target, not a guaranteed maximum: cleanup runs weekly and requires a protective waiting period and checks for ownership, remaining attachments, uploads in progress, and recovery needs. An unfinished maintenance pass, a processing failure, or unmet recovery checks can extend the period. Files whose history or ownership cannot be verified, and files outside the supported cleanup process, need separate review.

Public file URLs and cached copies may remain accessible after an image is detached. Storage versions, backups, security records, and copies already received by a connected assistant have separate retention lifecycles; removing an attachment or revoking a connection does not erase all such copies. Contact us for an uploaded-file deletion request rather than relying on detachment or scheduled cleanup.

Legal obligations or a specific dispute may require a narrow record to be retained longer. A legal hold does not authorize new analytics collection or broader access.

13. LOCATIONS AND TRANSFERS

USLY is based in the United States, and our providers may process information in the United States and other locations where they operate. Where an applicable law requires a transfer safeguard, we use an available contractual or other lawful mechanism appropriate to that transfer.

14. YOUR CHOICES AND POSSIBLE RIGHTS

Depending on your location, relationship with USLY, and applicable law, you may have rights to request access, correction, deletion, portability, restriction, or objection, and to appeal or complain to a regulator. These rights are not identical everywhere and may have exceptions.

You may withdraw optional Platform Analytics through Privacy choices. On an enabled tenant site, the Tenant Analytics notice links to that business's protected privacy section and provides the current allow, keep-off, and withdrawal controls. You may opt out of SMS by following the message instructions. Account and marketing-email controls are available through the relevant service or message.

Send a request to [email protected]. Describe the service or business involved and the request. We may need proportionate verification and will avoid collecting extra identification when a narrower method works.

California privacy statutes apply only when their coverage requirements are met. Regardless of coverage, USLY’s current product policy is not to sell personal information or share it for cross-context behavioral advertising.

15. CHILDREN

USLY’s own marketing website and business software are not directed to children. If you believe a child submitted personal information to USLY without appropriate authorization, contact us so we can review and take appropriate action.

16. CHANGES

We may update this Policy as the service or our practices change. We will update the date above and provide additional notice when a material change requires it. A new Platform Analytics or Tenant Analytics purpose, or a materially changed consent notice, requires a new version and a new choice where applicable; an old choice is not silently reused.

17. CONTACT

Privacy, security, or rights questions:

USLY LLC
1047 Rodeo Way, Unit 5
Sacramento, CA 95819, USA
Email: [email protected]

Platform Analytics privacy notice

Optional first-party Platform Analytics

USLY uses first-party Platform Analytics only to measure how visitors reach approved USLY marketing pages, interact with approved page sections and calls to action, and submit the separate USLY launch-interest form.

If you accept, USLY creates a short-lived pseudonymous handle and may later record closed page and interaction keys, a coarse referrer category, and authored campaign labels. These labels are observations, not verified identities or proof that an action caused a result. Platform Analytics does not collect raw URLs, query strings, fragments, raw referrers, IP addresses, user-agent strings, contact details, form values, click IDs, or a Django session identifier.

The handle is not described as anonymous. It becomes unusable after 30 minutes without accepted activity and always within 24 hours. A closed, scrubbed handle shell and future raw visit or event rows have a 90-day maximum. Unlinkable consent-decision evidence expires 25 calendar months after the decision. If non-identifying aggregate counts are later implemented, they may be retained for at most 25 months from the reporting period end, with no handle, visit drilldown, or low-volume label.

USLY treats a strict server-observed Global Privacy Control (Sec-GPC: 1) or Do Not Track signal (DNT: 1) as a choice to keep this optional analytics off. If a valid handle already exists, either signal fences future collection. Signal values are not stored. This is a conservative USLY product rule, not a claim that either signal has the same legal effect everywhere.

You can decline with the same prominence as accepting. Closing this notice, pressing Escape, scrolling, navigating, using a form, or agreeing to contact messages does not grant analytics consent. Privacy choices remains available to withdraw later. Withdrawal stops future collection and does not by itself delete previously accepted rows, which keep their ordinary retention clock. Deletion and other privacy-right requests are separate; contact [email protected] to ask about applicable controls and verification.

Platform Analytics is separate from analytics used on tenant business websites and is not used for cross-context advertising, sale or sharing, remarketing audiences, individualized profiling, sensitive inference, eligibility, pricing, booking decisions, AI recommendations, or general model training.

This information is handled only by the USLY operator and infrastructure providers needed to host and protect the service. See the USLY Privacy Policy for provider, retention, rights, and contact details. This notice describes the product behavior; it is not a certification of compliance with every law.

Notice version notice-en-us-v2; purpose version purpose-platform-marketing-v1; effective 2026-08-08; locale en-US.

Privacy Policy · Cookies and analytics choices

Accepting starts a new independent choice. Withdrawing attempts to stop a valid current Platform Analytics handle; the response never reveals whether one existed.