This policy explains how JoyReply handles data for creators and brands as the product expands from Facebook read-side workflows into a broader creator workspace. Last updated April 22, 2026.
JoyReply may process account and brand settings, connected social account identifiers, encrypted access credentials where applicable, recent Page or channel posts, comments, Page replies, reply suggestions, content drafts, calendar items, uploaded knowledge or PDFs, reply examples, audience signals, protection logs, audit logs, support messages, and technical diagnostics needed to run the service.
We use this data to connect authorized channels, sync comments, show an inbox, detect buying intent, identify clear abuse, prepare replies and content drafts in the right language and tone, keep saved brand context, suggest post ideas, build manual content plans, provide support, prevent abuse, secure accounts, and comply with legal or platform obligations.
JoyReply currently accesses only Facebook Pages that a user explicitly authorizes. We use Page data to sync posts and comments, detect abuse and buying intent, prepare editable reply and content drafts, group likely abuse for review, and keep saved brand context for that account.
Comments, Page context, knowledge notes, approved replies, and creator rules may be processed by AI features to classify comments, prepare replies, summarize saved brand context, create audience signals, and draft content ideas. Customer content is used to serve that customer account, not to train a shared JoyReply system.
Paid plans and trials can include drafted replies, scans, and post ideas. Manual review, local ignore or done states, copy reply, and open-post actions stay available separately from those included suggestions.
Page access credentials are stored encrypted and used only for the approved connected-Page workflow, such as listing authorized Pages, syncing posts and comments, and showing post or comment context. Public posting, moderation, publishing, DMs, and other action features stay manual or disabled unless the relevant platform approves additional permissions later.
When paid plans are enabled, JoyReply may store plan, invoice, tax, payment status, and subscription metadata. Card details are handled by the payment processor, not stored directly by JoyReply.
JoyReply uses essential authentication cookies and browser storage for preferences such as selected brand, theme, and language. We do not currently need advertising cookies for the core product.
We may use trusted services for hosting, databases, AI processing, Meta integrations, email/support, payments, logging, and security. We do not sell customer content or Page data.
We keep account, connected-channel, comment, draft, planning, billing, and audit data while the account is active and as needed for security, fraud prevention, legal obligations, accounting, dispute handling, or support. Users can disconnect a channel or request deletion.
You can ask for access, correction, deletion, restriction, portability, or objection where applicable. We may need to verify the request before changing or deleting account data.
For access, correction, export, or deletion requests, write to privacy@joyreply.com. Include the email used for JoyReply, the connected brand or Page name if relevant, and the action you want us to take.