Controller and product ownership
XR Ads is a product owned and operated by XAERE SARL, whose registered office and principal place of business are in Tunisia. XR Ads is an internal tool available only to authorised Xaere workforce identities. It has no public signup, customer console, delegated third-party API or resale of advertising-platform access.
JINFO IT SRL owns advertiser products managed by Xaere under written mandate, including Trajeto, Centrale de Taxis and Taxiima, and is the verified legal business associated with the Xaere Meta business portfolio. JINFO personnel do not access XR Ads. PROXIWEB is a contracted development and supervised technical-support provider; it has no product ownership or campaign authority.
Product data
Xaere Codes stores the organisation, project, code lifecycle, access credentials and operational audit data needed to issue and resolve codes. XR Audience is a separate service: it accepts only verified, minimised interaction events when an integrator has established a lawful consent flow. The technical data-boundary notice lists each current input, exclusion and deletion path.
Optional Meta analytics
The xaere.io website can load a dedicated Meta Pixel/Dataset to measure a page visit and a click that starts a real contact action. The Pixel is disabled when no dataset identifier is configured and Meta receives no browser event before you explicitly choose “Allow analytics”. Xaere does not send form fields, e-mail addresses or account data through these events.
Once allowed, the Meta script can receive ordinary browser and network information and can use Meta cookies or similar storage under Meta's own terms. Rejecting optional analytics leaves the third-party script unloaded.
Your choice is stored only in this browser for xaere.io. Use the “Analytics allowed” or “Analytics rejected” control at the bottom of the page to review or change it. Rejecting or withdrawing consent stops later events and asks the loaded Pixel to revoke consent.
Google Ads data used by XR Ads
XR Ads is an internal Xaere operations tool. For an account Xaere is authorised to manage, restricted Xaere personnel may use the Google Ads API to process customer-account references, account name, currency, time zone, campaigns, ad groups, ads, keywords, targeting and aggregated delivery-performance data needed for Search campaign creation, management, reporting, attribution and monitoring. The reporting OAuth authorization is read-only and does not grant campaign execution permission.
Controlled campaign execution is a separate authorization surface. It requires tenant and account ownership, an enabled feature and scope, a deterministic preview and explicit human approval before a provider mutation. Using separately controlled manager credentials, XR Ads may then create or update campaigns, budgets, ad groups, ads, keywords, targeting and schedules for that authorised account. New campaigns and ad groups are created paused. Unknown provider outcomes are reconciled instead of replaying a mutation. Large BatchJobs and Standard-only capacity remain disabled until Google explicitly approves Standard Access. XR Ads does not provide public or third-party access to the Google Ads API.
XR Ads uses a separate Xaere-controlled service account for Google Data Manager conversion delivery. The reporting OAuth flow does not request the Data Manager scope. Confirmed first-party conversion events may include an advertising click identifier and event time and are sent only to the Google Ads destination authorised for that organisation.
Meta Ads data used by XR Ads
When Xaere explicitly connects an authorised Meta advertising account, XR Ads may process the opaque Xaere account reference, public provider name, account name, currency, time zone, campaign, ad set and ad status, and aggregated delivery and performance metrics required for internal inventory and reporting.
The initial Meta milestone is internal and read-only. It is limited to the ads_read permission after a separate reviewed grant. Business verification, app association or a system-user record alone does not authorize access. XR Ads does not use Facebook Login, public-profile data or arbitrary Meta URLs for this integration. Any future ads_management, publishing, conversion delivery or other write capability requires a separate legal, security and product review, exact account allowlisting, preview and explicit operator approval. It remains disabled unless those controls are independently satisfied.
Purpose, sharing and markets
Advertising-platform data is used only to operate and improve authorised advertising activity for the relevant product. It is not sold, used for lending, shared with data brokers or unrelated advertisers, or used to train general-purpose AI models. Data from one organisation, project, provider or advertising account is not combined with another customer's data. Xaere currently manages products serving France, Italy, Switzerland and Belgium from its principal place of business in Tunisia.
Technical processors may handle encrypted infrastructure data only under contractual confidentiality, security and data-protection obligations. PROXIWEB may provide supervised technical support on that basis but cannot use the data for its own purposes or exercise campaign authority.
Security and access control
Provider credentials and refresh tokens are held server-side, encrypted at rest with authenticated encryption and transmitted over HTTPS. Access is least-privilege, tenant-scoped and audited. Provider resource identifiers do not constitute mutation authority. Unknown outcomes fail closed and require read-only reconciliation.
What the receiver does not do
The Flutter receiver SDK does not create a persistent device identifier and contains no publisher or Audience secret. Audience reporting is optional and starts only after host consent. Advertising and personalization are separate host choices and have no SDK data flow. A random in-memory measurement token rotates every 30 minutes by default, is never stored on disk and disappears when the receiver is disposed.
Retention, revocation and deletion
Google Ads and Meta Ads data and integration state are retained only while the relevant mandate, account connection and operational need remain active, plus any documented legal or security retention period. Xaere can revoke a connection, rotate or revoke credentials and remove account access. Termination of a mandate or tenant closure deletes stored credentials, imported reporting data and related integration state, except records that applicable law or security obligations require Xaere to retain.
Audience retention is configured per integration. An organisation owner can permanently close a tenant from the Console after MFA and explicit confirmation. This removes its Core workspace data and transactionally purges its verified events, replay state, integration secrets and legacy aggregates from the separate Audience database. Meta-specific revocation and deletion instructions are published on the Meta data deletion page.
Requests
Access, correction, deletion, revocation or privacy requests may be sent through the contact page or to integrations@xaere.io. Do not send passwords, access tokens or provider secrets by email. Google API data is handled in accordance with the Google API Services User Data Policy, including the Limited Use requirements where applicable.