Privacy Policy for Meta/Facebook Connection

This Privacy Policy explains how INHAYAT handles information connected to our Meta/Facebook integration, including Facebook Login, Facebook Pages, Lead Ads forms, and lead delivery webhooks.

INHAYAT is an adult-only ecommerce service for intimacy products. Because the nature of our products may be sensitive, we limit Meta-related data collection and use to what is needed to connect Facebook lead forms to our internal order workflow.

When an administrator connects a Facebook account, we may receive the administrator's Facebook user ID, display name, access token, Page list, Page IDs, Page names, Lead Ads form IDs, form names, and related permissions granted by Meta.

When a customer submits a Facebook Instant Form connected to INHAYAT, we may receive the fields configured in that form, usually customer name and phone number, plus Meta delivery metadata such as lead ID, form ID, Page ID, campaign ID, ad ID, ad set ID, and creation time.

We do not receive or store Facebook passwords. We do not request private messages, friend lists, personal posts, or unrelated Facebook profile content for this integration.

We use administrator connection data to keep the Facebook Page and Lead Ads form connection active, sync available forms, subscribe to leadgen webhooks, monitor delivery status, and troubleshoot failed requests.

We use customer lead data to create lead orders, contact the customer about the submitted inquiry, confirm product quantity and delivery details, and process the related order when the customer confirms.

We do not use Meta-derived lead data to build sensitive interest profiles, and we do not send the customer's adult-product interests back to Meta through our server-side lead forwarder.

We do not sell Meta-derived personal data.

Meta data may be visible to authorized INHAYAT administrators and staff who need it to operate lead intake, customer contact, order confirmation, delivery, security, auditing, and support.

We may disclose information if required by law, court order, regulatory request, security investigation, or to protect our rights, users, staff, and services.

Facebook access tokens and Page/form connection records are stored only for as long as the administrator keeps the integration active or as needed to operate the lead forwarding service.

Lead order records may be retained as part of customer service, order fulfillment, accounting, anti-fraud, dispute handling, and legal compliance.

Webhook request logs are kept for operational monitoring and retry/debugging, and may be deleted or minimized when no longer needed.

If a Facebook user removes our app or requests deletion through Meta, Meta may send a signed deletion request to our Data Deletion Callback URL. We verify the request, delete stored Facebook connection tokens for that Meta user, disable related form mappings, remove related forwarder request logs, and return a confirmation code with a status URL.

Administrators can also disconnect their Facebook account from the INHAYAT cpanel lead forwarder page. Customers may request deletion or correction of lead/order contact information by contacting us through Telegram.

We use access controls, authenticated admin endpoints, signed OAuth state validation, Meta signed request validation for deletion callbacks, and operational logging to protect integration data.

No internet service can be guaranteed to be completely secure, but we limit access to Meta data to operational needs and remove or disable integration data when deletion is requested.

Facebook administrators can remove INHAYAT's access from their Facebook or Meta Business settings, or disconnect the integration from the INHAYAT cpanel.

Customers who submitted a lead form may ask us to review, correct, or delete their contact information where applicable. Some records may be retained if required for accounting, legal, security, or dispute-resolution purposes.

For privacy questions, Meta/Facebook connection questions, or data deletion support, contact us through Telegram at @inhayat_bot.

We may update this Privacy Policy as our Meta integration, business operations, or legal requirements change. The latest version will be published on this page with the updated date.