Skip to content
EmpAI
  • For local businessesAI Phone Agent Early accessAnswers every call, day and nightAI Chat Agent Early accessTurns website visitors into customersAI SMS Agent Early accessText follow-ups, quotes and payment linksSolutions by industryDentists, law firms, plumbers and more
  • For online sellers & vendorsShopify Automation Early accessListings, stock checks, store chat and phoneMarketplace Automation Early accessTikTok Shop, Walmart, Amazon, Etsy and retailers
  • Pricing
  • About
  • Contact
Log in Get Started
Local businessesAI Phone AgentAI Chat AgentAI SMS AgentSolutions by industry Online sellersShopify AutomationMarketplace Automation CompanyPricingAbout EmpAIContact & supportLog in
Get StartedRequest Demo

Privacy Policy

Last updated: November 13, 2026

This Privacy Policy describes how Janyx LLC (“Janyx,” “we,” “us,” or “our”) collects, uses, discloses, and protects information in connection with EMPAI (the “Platform” or “Service”). EMPAI is operated by Janyx LLC and is not a separate legal entity.

EMPAI is an e-commerce automation and integration platform. Merchants may authorize EMPAI to connect with marketplace programs such as TikTok Shop and other marketplaces where available. EMPAI is applying to participate as a TikTok Shop ISV / App Developer and may process data received through merchant-authorized marketplace integrations, including TikTok Shop, solely to provide the functionality the merchant has authorized.

Businesses may also connect a Shopify store as a product source and may connect Facebook Pages and the business portfolio that owns them through EMPAI Meta Automation (Meta App ID 1592493365691426). How EMPAI handles data received from Meta is described in Section 5, and how to request deletion of that data is described in Section 5.9 and on our Data Deletion Instructions page.

This Policy applies to the website at https://empai.ai, related applications, APIs, and integrations that form part of EMPAI.

1. Who we are and how to contact us

Operator: Janyx LLC
Platform: EMPAI — E-commerce Automation & Integration
Privacy / general contact: support@empai.ai

2. Scope of marketplace data processing

When a merchant connects a marketplace account (such as TikTok Shop), EMPAI may process data made available through that marketplace’s official APIs and authorization mechanisms, within the permission scopes granted by the merchant. Marketplace data is processed only to provide authorized EMPAI functionality. EMPAI does not claim access to all information available within a marketplace account—only information reasonably needed for the features the merchant enables and the scopes the merchant grants.

3. Information we may collect or process

Depending on how you interact with EMPAI and which integrations you authorize, we may collect or process the following categories of information:

  • Company, account, and contact information — such as business or company name, contact name, email address, phone number, and related account profile details you provide.
  • Merchant / store information — store names, store identifiers, configuration settings, and related commercial account details needed to operate the Service.
  • Product catalog information — product titles, descriptions, media references, categories, attributes, and related listing metadata.
  • SKUs and variants — stock-keeping units, variant options, barcodes or identifiers, and related product structure data.
  • Inventory — quantity, availability, warehouse or location references where provided, and related stock status fields.
  • Pricing — prices, currency, promotional or list price fields, and related pricing metadata used for synchronization.
  • Marketplace seller / shop identifiers — seller IDs, shop IDs, and similar identifiers issued by a marketplace (including TikTok Shop where applicable).
  • Authorization information — records of which integrations a merchant connected, when authorization was granted or revoked, and related connection status.
  • OAuth / access / refresh tokens (where applicable) — credentials issued by a marketplace through its official authorization process so EMPAI can call APIs on the merchant’s behalf. EMPAI does not ask merchants for marketplace passwords (including TikTok passwords) and does not collect marketplace login passwords for TikTok Shop or similar marketplaces.
  • API permission scopes — the permissions a merchant grants during authorization, which define what EMPAI may access or update.
  • Technical and diagnostic information — IP address, browser or client type, device information, timestamps, request logs, error and diagnostic logs, and similar data used to operate, secure, and troubleshoot the Platform.
  • Support communications — messages, attachments, and related context you send to support@empai.ai or other EMPAI support channels.

4. Seller authorization (including TikTok Shop)

EMPAI accesses a seller’s TikTok Shop account or other marketplace account only after the merchant grants authorization through the marketplace’s official authorization process (for example, OAuth or an equivalent marketplace-approved flow). Merchants do not provide EMPAI with their TikTok or other marketplace passwords.

Merchants may revoke authorization where supported—through EMPAI disconnection controls and/or the marketplace’s seller settings or partner management tools. After revocation or disconnection, EMPAI will stop using that authorization for new marketplace API activity, subject to technical propagation and any short-term processing already in progress.

5. Facebook (Meta) integration

This section applies to data EMPAI receives from Meta Platforms, Inc. (“Meta”) through the Facebook Graph API (“Meta Platform Data”) in EMPAI Meta Automation (Meta App ID 1592493365691426). It supplements the rest of this Policy; where they differ for Meta Platform Data, this section controls.

5.1 How a business connects Meta

A business user connects Meta by clicking Connect Meta in the EMPAI console and signing in through Facebook Login. In Meta’s dialog the user chooses which Facebook Pages and business portfolio to share and which permissions to grant. EMPAI currently requests only these permissions: pages_show_list, business_management, and pages_read_engagement. EMPAI never asks for or stores Facebook passwords, and it accesses only the Pages and business portfolio the user authorizes.

5.2 Meta Platform Data we access and store

When a business connects Meta, EMPAI stores:

  • Connecting user — the app-scoped Facebook user ID of the person who authorized EMPAI. We do not request or store that person’s name, email address, profile photo, friends list, or other personal profile information.
  • Granted permissions — the list of permissions the user granted, and when the connection was authorized.
  • Access tokens — the user access token and the Page access tokens Meta issues, with their expiry time, encrypted at rest (see Section 5.5).
  • Facebook Pages — the ID and name of each Page the user authorizes.
  • Business portfolios — the ID and name of each business portfolio the user authorizes.

When a business opens its Analytics page, EMPAI also reads from Meta the connected Page’s name, category, follower and like counts, and its five most recent Page posts (text, publication date, link, and share count), and displays them to that business. This Page information is read on request to display it and is not stored in EMPAI’s database.

EMPAI does not access Facebook Messenger or Instagram Direct messages, Lead Ads form submissions, comments or reactions on posts, personal Facebook profiles or timelines, or friend or follower lists. EMPAI does not currently read Instagram accounts, product catalogs, ad accounts, or advertising data.

5.3 How we use Meta Platform Data

We use Meta Platform Data only to provide EMPAI to the business that connected it, on that business’s own assets:

  • Linking the right Page — the list of authorized Pages and business portfolios lets the business confirm which Page and portfolio belong to its EMPAI account. Each business sees only the assets it authorized.
  • Reviewing published content — the connected Page’s profile and recent posts are shown read-only on the Analytics page, so the business can review what it has already published when planning new content in EMPAI.

EMPAI does not post, comment, or change anything on Facebook today. Writing to Meta (publishing posts, catalog synchronization, and advertising) is switched off at the platform level and is not offered under the permissions above.

5.4 Planned functionality not yet in use

The following features are planned but are not active today, and EMPAI does not collect data for them: publishing approved posts to a business’s Facebook Page or Instagram professional account; synchronizing product information to a Meta product catalog; creating paused advertising campaigns after a business authorizes spend; reading Instagram or ad performance insights; and retrieving or replying to comments through the API. Marketplace listings are prepared for the business to post manually; no Marketplace API is used. Before any of these features process Meta Platform Data, we will request the required permissions from Meta and update this Policy.

5.5 Storage and security

Meta Platform Data is stored in EMPAI’s managed database (Supabase), and the application that processes it runs on our hosting provider (Railway). Access tokens are encrypted at rest with AES-256-GCM, Graph API calls are made over HTTPS with an app secret proof, and each business can access only its own organization’s data in the EMPAI console.

5.6 Sharing of Meta Platform Data

We do not sell, license, or rent Meta Platform Data, share it with data brokers or advertising networks, use it to build user profiles, or use it for any purpose other than providing EMPAI to the business that connected it. We share it only with:

  • Meta, only as part of the Graph API requests EMPAI makes to read the business’s authorized assets;
  • Our hosting and database providers, which store and process it on our behalf under confidentiality and security obligations (see Section 9); and
  • Legal and safety recipients, when required by law or legal process.

5.7 Retention

We keep access tokens and connected-asset records while the Meta connection is active. Page profile and post information shown on Analytics is not stored. When a business clicks Disconnect Meta in EMPAI, its tokens and connected-asset records are deleted immediately. When a business removes EMPAI from its Facebook settings, or asks us to delete its data, we delete the related Meta Platform Data within 30 days, except data we must keep by law. We keep a record of each deletion request (the confirmation code, app-scoped user ID, and date) to show that the request was completed.

5.8 Disconnecting Meta

You can disconnect Meta at any time from the Connections page in EMPAI with Disconnect Meta, which deletes that business’s Meta tokens and connected assets. You can also remove EMPAI’s access in Facebook: go to Settings & privacy → Settings → Business integrations, select EMPAI, and choose Remove. You can also remove EMPAI from your business portfolio in Meta Business Suite, or email us to disconnect it. After access is removed, EMPAI can no longer call Meta on your behalf.

5.9 Requesting deletion of your data

Anyone whose data EMPAI received from Meta — the business that connected Meta or the person who authorized it — can request deletion:

  • Email support@empai.ai with the subject “Meta data deletion request” and the Facebook Page or business portfolio involved; or
  • Remove EMPAI in your Facebook settings as described above. Meta may forward a deletion request to EMPAI and show you a confirmation code; include that code if you follow up by email.

We complete deletion within 30 days and confirm by email. Full instructions are on our Data Deletion Instructions page.

6. Data minimization

EMPAI seeks to collect and process only information reasonably necessary to provide the functionality authorized by the merchant, maintain the integration, provide support, protect security, and meet legal or marketplace requirements. EMPAI does not represent that it accesses all TikTok Shop information or all information available in any connected marketplace account.

7. How we use information

We may use information to:

  • Authenticate merchants and operate EMPAI accounts;
  • Establish and maintain authorized marketplace connections;
  • Synchronize product and catalog information;
  • Synchronize SKUs and variants;
  • Synchronize inventory and pricing;
  • Provide the Facebook and Instagram features a business has authorized, as described in Section 5;
  • Maintain integrations, configuration, and Service reliability;
  • Provide customer and technical support;
  • Prevent abuse, fraud, and security incidents;
  • Comply with applicable law and marketplace / platform partner requirements (including TikTok Shop requirements where applicable); and
  • Communicate service-related notices about EMPAI.

We do not sell personal information. Marketplace data received through authorized integrations is not used for unrelated advertising profiling outside the Service.

8. How we share information

We may share information with:

  • Marketplace and platform partners (such as TikTok Shop and Meta) as needed to perform authorized synchronization, listing, and publishing operations on the merchant’s behalf, within granted scopes;
  • Service providers / subprocessors that support EMPAI operations (see Section 9);
  • Professional advisors such as legal or accounting advisors under confidentiality obligations, where reasonably necessary; and
  • Legal and safety recipients when required by law, regulation, legal process, marketplace partner requirements, or to protect the rights, security, or safety of Janyx, merchants, or others.

We may also disclose or transfer information in connection with a corporate transaction (such as a merger, financing, or sale of assets), subject to appropriate confidentiality protections where applicable.

9. Service providers / subprocessors

EMPAI may use service providers to perform functions on our behalf, such as cloud hosting, databases and storage, email delivery, monitoring and logging, security tooling, and application infrastructure. Such providers may process information as necessary to provide their services to EMPAI. We require providers to use information only for contracted purposes and to apply appropriate confidentiality and security obligations.

10. Data retention and deletion

We retain information only as reasonably necessary to provide the Service, meet legal obligations, maintain security, resolve disputes, and support legitimate business recordkeeping.

  • When an integration is disconnected, marketplace authorization credentials and tokens are revoked or deleted where technically applicable, so EMPAI can no longer use them for new API access.
  • Meta Platform Data is retained and deleted as described in Section 5.7, including deletion within 30 days of a disconnection or deletion request.
  • Merchant or customer data associated with a terminated EMPAI account will be deleted or anonymized according to EMPAI’s retention practices, except where retention is legally required or reasonably necessary for security, dispute resolution, or required recordkeeping.
  • Information retained for backup, legal, security, or recordkeeping purposes remains subject to protective controls until deletion or anonymization. Deletion from active systems may not be instantaneous where backups, logs, or legal holds apply.

11. Security

EMPAI uses administrative, technical, and organizational safeguards designed to protect information against unauthorized access, loss, misuse, or alteration. No method of transmission or storage is completely secure, and we cannot guarantee absolute security. Merchants should use strong account practices and revoke marketplace authorizations when EMPAI access is no longer needed.

12. Privacy Requests

Where applicable under law or marketplace partner requirements, merchants and individuals may request:

  • Access to personal data;
  • Correction or update of personal data;
  • Deletion of personal data;
  • Information about personal data processed by EMPAI; and
  • Assistance with other applicable privacy requests.

To submit a privacy request, email support@empai.ai with enough detail for us to verify and respond to the request. We may need additional information to confirm identity and authority (for example, that you are authorized to make the request for a merchant account). Response timing depends on the nature of the request and applicable legal or technical constraints.

For data received from Facebook or Instagram, see Section 5.9 and our Data Deletion Instructions; we complete those deletion requests within 30 days.

13. TikTok / seller data requests

EMPAI will reasonably assist merchants and marketplace partners, including TikTok Shop where applicable, with valid requests concerning access, correction, deletion, or provision of data processed through the integration, subject to applicable law, marketplace partner requirements, and technical limitations. This commitment does not create a specific service-level agreement or guaranteed response time unless separately agreed in writing.

14. International processing and data location

Information may be processed in the United States and potentially in other locations where Janyx or its approved service providers operate. Processing location depends on the infrastructure and providers used to operate EMPAI. Where required by applicable law, we use appropriate contractual or other safeguards for cross-border transfers.

15. Children’s privacy

EMPAI is intended for business users. We do not knowingly collect personal information from children under 16.

16. Changes to this policy

We may update this Privacy Policy from time to time. When we make material changes, we will update the “Last updated” date at the top of this page. Continued use of EMPAI after an update constitutes acceptance of the revised policy where permitted by law.

17. Contact

Privacy questions and Privacy Requests:
support@empai.ai
Janyx LLC — Operator of EMPAI

EmpAI

One AI platform for calls, customers, online sales and daily work.

support@empai.ai

Local businesses

  • AI Phone Agent
  • AI Chat Agent
  • AI SMS Agent
  • Solutions by industry

Online sellers

  • Shopify Automation
  • Marketplace Automation
  • Marketplace integration
  • Pricing

Company

  • About EmpAI
  • Contact & support
  • Request Demo
  • Log in

Legal

  • Privacy
  • Terms
  • Data deletion
  • SMS terms
  • Trust & Platform Access
© 2026 Janyx LLC. EmpAI is the commercial platform brand of Janyx LLC.Log in to EmpAI

Marketplace names are trademarks of their owners. EmpAI is not affiliated with or endorsed by them. Example businesses in demos are made up. Photos: Unsplash.

Ask EmpAI
Example answers · for a real reply use the contact form
Hi! I'm EmpAI's assistant. What would you like to know?