Privacy Policy

“Rajlav AI,” “we,” and “our” refer to the Rajlav AI service. This policy covers information handled through the Rajlav AI website and SaaS workspace. A business using Rajlav AI is responsible for deciding what customer information it submits and for providing any notices or obtaining any permissions required for its use.

• Account information, such as a user's name, email address, authentication records, and workspace membership.
• Business information entered by a workspace, such as its name, industry, website, hours, services, appointment settings, and approved knowledge sources.
• Customer information and conversation content that a business receives through Website Chat or a connected channel, including contact details, messages, lead details, and related operational records.
• Integration information needed to connect and operate a channel, such as provider account identifiers, connection status, and server-side credential references.
• Usage and technical information needed to operate the service, troubleshoot failures, protect accounts, and measure provider usage.

We use information to provide and maintain accounts and workspaces, answer customer questions through configured channels, organize leads and conversations, support appointments and follow-ups, administer subscriptions, provide customer support, secure the service, and diagnose technical issues.

When a business uses AI features, message content and relevant business context may be sent to the AI provider configured for that service to generate a response or perform a supported task. AI-generated output can be inaccurate. Businesses should review their configuration and remain responsible for how they use generated content and actions.

Rajlav AI records provider, model, token-usage, outcome, and estimated-cost metadata for operational and cost monitoring. The usage-event records are designed not to store prompts, completions, or customer message bodies.

When a business connects Meta-powered channels (such as Facebook Pages, Instagram Professional/Creator accounts, or WhatsApp), Rajlav AI processes platform data on behalf of that business workspace:

• Facebook Page Connections: When a business connects a Facebook Page, Rajlav AI receives page identifiers, name, and scoped tokens (such as pages_show_list, pages_read_engagement, pages_manage_metadata, and pages_messaging). These credentials are used solely to receive incoming events, post configured replies, and send authorized messages on the Page's behalf.
• Instagram Professional Connections: When an Instagram Professional or Creator account connected to a Facebook Page is linked, Rajlav AI receives account identifiers, username, profile details, and permissions (such as instagram_business_basic, instagram_business_manage_messages, and instagram_business_manage_comments) to operate requested automations.
• Comments and Messages Processing: When an end-user comments on a post or reel, or sends a direct message to a connected account, Rajlav AI processes the webhook notification. The comment or message content is evaluated against the business workspace's configured rules (such as keyword matching) to deliver automated public comment replies, direct message replies (Comment-to-DM), or lead capture responses.
• Webhook Data: Webhook events from Meta (including sender IDs, comment IDs, timestamps, and message bodies) are processed in real time to deduplicate triggers, manage conversation threads, and provide live inbox visibility to authorized workspace team members.
• Workspace Access Controls: All Meta platform data, connection credentials, and customer conversation records are strictly scoped to the authorized business workspace. Team members can only access social data for the workspaces they are explicitly permitted to view.
• Disconnection and Deauthorization: A business can disconnect Facebook, Instagram, or WhatsApp at any time in workspace settings. Disconnection disables server-side credential references and stops automated event handling. If a user removes Rajlav AI from their Meta account settings, Meta dispatches a deauthorization or data-deletion callback to our endpoint, which records a privacy receipt. Disconnecting or deauthorizing alone does not delete historical conversation records already stored in the workspace; to request deletion of stored records, refer to the Data Deletion Instructions.
• No Data Brokerage or Advertising Use: Rajlav AI does not sell Meta platform data, does not use customer message or comment content for cross-context behavioral advertising, and does not share platform data with unauthorized third parties.

WhatsApp access is currently offered through controlled Early Access. All Meta and WhatsApp platform integrations remain subject to Meta’s terms and platform policies.

We use service providers to host and operate the application, store business records, deliver configured AI features, process payments, and connect third-party messaging services. Information is shared with a provider only as needed for the requested service, security, or operational support. Each provider may process information under its own terms.

Businesses may connect third-party services. Their use of those services is also subject to the third party's terms and privacy notices.

We use technical and organizational measures intended to protect information, including account authentication, business-scoped access controls, and server-side handling of integration credentials. No internet service can guarantee absolute security.

We retain account, business, conversation, and operational information while needed to provide the service, meet operational requirements, resolve disputes, and comply with applicable obligations. Retention periods can vary by record type and provider. Backups and recovery copies may persist under operational processes and are not immediately changed by a deletion request. We do not specify a deletion timeframe here.

To request deletion of an account or data, follow the Data Deletion Instructions. A request may require identity and business-authority verification. Disconnecting a channel alone does not delete stored business or conversation data.

Depending on where you live and your relationship to a Rajlav AI customer, you may have rights to request access, correction, deletion, restriction, or a copy of personal information. A business administrator may need to submit requests for information processed on that business’s behalf. We may need to verify a request before acting.

The workspace uses browser storage to maintain the signed-in session. The Meta JavaScript SDK may use browser storage or cookies when a user chooses to start Meta Embedded Signup. This policy does not represent that optional analytics or advertising cookies are currently used.

Rajlav AI is offered to users in India. Service providers may process information in other locations, subject to their terms and applicable safeguards. We may update this policy as the service changes; the updated date above identifies the latest version published here.

For privacy questions or requests, email support@rajlav.co.in. See the Data Deletion Instructions to request deletion.