Parlami / Faccia

Privacy Policy

Last updated: July 28, 2026

Parlami helps businesses and the teams that support them monitor advertising and site performance across Meta and Google, capture inbound lead records, and review approval-first recommendations. We collect and process the information needed to provide those services.

Data may include account profile information, tenant and user identifiers, connected advertising and analytics asset identifiers, advertising and site-performance metrics, lead contact fields submitted through forms, lead qualification outcomes, audit logs, and email delivery or engagement events. We use this data to operate dashboards, sync metrics, attribute leads to campaigns, calculate quality metrics, generate findings and drafts, and preserve an approval and audit trail.

We do not sell personal information. We do not use lead details or Google user data to develop, improve, or train generalized or public AI/ML models. Production data is tenant-scoped, and privileged operational access is limited as described below.

Customers may request export or deletion of their tenant data. Lead subjects may request deletion by contacting the business that collected the lead or Parlami support. Some audit, billing, security, or legal records may be retained when required for legal, platform, financial, security, or anti-abuse purposes.

For Meta platform data deletion requests, use the Data Deletion Instructions linked below. Faccia exposes a Meta-compatible callback at /api/meta/data-deletionthat validates Meta signed requests and returns a confirmation code plus status URL.

Google user data

When you connect a Google account, Parlami requests the scopes used by the connected features. The standard connection requests:

If Google Business Profile access is enabled for the service, the connection additionally requests https://www.googleapis.com/auth/business.manage. Google provides one Business Profile scope for both read and write operations. Parlami currently uses that scope only to enumerate accessible Business Profile accounts and locations and to read review data for the location you select. It does not use that scope to edit listings, publish posts, or post review replies.

Parlami uses Google user data to provide user-facing features in your tenant: dashboards and reports, measurement and attribution, recommendations about your own advertising and site performance, AI-assisted explanations and drafts, and the approval and audit trail. We do not use Google user data to target or serve ads for Parlami, for unrelated third parties, or across customers. We do not sell it or use it to determine credit worthiness or eligibility for lending.

Service providers and automated processing. By authorizing Parlami's Google connection after being given access to this policy, and by choosing to use Parlami's Google-powered features, you consent to the purpose-limited service-provider transfers described here. Parlami transfers only the Google user data needed by contracted infrastructure, database, monitoring, and AI inference providers to deliver the specific user-facing features you choose. When an AI-assisted feature produces an explanation or draft for you, the minimum tenant-scoped Google-derived information needed for that feature—such as aggregate metrics, campaign or search-term context, and findings—may be sent to an AI inference provider solely to produce the result shown to you. These providers process the information on Parlami's behalf and are not permitted to use it for their own advertising or to train generalized or public models. Parlami does not transfer Google user data to data brokers or information resellers.

Other transfers occur only when necessary for security, to comply with applicable law, or as part of a merger, acquisition, or sale of assets after we obtain your explicit prior consent.

Storage and security. Google API calls use HTTPS/TLS. Google access and refresh tokens are encrypted before they are stored, and persisted Google-derived data is kept in managed storage protected at rest. Server-side components that handle OAuth, scheduled syncs, and approval-gated operations can decrypt tokens when needed to call Google. Application code does not include OAuth tokens or other authentication secrets in logs or customer reports. Stored Google records are tenant-scoped and are not made visible to other customers.

Human access. Parlami personnel may read specific Google user data only when you give affirmative agreement for that specific data so we can provide support or another user-facing feature you requested; when necessary for security; when required by applicable law; or, for internal operations, only after the data has been aggregated so it does not identify an individual.

Revoking access and deleting stored data. You can revoke Parlami's Google authorization from your Google Account at myaccount.google.com/permissions. Revocation prevents future authorized Google API access after Google invalidates the grant, but it does not by itself erase tokens or Google-derived data already stored by Parlami. To request deletion of Parlami's stored Google tokens and previously synced Google data, email privacy@parlami.ai. We verify the requester's authority before an operator deletes stored Google token records and Google-derived data tied to the tenant from active systems. We retain only records needed for legal, billing, security, or anti-abuse obligations and only for those purposes.

Parlami does not currently offer automated self-service deletion or promise a fixed fulfillment time. Encrypted provider-managed backups may retain copies until their normal expiration. Backup copies are not queried for product features and are restored only when needed for disaster recovery.

Parlami's use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Data retention

Data deletion

To request deletion, email privacy@parlami.ai with the business name, the account administrator's email, the affected platform, and enough information to locate the records. For a lead-subject request, include the lead email or phone number and the business that collected the lead.

View data deletion instructions