• CronusAI engagement layer
  • AtlasLive inventory, storefront, and reservations
  • ForgeVehicle configuration and personal offers
  • PagesDealership website your team edits in minutes
  • LensAgentic dealership advisor
  • AI agents for dealershipsBook, send offers and update the record
  • Dealer communicationsWhatsApp and every channel in one inbox
  • Marketing automationJourneys and AI follow-up for every lead
  • Omnichannel commerceOne deal online and in the showroom
PlatformWhy AI-native

Products

CronusAI engagement layerAtlasLive inventory, storefront, and reservationsForgeVehicle configuration and personal offersPagesDealership website your team edits in minutesLensAgentic dealership advisor

Solutions

AI agents for dealershipsBook, send offers and update the recordDealer communicationsWhatsApp and every channel in one inboxMarketing automationJourneys and AI follow-up for every leadOmnichannel commerceOne deal online and in the showroom
PlatformHow the whole system works togetherWhy AI-nativeWhy the shared AI foundation matters

Last updated 4 November 2026

Privacy Notice

This notice explains how Architera handles personal data across its website and platform, including its products Cronus (Architera's customer conversation product), Atlas (inventory and online stock), Forge (vehicle configurator), Pages (dealer websites), Lens (analytics assistant), Sales (Architera's sales product, a working name) and My Account (buyer accounts). This notice uses those names throughout.

On this page

  1. Who we are
  2. Is Architera a data controller or a data processor?
  3. The personal data we process
  4. How each product uses dealership data
  5. Product and WhatsApp data
  6. Facebook, Messenger, Instagram and Lead Ads data
  7. Where the data comes from
  8. Purposes and legal bases
  9. AI and automated processing
  10. Channels and connected services
  11. Who receives personal data
  12. International processing
  13. Security
  14. How long we keep it
  15. Website analytics and browser storage
  16. Business marketing and email tracking
  17. Your rights and deletion requests
  18. Children, other websites and updates
  19. Contact

Who we are

Architera FZ L.L.C is registered with the Expo City Dubai Authority under business licence and registration number 00374. Our registered address is Unit No: EC-SD-201-24, 14 Mangrove Quarter B, Expo City Dubai, Dubai, United Arab Emirates. Contact accounts@architera.ai about this notice or your personal data.

Is Architera a data controller or a data processor?

We are a data controller for our own business: dealership-user accounts, billing and contract contacts, support for our service, our business prospects and enquiries, and traffic on our own website. We decide the purposes of that processing and handle requests about it directly.

We are a data processor for dealership customer and prospect data handled through the platform, including buyer accounts in My Account. The dealership is the controller and gives us documented instructions under a Data Processing Agreement (DPA). This includes a staff member's identity when it forms part of a dealership's customer record or audit trail. Contact the dealership about that data; if you write to us, we forward the request and tell you. The dealership's own privacy notice explains its purposes, legal bases and retention instructions.

The personal data we process

The information depends on the products and features a dealership uses. We do not collect every category in every interaction.

CategoryPersonal information examples
Dealership-user accountsName, work email, organisation, role, permissions, sign-in and account preferences
Architera business prospects and enquiriesBusiness contact details, role, company, source, messages, sales notes and contact history
Customer identity and preferencesName, phone, email, channel identifiers, language, consent and opt-out records
Conversations and voiceMessages, attachments, images, call details, audio where recorded or supplied, transcripts, summaries, delivery status and timestamps
Vehicle and buying activityVehicle interests, saved cars, configurations, quotations, appointments, requests, reservations, offers, orders and purchase history
Transaction and document recordsBilling details, payment references/status, acceptance records and documents submitted for an enabled booking or offer process, which may include driving-licence or identity documents
Buyer accountsSign-in/session identifiers and links to the buyer's dealership records, saved vehicles/builds, bookings, offers, orders and documents
Website and session activityBrowser identifiers, page paths, product interest, form submissions and bounded activity/attribution information described below
AI and analyticsQuestions, relevant business/customer context, prompts, generated replies, summaries, classifications and suggested actions
Security, support and auditTechnical request information, support messages, errors, security events and records of supported actions

Do not send sensitive personal information unless it is needed for a specific dealership process and the dealership has explained how it will be handled. We do not seek health, biometric-identification, religious or political data for ordinary use. Information volunteered in a conversation may nevertheless contain sensitive details. A voice recording is personal data; recording it does not mean we use it for biometric identification.

How each product uses dealership data

Product or surfaceProcessing on the dealership's behalf
CronusReceives and sends conversations through connected webchat, WhatsApp, email, configured voice and, where the dealership connects them, Facebook Messenger and Instagram Direct; uses contact, vehicle, consent and conversation context for replies, summaries, requests, appointments and enabled journeys
AtlasDisplays stock and records customer-linked interests, saved vehicles, reservations, offers, orders and payment references through enabled commerce flows
ForgeProcesses vehicle selections, configurations, saved builds, enquiries and enabled quote, reservation and order flows
PagesServes dealer content and handles visitors, enabled forms, enquiries and site activity
LensUses records the operator is permitted to access to answer questions, produce analytics and summaries, and support enabled governed actions; retains operator conversation history
SalesUses customer and lead records, including leads from Facebook and Instagram lead forms the dealership connects, buying context, offers, orders and related activity in the released sales functions the dealership has enabled
My AccountLets a buyer access their scoped saved cars/builds, bookings, offers, orders, documents and conversation history across connected dealership services

A product name in this notice describes possible processing, not an entitlement to every feature. Some records are shared between products within the dealership's permitted scope. This is not permission to pool unrelated dealerships' customer data.

Product and WhatsApp data

Architera FZ L.L.C. processes product and WhatsApp data for each dealership that uses our services. The dealership decides which WhatsApp Business account and phone number to connect and is the controller of its customers' data; Architera FZ L.L.C. processes that data on the dealership's behalf under a data processing agreement. For dealership users' own account data, Architera is the controller.

The data may include dealership workspace and user account details; selected WhatsApp Business account, business asset, and phone-number identifiers; customer phone numbers; message content and attachments sent or received on the dealership's behalf; message timestamps, delivery status, consent and opt-out records; approved template metadata; and security, support, and audit logs.

We use this data to connect and administer the dealership's selected account and number, receive and send customer messages on the dealership's behalf, operate the workflows and safeguards the dealership enables, provide support, protect the service, and meet legal obligations. We do not use WhatsApp message content to train general-purpose AI models.

Product and WhatsApp data is shared with Meta as the operator of the WhatsApp Business Platform and with service providers that support our hosting, database, security, communications, support, and contracted AI processing. Those service providers may process the data only to provide the relevant service to Architera and under appropriate contractual obligations.

We keep account and connection data while the dealership uses the service. Message content, customer records, and related activity are kept according to the dealership's agreement and configured product settings, then deleted or anonymized when they are no longer needed. Limited security, audit, billing, backup, dispute, and legal records may be kept for the period required to protect the service, establish legal rights, or comply with law.

A person or dealership can request deletion by following our Data Deletion Instructions.

Facebook, Messenger, Instagram and Lead Ads data

When a dealership connects its Facebook Page, its Instagram professional account or its Facebook and Instagram lead forms, Architera FZ L.L.C. processes the related data on the dealership's behalf under a data processing agreement. The dealership chooses which Page, Instagram account and forms to connect and is the controller of its customers' data.

The data may include the connected business portfolio, Page, Instagram account, lead form, ad and campaign identifiers and names; Page access tokens used to connect the service; the identifiers Meta assigns to a person who messages the dealership's Page or Instagram account; message text and records that an attachment was received; message timestamps and delivery records; the answers a person submits in the dealership's lead form, including consent checkbox answers; consent and opt-out records; and security, support and audit logs.

We use this data to connect and administer the dealership's selected Page, Instagram account and forms, receive messages people send to the dealership and send the dealership's replies, create a lead for the dealership from each lead form submission, operate the workflows and safeguards the dealership enables, including disclosed AI replies and staff takeover, provide support, protect the service and meet legal obligations. A message or a lead form submission does not by itself give marketing permission. We do not sell this data, do not use it to build advertising profiles, and do not use message content or form answers to train general-purpose AI models.

This data is shared with Meta as the operator of Facebook, Messenger and Instagram and with the service providers that support our hosting, database, security, communications, support and contracted AI processing, under the same obligations as product data.

Page access tokens are stored encrypted and cleared when the connection is disconnected or revoked. Connection identifiers and status records can remain. Disconnecting stops new messages and leads but does not erase existing records; message content, customer records and leads are kept and deleted under the same rules as other product data. A person can request deletion through our Data Deletion Instructions by naming the dealership's Page or Instagram account, or the form they completed, without needing a phone number or email address.

Where the data comes from

We receive data from you, dealership staff, the dealership's connected systems and communications providers. Architera's own business contacts can come from public or licensed business sources. The service also generates delivery, session, AI, analytics, support and audit records. Dealer-provided records may include imported customer or vehicle information.

Account and contact details are needed to provide the relevant account, reply or transaction. If you do not provide required information, we or the dealership may be unable to provide that function. Optional marketing permission is separate from a request to answer an enquiry.

Purposes and legal bases

For our own controller activities, we use personal data to administer and secure accounts, answer enquiries, provide support, manage our business relationships, understand use of our website, bill and keep legally required records. We do not sell personal data.

Where UAE federal data protection law applies, we rely on consent unless a specific legal exception applies, such as processing necessary for a contract with the individual or steps they request before it, legal obligations, or legal claims. A contract with a dealership does not automatically make every employee's data necessary for a contract with that employee. We identify the applicable basis for the activity; a general business interest is not, by itself, a UAE consent exception.

Where another applicable law permits legitimate interests, these may include proportionate business relationship management and service security, subject to the individual's interests and rights. Consent can be withdrawn by contacting us; withdrawal does not invalidate earlier lawful processing. Marketing objections are respected separately from records we must retain by law.

For dealership-controlled data, the dealership identifies the lawful basis and gives the required notices and instructions. Platform and channel controls assist that work; they do not replace the dealership's legal assessment.

AI and automated processing

AI can use conversation content and relevant customer, vehicle and business records to draft or send replies, summarise interactions, answer operator questions and suggest actions. Operators may also request analysis of stored conversations. Generated output can be inaccurate. Analytics and classifications can help staff prioritise work; they are not a guarantee about a person or a sale.

Dealerships can turn inbound AI on or off by channel and set the approval modes the product supports. Webchat may answer automatically within its safety controls; it does not offer review of every reply before sending. Email, WhatsApp, Messenger and Instagram use channel-specific disclosure, and webchat displays an AI notice. Voice disclosure and recording notices must be checked for the configured call flow. A disclosure is not repeated in every message.

We do not train general-purpose AI models on dealership customer data. Customer-data model processing must use the provider terms and settings agreed under the DPA. The DPA identifies providers and permitted processing; a model call still sends the necessary context to that provider. The platform is not intended to make credit, legal or similarly significant decisions about a person solely by automated means. Contact the dealership to challenge an outcome or ask for human consideration, and contact us about processing for which we are controller.

Channels and connected services

The covered communication flows are webchat, WhatsApp, email, configured voice and, where a dealership connects them and they are available to it, Facebook Messenger, Instagram Direct and Facebook and Instagram lead forms. Each dealership's available channels depend on its subscription, setup and provider approval. Further channels require a separately agreed and available service.

Communications platforms carry messages or calls under their own applicable terms. A dealership may also connect payment, inventory or other systems. The dealership is the merchant for vehicle transactions. A provider may have its own controller responsibilities; those are described in its notice and the dealership's notice.

Who receives personal data

Recipients include hosting, database, storage and authentication providers; AI model and voice-processing providers; messaging, email and telephony providers; and providers supporting security or enabled delivery functions. They receive the information needed for their function. Dealership customers receive our current list of subprocessors with their data processing agreement, and it is available to them on request.

Authorised dealership staff, authorised parent organisations and Architera personnel may access data within their permitted roles for service, support and operations. We may disclose information to professional advisers, authorities where required by law, or parties involved in a business transfer subject to appropriate confidentiality and legal protections. A dealer's chosen external service may receive data on the dealer's instructions.

International processing

Our primary customer database and object storage are hosted in Frankfurt, Germany. Our team operates from the United Arab Emirates. Application delivery, communications, AI and other providers may process data in other countries; primary database location is not a promise that all processing stays in the European Union.

The DPA schedule identifies the relevant providers, locations and transfer arrangements for dealership data. Transfers must use a mechanism permitted by the applicable law, with the necessary contractual and other safeguards. Where the GDPR or the UK GDPR applies to a transfer of dealership data, the DPA incorporates the European Commission's standard contractual clauses for controller-to-processor transfers, and the United Kingdom addendum to them, so that safeguard applies without a separate signature. We do not treat a provider's European location or a generic contract reference as proof of an approved transfer. Contact us for information about the safeguards applicable to your data.

Security

We use access controls, database isolation, encrypted transport and infrastructure encryption at rest, together with security monitoring and records of supported customer-data actions. Access can include authorised parent organisations and authorised platform administration. We do not claim that every read is logged, that every record is immutable, or that a security certification has been awarded. No system is completely secure.

We investigate personal data incidents, inform the relevant dealership for processor data, and notify individuals and authorities when the applicable law requires. Further factual information is available in our Security overview; contractual measures are in the DPA.

How long we keep it

DataRetention approach
Architera business prospectsA 24-month inactivity threshold identifies records for retention review and anonymisation; review and lawful exceptions can affect completion. This is not an automatic deletion guarantee on the anniversary
Raw Architera website trafficA scheduled process removes records older than 90 days; a journey attached to an enquiry is part of that enquiry's record
Dealership-user accountsFor the service relationship and thereafter only as needed for closure, security, legal obligations or claims
Dealership conversations and customer recordsUnder the dealership's DPA schedule. Available retention jobs have defined scopes and require activation; there is no universal automatic deletion period across all products
Pages form submissionsA scheduled process removes the submission rows after 90 days; a resulting customer/enquiry record is governed separately
Offers, orders, documents and buyer accountsAccording to the dealership's instructions and lawful transaction, support and recordkeeping needs; stopping a paid subscription does not itself erase these records
Security, audit, billing and backupsFor the applicable operational, legal or backup period, restricted to the justified purpose; the dealership's schedule records the relevant periods and exceptions

The dealership's DPA governs return and deletion on exit, including any agreed closeout. A deletion confirmation identifies what was removed and any lawful or backup exceptions. Unsubscribing from messages is not the same as deleting past records.

Website analytics and browser storage

On Architera's website, necessary storage remembers your privacy choice. Optional Analytics and Marketing and attribution are off until you choose them. You can accept all, reject all or select categories, and change your choice through Cookie settings in the footer. Analytics permits aggregate website measurements. Marketing and attribution permits linking a visit from an outreach email to that send and our contact record, including clean page paths, active time, deliberate video interactions and demo/contact clicks. Revoking it stops future identified activity. The server-side email click record is separate and remains recorded. The traffic ledger does not store message/form contents, raw IP addresses, fingerprints or full referring URLs. Hosting systems can separately receive technical request data such as IP addresses.

We use Vercel Web Analytics for aggregate website activity and bounded events such as demo-request interaction and contact clicks, only with Analytics consent. Event properties do not contain the text entered into the form. Google Analytics and Google Tag Manager are not installed on Architera's marketing website. Fonts are served from our own site. Films and images are delivered as website content from hosting and image services, without an embedded YouTube or Vimeo player. Loading that content sends technical request data to its host; it is not an analytics consent grant.

Your privacy choice records the time, policy version, category choices and whether Global Privacy Control was detected. We ask again after twelve months or a policy-version change. Global Privacy Control keeps Marketing and attribution off, including when Accept all is pressed. The current choice and a bounded history of up to 100 choices are stored in your browser, without a contact identifier. For identified outreach, the separate server record retains the grant or withdrawal time and session against the original send. Clearing browser storage removes the device-local proof, not those existing server records.

Cookie, storage key or serviceProvider and purposeCategoryDuration and party
architera_cookie_consent_v1Architera, current versioned privacy choiceStrictly necessaryUp to twelve months; first-party local storage
architera_cookie_consent_log_v1Architera, device-local choice historyStrictly necessaryUp to 100 choices from the current policy within twelve months, pruned on the next choice; first party
architera_cookie_draft_v1Architera, unsaved category editsStrictly necessaryBrowsing tab, cleared on save; first-party session storage
architera_marketing_session_v1, architera_marketing_session_v1_outreachArchitera, aggregate page-view session; outreach variant carries no persistent visitor identifierAnalyticsBrowsing tab or withdrawal; first-party session storage
architera_marketing_visitor_v1Architera, identifier for a disclosed form or tracked-link associationAnalytics plus Marketing and attributionUntil withdrawal or consent expires, checked on the next visit; first-party local storage
architera_interest_journey_v1Architera, bounded pages and interactions attached to a submitted demo requestAnalytics plus Marketing and attributionBrowsing tab or withdrawal; first-party session storage
architera_outreach_v1, architera_outreach_v1_eventsArchitera, consented outreach session and bounded delivery queue; an undelivered withdrawal receipt can remain until deliveryMarketing and attribution; withdrawal proof is necessaryBrowsing tab; identified session removed on withdrawal, queue removed on delivery; first party
Configured Google tags and LinkedIn Insight TagGoogle Analytics measures site use; Google Tag Manager manages approved tags; LinkedIn measures campaigns and post boostsGoogle Analytics: Analytics; LinkedIn: Marketing and attribution; Tag Manager: bothProvider-specific cookies, including Google _ga (up to two years) and LinkedIn li_fat_id (up to 30 days); disabled until an ID is configured
Vercel Web Analytics script and event endpointsVercel, aggregate activity; no analytics cookie or browser storage keyAnalyticsNo persistent browser identifier; first-party endpoint, hosting provider processes requests
architera:draft:v1:*, architera:draft:tab-historyArchitera, demo-form text and tab ownership, only after the form is usedStrictly necessary for the requested formBrowsing tab, draft expires after seven days or on submission; first party
Roboto and Geist Mono font filesArchitera, self-hosted typographyWebsite contentBrowser HTTP cache; first party
Film files and catalogue imagesVercel Blob, Supabase Storage or the vehicle image provider, content delivery without tracking pixelsWebsite contentBrowser HTTP cache; third-party content host

These keys describe Architera's own marketing site. Buyer products have separate functional storage and dealer-controlled integrations. The following inventory identifies the shared product storage; a dealer's notice must also identify its actual configured services.

Buyer cookie, storage or integrationPurpose and categoryDuration and party
architera_visitor_token, architera_visitor_token_expires_at, architera_returning_visitor_consentArchitera, optional cross-visit chat recognition with the chat's memory opt-inToken: 365-day sliding lifetime; consent until withdrawal; first party on the serving origin, embedded browsers may restrict it
architera_tab_session_id, cw:voice-tab, cw:final-launcher:folded, cw:bubble:positionArchitera, current chat, requested voice/form work and layout choicesBrowsing tab; first party
cw:launcher:*:dismissed, cw:nudge:kind-memory, cw:nudge:session-countArchitera, remember dismissal and prevent repeated promptsDismissal until cleared, nudge silence seven days, counter per tab; first party
architera_recently_viewed_vehicles, architera_forge_last_buildArchitera, browser journey context for vehicle and configurator continuityThirty days, checked on use; first party
cw:durable:*, architera:draft:v1:*Architera, keep requested chat/form work and unsent inputDurable chat state until cleared; drafts up to seven days, session drafts end with tab; first party
sb-*-auth-token*Supabase, necessary signed-in product sessionSession expiry and renewal follow the signed-in product; first party
Cookiebot or UsercentricsDealer-selected consent manager, necessary choice storageConfigured by the dealer and provider; may use third-party services
Configured GA4, chat or custom tagsDealer-selected analytics, chat and marketing services on dealer Pages; held behind the configured consent manager unless explicitly declared strictly necessary by the dealerProvider-specific cookies, keys and retention must appear in the dealer's notice; not installed by Architera's marketing cookie choice

With both optional categories enabled, a submitted demo request can include a bounded journey from the current tab: paths, active time, view counts, interaction labels/counts and campaign tags. A tracked link or submitted form can associate the first-party identifier with our business contact record only with Marketing and attribution consent. Our first-party journey records are limited to this website. When enabled with consent, Google and LinkedIn may connect activity with data from other sites under their privacy policies. Clearing site storage resets that browser identifier; it does not delete existing server records.

Where a dealer chat offers conversation memory, it asks for your opt-in before using a browser identifier to recognise a later visit. You can withdraw that choice in the chat. Withdrawal stops future recognition; it does not erase past conversations. You can request their deletion separately.

Google Analytics, Google Tag Manager and LinkedIn Insight Tag are prepared but stay off until their deployment IDs are configured. Google Analytics requires Analytics consent; LinkedIn requires Marketing and attribution consent. Google Tag Manager requires both. Google Consent Mode v2 starts denied, with no vendor request before the required consent. Withdrawal reloads the page to stop loaded vendor code. Configured services may set their own analytics or advertising cookies. Signed-in products use necessary session cookies. Dealer Pages and other buyer surfaces use the storage and connected services relevant to the dealer's enabled features; the dealer must describe these in its notice.

Business marketing and email tracking

Email-open tracking is disabled for recipients in EU and EEA markets and where the market is unknown. Other known markets retain open tracking unless disabled for the send. The market comes from our stored company record, not your email address or IP address. Our emails may use first-party tracked links independently of open tracking. A cookie choice on our website does not grant permission for email pixels or for contacting you. You can object to business marketing by replying, using an available unsubscribe link, or emailing accounts@architera.ai. We keep a limited suppression record to respect the request. Open/click signals are imperfect and do not prove a person read a message.

Your rights and deletion requests

Depending on the applicable law and circumstances, you may request information or a copy, correction, erasure, restriction, portability, withdrawal of consent, or objection to direct marketing or certain automated processing. We protect other people's data when responding. Rights can have legal exceptions; we explain an applicable refusal or limitation.

Write to accounts@architera.ai. We acknowledge requests within 5 business days and complete verified requests within 30 calendar days, subject to any shorter legal requirement. We explain any lawful extension and its reason. For dealership-controlled data, we forward a request within 5 business days and help the dealership respond; the dealership determines the outcome. Identity or authority verification must be proportionate.

See our Data Deletion Instructions for the practical request route. You may complain to the competent data protection authority, including the UAE Data Office where UAE federal law applies; contact us if you need help identifying the appropriate route. You do not have to complain to us first.

Children, other websites and updates

The platform is intended for dealership business and adult vehicle customers. It is not directed to children. If a child's data has been provided, contact the dealership or us so it can be handled appropriately. Other websites have their own notices. We update this notice when processing changes and take reasonable steps to communicate material changes. The date identifies this version.

Contact

Architera FZ L.L.C, Unit No: EC-SD-201-24, 14 Mangrove Quarter B, Expo City Dubai, Dubai, United Arab Emirates. accounts@architera.ai. Dealership customers should contact their dealership first for data it controls.

The agentic operating system for automotive retail.

Security and trust
  • GDPRGDPR
  • Guardrails
  • Human handover
  • EU AI Act

Platform

How Architera worksIntegrationsWhy AI-nativeSecurity overviewFAQAbout ArchiteraBook a demo

Products

CronusAtlasForgePagesLens

Solutions

AI agents for dealershipsDealer communicationsMarketing automationOmnichannel commerce
© 2026 Architera
Privacy NoticeTerms of UseData Deletion
ARCHITERA FZ L.L.C, Dubai, United Arab Emirates