Privacy policy.

MIQAS is operated by insiyan Establishment For Advertising ("Ensign"), a Saudi-registered entity. This Privacy Policy describes what data we collect, how we use it, and your rights under KSA's Personal Data Protection Law (PDPL).

• Account data: name, email, password hash, role within your workspace.
• Workspace data: the data you upload (ad credentials, aggregator exports, order data from your connected platforms), and the data we derive from it (aggregated metrics, cross-channel attribution).
• Technical data: IP address, browser type, login timestamps. Used for security and abuse detection only.
• Cookies: essential session cookies (always on), and analytics cookies (opt-in via the consent banner).

We process your data to operate the Service: authenticate you, show your dashboards, send transactional emails, and improve the product. We never sell or rent your data, and your business data (orders, revenue, and customer records) is never shared with any third party for its own purposes. Separately, with the consent you give at signup, we may use your account email address to tell you about MIQAS features and offers and to build advertising audiences on platforms such as Meta and Google; those platforms may not use your address for anything else. You can opt out at any time by emailing contact@ensignksa.com.

Your workspace data is visible only to the members you invite. Ensign staff do not browse customer data. A small number of authorised Ensign administrators can open a workspace only to provide support or resolve a technical issue, and every such access is recorded in an audit log. We never access your connected ad accounts beyond what is needed to pull the metrics you asked us to show.

Workspace data is stored in Supabase (Postgres) in the EU-Central (Frankfurt) region. Static assets are served via Vercel's global edge network. Transactional emails go through Resend.

The minimum needed to run the Service:

• Paymob — when you start a subscription, we share your name, email, and workspace ID so they can take payment. Your card details are entered directly into Paymob and never touch our servers.
• Supabase — database and authentication hosting.
• Vercel — application hosting.
• Resend — transactional email delivery.
• AI processing— aggregated workspace metrics and the text you write in the in-product help chat are processed by a licensed AI provider under a zero-data-retention configuration to generate answers, reports, and recommendations. Your end-customers' identifiers are not included in this processing.
• Connected platforms you authorize (Meta, TikTok, Google, etc.) — your credentials are used to pull data on your behalf, only for as long as you keep the connection active.

When a workspace admin connects a Meta account through Facebook Login for Business, MIQAS asks Meta for the permissions below and receives only the data each one covers. As Meta's Platform Terms require, this section explains what that data is, how we process it, the purposes, and how you can have it deleted.

• ads_read— the connected ad account's campaign structure and performance figures (spend, impressions, clicks, reach and conversions, by campaign, ad and day). Used to build your Ad Campaigns reports and to compare ad spend with the sales and leads measured on your own website.
• ads_management— used to send conversions measured on your website or in your pipeline back to your own Meta ad account through the Conversions API, to create and refresh retargeting audiences on that account when you ask for them, and, only after you approve a specific suggestion from AI Autopilot, to change a campaign's daily budget or pause it. Conversions and audiences carry identifiers hashed with SHA-256 before they leave MIQAS; we never send raw names, email addresses or phone numbers to Meta.
• business_management — the identifiers of the business portfolio and ad accounts you hold, read during connection to find the ad account to connect.
• pages_show_list, pages_read_engagement and pages_manage_ads— the list of Facebook Pages you manage, each Page's name, category, link and picture, and the lead forms attached to each Page with their status and lead counts. Read so we know which forms to retrieve leads from and can label them by Page name on your Integrations page. We read no posts, comments or messages, and we never create, edit or pause a Page ad or a form.
• pages_manage_metadata— used for one thing: to subscribe MIQAS to your Page's lead notifications, so that when someone submits one of your Instant Forms Meta tells MIQAS at once and the enquiry appears in your pipeline within seconds instead of at the next hourly check. The notification carries only the Page, form and lead identifiers; the submission itself is then read under leads_retrieval. We change no Page settings and post nothing.
• leads_retrieval — the submissions people make on your Instant Forms (name, phone number, email address and any other question you added to the form, with the campaign and the time of submission). Each becomes an enquiry in your MIQAS pipeline and a contact in your CRM, so you can follow up and see which campaign produced it.

How we process it.This data is stored in your workspace only (Supabase, Frankfurt), is visible only to the members of your workspace, and is used for nothing beyond the purposes above. We do not sell, license or rent it; we do not combine one business's Meta data with another's; we do not use it to build profiles of people for any purpose other than serving you; and we do not use it for surveillance or for decisions about anyone's eligibility for anything. Lead details are held in your encrypted CRM vault, and the phone number and email address are also stored as SHA-256 hashes for matching. We share Meta data only with the service providers listed above, as needed to run the Service, or when the law requires it.

Retention.Meta data stays for as long as your connection and your workspace are active, then follows the period in the "Data retention" section below. Your Meta access token and the connection record are deleted immediately when you disconnect Meta.

How to request deletion. Disconnect Meta from Settings → Integrations to stop all further collection and delete the stored token at once. Delete any individual lead from your Leads page or your CRM. Request deletion of your whole workspace, including everything received from Meta, from Settings → Privacy & your data; it is permanently erased within 30 days. You can also email contact@ensignksa.com with any deletion request, and we respond within 30 days.

Our use of this data is governed by the Meta Platform Terms and Developer Policies in addition to this policy. Data held on Meta's own platforms is governed by Meta's Privacy Policy.

Under PDPL, you have the right to:

• Be informed of how and why your data is processed
• Access the personal data we hold about you
• Obtain a copy of your data in a readable and clear format (PDPL's equivalent of data portability)
• Correct, complete, or update inaccurate data
• Request destruction (subject to retention obligations under KSA law)
• Withdraw consent to non-essential processing at any time
• Lodge a complaint with the Saudi Data & AI Authority (SDAIA)

You can download a full copy of your workspace data, and request permanent deletion, yourself from Settings → Privacy & your data inside the dashboard. For corrections or anything else, email contact@ensignksa.com. We respond within 30 days (extendable by a further 30 days for complex requests, as PDPL allows).

If a personal-data breach occurs that affects your data, we notify the Saudi Data & AI Authority (SDAIA) within 72 hours of becoming aware of it, as required by the PDPL Implementing Regulation, and we notify affected users without undue delay where the breach may cause harm.

We retain your data for as long as your workspace is active, plus 30 days after cancellation to allow account recovery. After that, all personal data is permanently deleted unless KSA law requires longer retention (e.g., tax records for 10 years).

MIQAS is a business tool. We do not knowingly collect data from anyone under 18.

Material changes are communicated via email at least 14 days before taking effect. The "last updated" date at the top reflects the most recent revision.

contact@ensignksa.com