Your data stays tied to the creator relationship
Last updated October 18, 2026
What changed: we added Anthropic (Claude) as our drafting AI, a table of service providers, a cookie table, and details on TikTok replies, images, AI tools you connect, children and California rights.
Loresta is operated by Michael Ngo, a sole proprietor, who is responsible for the personal data processed through the service.
What we collect
We collect account details, approved creator profile information, storefront settings, gift catalog data, connected social account identifiers, inbound conversation content, supporter names and contact details they choose to provide, purchases, creator-authored supporter notes, operational receipts, security events, and first-party activation events needed to run and improve Loresta.
How we use it
We use data to host creator pages, process creator transactions, maintain supporter context, enforce automation and commerce rules, secure accounts, troubleshoot delivery, process billing, alert creators to conversations that need a human, and show workspace results. We do not sell personal data or use private conversation content for advertising.
Supporter chat and memory
A creator may save relevant notes about a supporter relationship, such as an approved preference or fulfillment detail. Loresta separates supporter records by creator profile. Assistant replies can use only permitted context, creator-approved facts, and live commercial details. Supporters may ask the creator or Loresta to correct or remove information, subject to records we must retain for security, payments, disputes, or law.
Reply previews and voice learning
Public reply previews are processed to return the sample requested and are not saved by Loresta. If a creator opts into voice learning, Loresta temporarily reads replies the creator authored through a connected account, filters sensitive data, and saves a reusable style summary rather than the raw reply history. Creators can turn voice learning off and clear the learned summary.
Payment accounts and payouts
Stripe collects and processes creator identity, business, tax, bank, capability, verification, transaction, refund, payout, and dispute information under its own terms. Loresta embeds Stripe-managed tax settings and registration tools and stores only connected-account readiness, registration counts and countries, requirement codes, transaction references, and status needed to operate checkout and respond to refunds or disputes. Loresta does not store full card or bank credentials, or full tax-identification credentials.
Connected platforms
Social access is granted through OAuth. Tokens are encrypted at rest, limited to supported actions, and removed from active use when an account is disconnected. Provider data remains subject to each connected platform’s policies.
TikTok replies are posted publicly as comments. You’re responsible for what’s posted from your account.
Messages go to the AI tool you choose, at your request.
Delete Instagram or Facebook data
To stop access, sign in to Loresta, open Connections, and disconnect the Instagram account or Facebook Page. You can also remove Loresta through the connected platform’s app permissions. Disconnecting stops new imports and replies; it does not by itself erase records already received.
To request deletion of connected-platform records, email privacy@loresta.co with your Loresta account email and the Instagram username or Facebook Page involved. Do not send passwords or access tokens. We verify your authority, explain any records that must be retained for law or security, and confirm the outcome. Workspace owners can also request full workspace deletion through Settings and its privacy controls after signing in again. Deletion completes 14 days after the request, and the owner can cancel it by signing in before then. A platform-data request does not require you to delete your Meta account.
Where you use a managed social connection, SocialAPI processes authorization and inbox data for Loresta. A direct Meta connection communicates with Instagram or Facebook without that intermediary. We request supported account and inbox permissions; connecting an account does not activate automated replies.
Who receives information
We use service providers for hosting, storage and security (Cloudflare), payment processing (Stripe, including Link when you buy a Loresta plan through Stripe Managed Payments, where Stripe acts as merchant of record under its own privacy notice), email delivery (Resend), AI processing (Anthropic’s Claude to draft replies and read images you send; OpenAI for safety checks and as a backup drafter; and Typesafe AI for classifying messages, images and supporter notes, such as whether a note is private or what a message is asking for; Typesafe AI does not generate text), and optional product analytics (PostHog). Depending on the feature you use, those providers receive the account, contact, conversation, transaction or technical information needed to provide it. Creators receive information needed to manage their own supporter relationships. Connected social platforms receive requests you authorize. We may also disclose information when required by law or to investigate fraud and protect people's rights. A provider's own account or payment relationship with you is governed by its privacy notice.
Browser analytics and your choices
On the public site and Creator Pages, PostHog browser analytics and marketing-site campaign attribution are off until you allow them on this browser. When you are signed in to your creator dashboard, we count page views and feature use with cookieless analytics that store nothing on your device, use no personal identifier and record no sessions; choosing "Keep analytics off", Global Privacy Control or Do Not Track turns this off too. When allowed, we use a first-party random visitor identifier to understand which landing page, campaign or referring domain led to signup and purchase. We store approved campaign parameters and the referring domain, not full referring URLs, message content or arbitrary query parameters. Attribution lasts up to 90 days after your last visit. Session replay requires a separate opt-in and excludes sensitive routes.
Global Privacy Control and Do Not Track signals override permission for these optional browser analytics. We do not enable third-party advertising tracking across other websites. These controls cover PostHog and marketing-site campaign analytics; Creator Pages and discovery also record first-party visits and actions to report activity to creators. Payment and connected-platform services may process information under their own notices. Necessary sign-in, security, transaction and service-operation records continue regardless of this choice.
Service providers
Images in messages may be sent to Typesafe to sort them (for example fan art or payment screenshots). Only the label is kept.
| Provider | What it does | What it receives | Where |
|---|---|---|---|
| Cloudflare | Hosting, storage and security | What you use on the site, plus your IP address | Global network |
| Stripe | Payments, payouts, tax and plan billing | Payment, identity, bank, tax and transaction details | United States and other countries |
| Resend | Sending email | Email address and email content | United States |
| Anthropic (Claude) | Drafting replies and reading images | Message text, approved facts and images you send | United States |
| OpenAI | Safety checks and backup drafting | Message text | United States |
| Typesafe (Jev) | Sorting messages, notes and images by label | Message text and images. Only the label is kept. | Ask privacy@loresta.co |
| PostHog | Product analytics and error tracking | Page views, feature use and short error codes | United States |
| SocialAPI | Connecting Instagram, Facebook, X and TikTok | Account authorization, inbox messages and comments | Ask privacy@loresta.co |
| One-tap sign-in, on the sign-in page only | Your sign-in request | United States and other countries |
Cookies and browser storage
These are the cookies and browser storage Loresta sets. Optional analytics stays off until you allow it.
| Name | What it does | How long |
|---|---|---|
| loresta_affiliate | Remembers the partner link that brought you, so the partner gets credit at sign-up. Set only when you open a partner link. | 90 days |
| loresta-referral-code (browser storage) | Remembers a friend’s referral link, so the reward goes to them. | 30 days |
| __Host-loresta_session and __Host-loresta_csrf | Keep creators signed in and protect forms. | Up to 30 days (90 in the mobile app) |
| __Host-loresta_supporter and __Host-loresta_supporter_csrf | Keep supporters signed in to My Stuff and protect forms. | 30 days |
| loresta_analytics_consent (browser storage) | Remembers your analytics choice. | Until you clear it |
| PostHog analytics and error tracking | Counts visits and feature use when you allow analytics. Error tracking sends a short error code, never message content. | Until you close the tab; campaign attribution up to 90 days |
International users and privacy rights
Loresta is operated from California, United States. Our providers may process information in the United States and other countries. Availability of registration, payment processing and payouts varies by country; access to the website does not promise availability of every feature.
Where applicable privacy law requires a legal basis, we process information to provide the service you request, meet legal obligations, pursue legitimate interests in security and service operation, or with your consent for optional processing. Depending on your location, you may have rights to access, correct, delete or receive a copy of your information, restrict or object to processing, withdraw consent, or complain to your local data protection authority. Withdrawing consent does not change processing already performed lawfully. Contact privacy@loresta.co to exercise these rights or ask about providers and international-transfer safeguards. We verify requests proportionately and explain any legally permitted limits. Creators may separately be responsible for information they collect about their supporters.
When personal data from the European Economic Area, United Kingdom or Switzerland is transferred to the United States or another country, we rely on the safeguards our providers offer for that transfer, such as the EU–U.S. Data Privacy Framework or standard contractual clauses, where the law requires them. Contact privacy@loresta.co for details.
California privacy rights
California residents may ask us to tell them what personal information we collect, use and disclose, and to correct or delete it, and may not be treated unfairly for doing so. We do not sell personal information or share it for cross-context behavioral advertising. Send requests to privacy@loresta.co; we may need to verify your identity, and an authorized agent may act for you with your written permission.
We answer California requests within 45 days. If we need more time, we tell you why.
We honor Global Privacy Control for optional browser analytics. We don’t sell or share personal information, so there is nothing more to opt out of.
Personal information we collect, by category:
| Category | Examples | Why we use it | Who receives it |
|---|---|---|---|
| Identifiers | Name, email, handle, IP address | Run your account and keep it secure | Cloudflare, Resend, Stripe |
| Purchases | Orders, plan, payment references | Process payments and refunds | Stripe, the creator |
| Messages and content | Messages, notes, images | Show conversations and draft replies | The creator, Anthropic, OpenAI, Typesafe |
| Online activity | Page views, feature use, error codes | Keep Loresta working and improve it | PostHog, if you allow analytics |
| Payment and bank details | Held by Stripe; Loresta keeps only references | Pay creators and bill plans | Stripe |
Children
Loresta is not directed to children under 13, and we don’t knowingly collect their personal information. To have a child’s information deleted, email privacy@loresta.co.
Retention and control
Raw conversation and AI invocation content follows the workspace retention setting, which is limited to 30–365 days and defaults to 90 days. Operational telemetry is compacted into bounded reports and then removed on its published schedule. Browser continuity and short-lived authentication records expire sooner. Billing, payout, refund, dispute, provider-usage, security-audit, and named-operator records are kept separately for the period needed for financial, security, or legal obligations, with sensitive provider payloads removed where possible. An active investigation hold pauses the relevant cleanup until the hold is released. The dashboard lets workspace owners export records, disconnect accounts, and submit a verified deletion request. Confirmed deletion removes workspace records and stored media, subject to these limited records and any active hold.
Security and access
We use workspace isolation, encrypted credentials, short-lived sign-in links, role checks, CSRF protection, signed webhooks, idempotent payment processing, audit records, and restricted administrative operations. No internet service can promise absolute security.
The sign-in page loads Google Identity Services from Google to offer one-tap sign-in with your Google account. Google sees that request under its own privacy policy; no other Loresta page loads it, and you can always sign in with email instead.
Changes to this notice
We publish revisions on this page and update the date above. When a change requires additional notice or new consent under applicable law, we provide that notice or request consent before relying on the change.
Contact
Questions or privacy requests can be sent to privacy@loresta.co.