What changes when you connect Coexistence?

Short answer: No. The provider shown on the connection determines the privacy path.

• Meta-direct Frepi: the business authorizes the Frepi Platform app and Meta sends approved events to Frepi. This is the path covered by the rest of this FAQ.
• Via Respond.io: Respond.io remains the Meta provider of record. Frepi receives data through the Respond.io connection and credentials configured by the business. Meta's optional 180-day history and complete contact synchronization do not flow directly to Frepi on that path.

Customers should check the provider displayed for the number before relying on a privacy answer, because the processors, credentials and deletion boundaries differ.

Short answer: The business's existing WhatsApp Business App number is also onboarded to Meta's Cloud API for use by Frepi.

The number and the WhatsApp Business App remain usable. Coexistence creates a second, API-based operating path so messages can be mirrored between the app and an authorized business platform.

Short answer: A representative of the business authorizes it through Meta's own Embedded Signup flow and confirms the connection in the WhatsApp Business App.

The person signs in with their Meta business credentials, chooses the relevant business assets and confirms the number. Frepi does not receive or store that person's Facebook password.

Short answer: WhatsApp business messaging and WhatsApp business management.

• Messaging permits the authorized app to send and receive messages for the selected business number.
• Management permits operations on the selected WhatsApp Business Account, such as reading phone-number settings and managing message templates.

These permissions concern selected WhatsApp business assets. They do not provide blanket access to a person's Facebook account or unrelated business portfolios.

Short answer: Frepi exchanges Meta's temporary code for a customer-scoped business access token.

The exchange happens server-to-server. Frepi does not return token or app-secret values through connection APIs. Manually supplied tokens, refreshed add-number tokens and stored client app secrets use the current application-encryption helper. The initial Embedded Signup token and customer-supplied AI API keys do not yet have complete application-level encryption coverage, so Frepi does not make a blanket claim that every credential is application-encrypted at rest.

A token is powerful because it represents delegated access. Encryption, scope validation, daily validity checks and revocation are therefore more meaningful controls than hiding the existence of the token. Refresh of expiring Embedded Signup tokens remains an operational requirement.

Short answer: It shows that Meta marked Frepi's business and Technology Provider access verification complete and approved Advanced Access to the two WhatsApp permissions.

As of 1 September 2026, Frepi's Meta dashboard records business verification, Technology Provider access verification, and advanced access to whatsapp_business_messaging and whatsapp_business_management.

Anyone can independently confirm Frepi's public Meta app record: App ID 1233214825458555 returns the name Frepi Platform from Meta's Graph API without a token. Meta does not publish a Technology Provider license number or a public provider directory.

This is Meta's Technology Provider access verification. It is not a privacy certification, a penetration test or a blanket endorsement of this FAQ by Meta.

Short answer: Frepi currently processes supported standard message events, identifiers, status and business-number metadata delivered by Meta.

The current processed path can include:

• supported new incoming messages and Cloud API messages sent by Frepi;
• delivery, read, failure, edit and deletion events when Meta provides them;
• WhatsApp contact identifiers and profile names attached to those messages; and
• message content and identifiers in the supported standard webhook format.

Meta can additionally deliver history, full contact synchronization and app-sent message echoes. Frepi retains incoming signed webhook payloads but does not currently import those three additional event types into the displayed conversation.

Short answer: Not currently. Meta supports an optional history flow, but Frepi does not yet initiate or import it.

Meta supports a one-time synchronization covering messages sent or received during the 180 days before Cloud API onboarding. The request must be initiated within 24 hours after onboarding. If the business declines history sharing, Meta returns a “history not shared” result instead of the past conversations.

Historical media is more limited: Meta sends media asset identifiers separately only for media messages from the 14 days before onboarding.

Short answer: Meta does not deliver the past conversations through its history flow.

Frepi does not currently request that flow in either case. If history import is enabled in a future release, declining the option will prevent that backlog from being shared while supported new message events can still operate after connection.

Short answer: Frepi does not currently initiate Meta's complete contact-list synchronization.

Frepi receives contact identifiers and profile names attached to supported new message events. Meta's Coexistence API separately supports synchronization of all contacts that have a WhatsApp number, followed by contact-change events, but that broader flow is not currently imported by Frepi.

Short answer: Meta can deliver those copies, but Frepi does not currently import them into the displayed conversation.

Meta sends supported app-sent copies through the smb_message_echoes webhook. Frepi's signed webhook buffer can receive the raw event, but the current conversation importer does not convert that event into a displayed message. Until that support ships, a Frepi conversation may omit messages employees sent from the app.

Short answer: Group chats are not synchronized, and several privacy-sensitive app features are not supported in Coexistence.

• WhatsApp group chats are not sent through the Coexistence API path.
• Disappearing messages are turned off for individual chats after onboarding.
• View-once messages and live-location messages are disabled for individual chats.
• App broadcast lists cannot be newly created; existing lists become read-only.

These are Meta product behaviors, not Frepi settings. They should be reviewed with the business before connection because they change how employees use the app.

Short answer: No.

Frepi receives data through Meta's documented Embedded Signup, Cloud API and signed webhooks. It does not currently call Meta's optional history or complete contact-synchronization endpoints, remotely read the device, or automate the consumer interface.

Short answer: No—the accurate description is encrypted transport through Meta's Cloud API, not device-to-Frepi end-to-end encryption.

Meta documents that the message travels encrypted between the WhatsApp user and Cloud API. Cloud API decrypts it so it can forward the message to the business. Business-platform traffic then uses HTTPS/TLS, and Meta manages the Cloud API encryption keys on the business's behalf.

Frepi should not claim that only the sender and the employee's phone can read a Coexistence message. The connected business platform must receive usable message content in order to provide inbox and analytics services.

Short answer: Frepi supports dedicated workspace data planes, but not every record or deployment is physically isolated in a separate database.

When a dedicated tenant data plane is provisioned, canonical conversation and analytics tables are specific to that workspace. Frepi also supports partnership-level data sources and keeps platform records such as connection, credential and workspace configuration metadata in shared infrastructure. Those shared records depend on workspace identifiers, tenant fences, row-level controls and application authorization. Raw ingress and operational records may also live outside the dedicated tenant database.

Dedicated tables reduce the cross-customer blast radius when used, but they do not replace authentication, authorization, backups or operational controls. Ask Frepi to document the actual topology for the contracted workspace.

Short answer: For supported surfaces, an authorized administrator can supply provider credentials; this is not yet a global processor-selection or AI-disable control.

The configuration resolves in this order:

1. workspace-specific provider, model and API-key override;
2. partnership-level configuration; then
3. Frepi's platform default when no customer override is set.

Supported configuration can route some AI requests through the customer's own OpenAI, Anthropic or xAI account. If a selected provider lacks a usable key, the resolver can select another configured provider. Analysis Studio classification can use a separate platform provider and model. Removing an override moves the workspace back to inherited Frepi configuration. API keys are masked in responses, but masking is not encryption and complete application-level encryption of these keys remains open work.

Bring-your-own-key affects routing and billing on supported paths; it is not a tenant boundary or proof that every AI feature uses the same account. Frepi still orchestrates requests, and enabled background features may process content without a contemporaneous user prompt. Customers needing a single provider or no AI processing should require a feature-by-feature configuration and contract term.

Short answer: Meta may retain encrypted Cloud API message data for up to 30 days to provide base functionality such as retransmission.

That Meta retention window is separate from the business copy stored in Frepi. The two systems have different purposes, policies and deletion controls.

Short answer: Frepi stores the supported business copy and raw signed events on Google Cloud in São Paulo, Brazil (GCP Brazil).

The current Coexistence path can include:

• supported new incoming content and messages sent through Frepi;
• contact identifiers and profile names attached to those messages;
• message status, timestamps, templates and campaign records;
• raw signed webhook payloads, including media identifiers when Meta supplies them; and
• derived analytics or AI classifications when those features are used.

Frepi does not currently download or display Coexistence media from those raw identifiers, and it does not currently import Meta's optional history, full contact-list or app-echo flows.

Short answer: Conversation and campaign records are generally retained for the life of the workspace, subject to the controlling policy and contract.

Frepi's current Privacy Policy states response and deletion targets for validated requests. This FAQ does not represent that the workflow has been independently audited or fully automated across every tenant database, raw event, backup, log and subprocessor. Customers requiring a fixed deletion SLA should record its scope, exceptions and evidence in the applicable data-processing agreement.

Short answer: Frepi combines transport security, signed-event validation, workspace-scoped controls, role-based access and path-specific secret handling.

• Meta API and webhook traffic uses HTTPS/TLS.
• Frepi validates Meta's X-Hub-Signature-256 before processing webhook payloads.
• Secret values are not returned by connection APIs; stored client app secrets and several token paths are application-encrypted, while initial Embedded Signup token encryption remains incomplete.
• Customer data uses dedicated workspace tables where provisioned and tenant controls in shared infrastructure.
• Application roles limit which workspace users can view or administer data.
• Specified administrative actions performed through Frepi are logged; this document does not claim complete logging of every direct infrastructure access.

No technical control makes risk zero. Security reduces likelihood and impact; governance and incident response remain necessary.

Short answer: Authorized workspace users, authorized administrators, limited Frepi operations personnel, and necessary subprocessors.

A reseller or white-label partner can administer its own customer workspaces but not another partner's. The business controls which staff it invites. Infrastructure providers process data to host the service, and authorities may receive data where law requires it.

Short answer: It can be, when the workspace uses an AI feature that needs that content.

Features such as classification, Copilot or suggested audiences may send necessary prompts and conversation text to model providers outside the workspace. Interactive and configured background features must both be considered; supplying or removing one API key is not a global off switch.

Frepi does not use one customer's WhatsApp conversations to train a model that serves other customers. Model providers may apply their own security and abuse-monitoring terms, which should be assessed separately.

Short answer: No.

Frepi's privacy policy states that it does not sell personal data, use one client's conversations to contact another client's customers, or build a cross-customer advertising graph from WhatsApp Platform Data. Meta states that Cloud API does not automatically use messages to inform the ads a person sees.

Short answer: Frepi stores the workspace copy on Google Cloud in São Paulo, Brazil (GCP Brazil). That is not a blanket Brazil-only guarantee for every system on the Coexistence path.

Frepi's production application and databases run in Google Cloud's Brazil region (São Paulo). Coexistence still involves Meta's Cloud API, and optional AI features can involve model providers outside that region. Businesses with residency requirements should request the current subprocessor and transfer details and record the required safeguards contractually.

Short answer: Yes.

Meta instructs the business to open WhatsApp Business App and go to Settings → Account → Business Platform → Disconnect Account. This offboards the Cloud API connection; it is not the same as deleting the WhatsApp account or surrendering the number.

Short answer: Provider-side disconnection should stop authorized sends and future event delivery, but local cleanup differs by path today.

Meta can send a partner-removed event when the Coexistence connection is disconnected. Frepi excludes revoked connections from normal routing. The standard Connections path clears the stored token; a separate internal administrative path can currently mark the connection revoked without deleting it, and provider-originated disconnection is not yet a single verified credential-destruction workflow.

Disconnection stops the future connection. It does not by itself prove that every historical copy in every system has already been erased.

Short answer: Existing business copies may remain under each system's retention policy until deletion or de-identification occurs.

Messages still in WhatsApp remain under WhatsApp's controls. Copies in a third-party inbox remain under that provider's controls. Frepi may delete or de-identify WhatsApp Platform Data after disconnection, and the customer can make an explicit deletion request for the Frepi copy.

Short answer: Email henry@frepi.ai from the address associated with the Frepi account.

Use the subject Data deletion request and identify:

• the workspace name or URL; and
• whether the request covers one user, one contact's conversations, or the entire workspace.

The current Privacy Policy states response and completion targets. Customers should treat those policy terms as controlling and request a scoped contractual commitment where needed. Frepi is still consolidating end-to-end operational evidence across tenant data, raw events, backups, logs and subprocessors; this FAQ does not characterize that process as independently audited.

Short answer: The business is generally the controller for customer conversations and Frepi generally acts as its processor for the contracted service.

The business decides why to message customers, which Frepi features to use, which employees receive access, and how long business records are needed. Frepi processes data to provide the contracted workspace. Applicable law and the parties' agreement ultimately determine these roles. Frepi may act as an independent controller for limited purposes it determines itself, such as its own account administration, billing, fraud prevention, security records and legal compliance.

Short answer: Its privacy notice should accurately describe business-platform processing, purposes, providers, retention, rights and marketing choices.

The business remains responsible for:

• having a lawful basis for messaging and storing conversations;
• providing required privacy notices;
• honoring opt-outs and data-subject requests;
• limiting staff access; and
• assessing optional AI processing before enabling it.

Connecting a certified or verified provider does not transfer these controller obligations to Meta or Frepi.