Data and privacy

Loresta keeps operational records apart from raw conversation text and applies a separate retention rule to each kind of data.

Protected contacts and notifications

Marking a contact as protected stops Loresta’s AI from drafting for them. You can still send them a reply you write yourself.

Phone alerts use general wording. They leave out supporter names, purchases, amounts and quoted messages from the lock screen. Opening one loads the checked in-app view.

When Loresta itself fails, it keeps a short seven-day record linked to the request reference. It holds safe labels, not error text, database queries, headers, request contents or conversations.

Imported message history

Importing past messages from a connected app is optional. Imported messages are marked for deletion after 30 days and removed unless a legal investigation requires a hold.

Other records follow their own retention rules, which are different from the 30-day rule.

Secrets

• Connection sign-in details are encrypted.
• Screens and exports leave out connection tokens and secrets.
• Exports remove any column that could hold a secret.

Account exports

You can ask for a download of your account data in Settings. It comes with a contents list and the count for each kind of data. If an export cannot include everything it needs, it fails instead of giving you part of your data.

Consent and communication

Importing message history, messages to supporters and public recognition are separate controls. Support cards keep names and amounts private by default. Marketing messages to supporters need the consent they recorded with you.

What to share with support

• Send the request reference, the time, the page you were on and what happened.
• Do not send passwords, access tokens or full private messages. Describe them instead.
• Do not put private supporter details in screenshots you share publicly.

See security and settings, team, billing, and payouts.