Privacy Policy

Lavin Reply is a service that reads messages and comments from the Facebook Pages, Instagram accounts and WhatsApp Business accounts you connect, and sends replies and messages on their behalf according to rules you configure. This policy covers the Lavin Reply website and application. It does not cover Meta's own handling of your data, which is governed by Meta's privacy policy.

Account data you give us directly:

• Your name and email address, used to identify your account.
• Your password, stored only as a hash by our authentication provider — we never see or store the password itself.

Data received from Meta when you connect an account:

• Page, Instagram and WhatsApp Business account identifiers, names and profile pictures for the accounts you select.
• Page access tokens, which allow Lavin Reply to read messages and send replies as that Page. These are credentials and are treated as secrets.
• The content of direct messages sent to your connected accounts, including text, attachments' metadata, timestamps, and the sender's platform ID and display name.
• The content of comments left on your posts, including text, timestamps, and the commenter's platform ID and display name.
• WhatsApp phone numbers of the people who message your WhatsApp Business account or whom you add as contacts.
• The content of WhatsApp messages sent to and from your WhatsApp Business account, including text, timestamps and the sender's display name.
• The content of the WhatsApp message templates you create.
• Each WhatsApp contact's marketing opt-in or opt-out status.

Data the service generates:

• A log of the replies Lavin Reply sent, which rule matched, and when.
• Webhook delivery records used to avoid replying to the same event twice.
• Basic technical logs such as error traces and request timestamps.

We do not collect data from your personal Facebook profile beyond what is needed to establish that you administer the accounts you connect, and we do not post to your personal profile.

• Message and comment content is matched against your reply rules — this is the core function of the service and it cannot work without reading the message.
• Page and WhatsApp access tokens are required by Meta's APIs to read and send on behalf of an account you administer.
• WhatsApp phone numbers, message templates and opt-in status are used to send and receive WhatsApp messages and to respect each person's choice about marketing messages.
• The reply log exists so you can see what was sent in your name and correct a rule that behaved unexpectedly.
• Webhook records prevent duplicate replies when Meta re-delivers the same event.
• Account data identifies you and controls what you and your team members can access.

We do not sell your data, we do not share it with advertisers, and we do not use message or comment content to train machine learning models.

Data is stored in a managed Postgres database provided by Supabase, hosted in a data centre region selected for the project. Access is restricted by row level security so an account can only read its own records. Data is encrypted in transit over HTTPS and encrypted at rest by the hosting provider.

Page access tokens are held server-side only. They are never sent to the browser and never exposed in the application interface.

You can ask us to delete Meta Platform Data sooner at any time — see our Data Deletion page. The 90-day period applies automatically as messages age, and when a channel is disconnected the remaining data is deleted within 30 days. A direct deletion request is completed within 30 days and takes priority over the 90-day period. In short: the 90-day period runs while an account is connected, and the 30-day deadline starts when you disconnect an account or ask us to delete your data — they are different triggers and do not conflict.

We use the service providers below to run Lavin Reply. Each processes data on our instructions. We may also disclose data if required by law.

Inside your own account, team members you invite can see the inbox and the reply log for the accounts they are given access to.

When AI replies are switched on for your account, we send the incoming customer message, the recent messages in that conversation, and the reply instructions you have configured to an AI provider, which generates the reply text. We use Anthropic's Claude API and Google's Gemini API; if one is unavailable the other is used so replies keep working.

AI replies are off by default. You can switch them off at any time. Replies generated this way are labelled "AI" so your customers can see them.

When we test new features we use sample messages we write ourselves, never real customer conversations.

You can disconnect a Page, Instagram or WhatsApp account at any time from the connection settings in the application. Disconnecting immediately stops Lavin Reply from receiving events for that account and from sending any further replies, and deletes the stored access token for it.

You can also remove Lavin Reply from the outside, in your Facebook settings under Business Integrations. Doing so revokes our access even if you cannot reach the application.

To have your data deleted, email privacy@allsaferai.com from the address on your account and say which you want: deletion of a specific connected Page's data, or deletion of your whole account.

We will confirm the request and complete it within 30 days, then write back to tell you it is done. Deleting your account removes your profile, your rules, your reply log and all stored message and comment content. Backups are rotated out within a further 30 days.

You can ask for a copy of the data held about you, ask for it to be corrected, or object to how it is being processed, using the same contact address. If you are in a jurisdiction that grants you statutory data protection rights, this policy is not intended to limit them.

If this policy changes materially, we will update the date at the top and notify account holders by email before the change takes effect.

Questions about this policy or about your data can go to privacy@allsaferai.com.