Privacy Policy

Government and public authority data requests — October 20, 2026

MIAOZHIAI PTE. LTD. applies this process to requests from government bodies, law enforcement, courts, regulators and other public authorities for personal data we hold, including WhatsApp (Meta) and other connected-platform data. The policy owner is Poter Chen, Data Security Officer. The company's underlying policy took effect on September 1, 2026; this public description was updated on October 20, 2026.

Receiving requests: personnel who receive a request must forward it to the policy owner within one business day, escalating urgent matters immediately, and must not independently disclose data. Requests and the requesting authority's identity are documented and verified before disclosure.

Legal review: the policy owner, with external legal advice where needed, checks the requesting authority's identity, the legal basis and process, applicable jurisdiction, and the specific accounts, data fields, purpose and time period requested. We consider the laws applicable to our company and the data, including Singapore law.

Challenging requests: we reject or seek written clarification, correction or a narrower scope for requests considered unlawful, overbroad, vague or outside the requesting authority's jurisdiction. Where appropriate, we seek legal advice and challenge the request through available legal channels. We do not disclose data while a challenge is pending unless legally compelled.

Minimum disclosure: for a valid request, we approve and disclose only the specific data necessary to meet it, using anonymized, aggregated or pseudonymized data where that satisfies the request. We verify the receiving party, use a secure transfer channel and record the approved scope and the actual disclosure.

Notification: unless prohibited by law or a binding order, we notify affected users before disclosure so they can seek legal remedies. Where our platform agreements require notification to Meta or another platform partner, we comply with those obligations and applicable timing requirements where legally permitted. We record notification decisions, timing and any restrictions.

Record-keeping and access: the request register is stored in our database in Singapore. Access is restricted to authorized data security personnel. Each record includes the request and legal basis, our review and reasoning, the people involved in reviewing, approving and carrying out the response, any clarification or challenge, our response, the data and recipients involved in any disclosure, and notification decisions.

Retention: the policy owner records the legal or business reason for retaining request records, their retention end date or review date, and any applicable legal hold. We review retention at least annually and when a matter closes or a hold ends, and securely delete or irreversibly anonymize personal data when retention is no longer necessary, subject to applicable legal requirements.

Personnel and review: relevant personnel have been informed of this process. We brief staff who handle personal data at onboarding and at least annually, and review the policy annually and after a government request or relevant change in law.

Contact the policy owner through support@admapix.com.

Meta integrations: Facebook, Instagram and advertising — October 13, 2026

When you connect a supported Meta account, we receive the identifiers, names or usernames, permissions and OAuth tokens needed to connect the Facebook Pages, Instagram professional accounts or advertising accounts you authorize. Authorized resource details can include Page roles, account currency and time zone. We do not receive your Facebook or Instagram password. Connection tokens and selected Page credentials are encrypted on our server and are not returned to customer API callers.

We use this data for the account and resource selection, publishing, messaging and reporting features you request. For supported publishing, we send the text, caption, link, media URL and settings you approve to Meta and retrieve the resulting identifiers and status. Supported inbox features retrieve recent conversation and participant identifiers, names, message text and timestamps, and send replies you request within Meta's permitted messaging window. Advertising reads retrieve your authorized account and campaign details and performance reports. Comment management, additional analytics, advertising changes and other capabilities require their own approved permissions and enabled implementation; connecting an account does not mean every capability is available.

We store connection and resource identifiers, encrypted credentials, approved permissions, and operation records such as request IDs, content fingerprints, status, timestamps and platform result IDs. Publishing history may include a text or caption and media URL snapshot; pending requests can include an encrypted operation payload. Uploaded source media is stored separately in Cloudflare R2 and delivered for previews and platform fetching. Anyone with a source media URL can access it while it remains available; a platform audience setting does not restrict that source URL.

Meta receives the information needed to perform your requested operation. Our hosting, database and storage providers process data to operate the service. If you connect through an authorized developer or SaaS customer, that operator can request permitted actions and receive the associated resource, content, conversation and reporting results for your customer profile, but not the platform credentials. Review that operator's privacy policy as well. We do not sell connected Meta account data or use it for data brokerage, competitor research, our own advertising audiences or general-purpose AI model training. The separate website analytics, Meta Pixel and Conversions API practices below do not authorize these uses of connected account data.

Connection data is retained while connected. Disconnecting in Console removes active credentials, selected resource details and related connection sessions, and clears stored publishing payloads and content snapshots. For Facebook and Meta Ads we also attempt to revoke the app's access; if revocation fails, or for another integration without automatic revocation, remove Admapix in the relevant Meta app or website's connected-app or business-integration settings. Revoking access to the same Meta app may affect its other connected features.

Minimal publishing and messaging receipts can remain after disconnect to prevent duplicate actions and investigate uncertain outcomes, until account deletion or a deletion request. Disconnecting does not automatically erase separately uploaded media, browser drafts or backup copies, delete posts or messages already delivered to Meta, or pause or delete advertisements. An operation already submitted may still finish. Contact support@admapix.com to request deletion of retained integration data and media; any legally required retention will be explained when we handle your request.

Step-by-step instructions for disconnecting, revoking access and requesting deletion: https://www.admapix.com/data-deletion.

Meta also processes information under its own privacy policy: https://www.facebook.com/privacy/policy/.

YouTube and Google Ads account integrations — October 12, 2026

When you connect a Google account, AdMapix receives the account identifier, approved OAuth permissions, and access/refresh tokens. For YouTube, we read your authorized channel ID and name to let you select and bind your own channel, and retrieve channel analytics such as views, watch time and subscriber changes for the date range you select.

When you explicitly approve an upload, we send your selected video, title, description, visibility and made-for-kids choice to YouTube. We also read that video's upload, processing and visibility status. Video bytes pass through our service in bounded chunks and are not saved to the integration database. We do not collect your Google password.

For Google Ads, we discover the advertising accounts and manager relationships you are authorized to access, including account IDs, names, currency and time zone. We use your selected account to display and manage budgets, campaigns, ad groups, ads, keywords, targeting and supported assets, and retrieve impressions, clicks, costs and conversions for the dates you select. Changes are sent to Google only for operations you authorize. New campaigns, ad groups, ads and keywords start paused; enabling delivery requires additional confirmation.

If you connect through an authorized developer or SaaS provider, that provider can request operations and receive account, advertising and reporting results for the customer profile associated with your connection. Google access and refresh tokens are not returned to that provider. Minimal advertising operation receipts, including request identifiers, fingerprints, status and results, are retained across reconnects to prevent duplicate writes and resolve uncertain outcomes, until your AdMapix account is deleted or you request their deletion. Contact support@admapix.com to request deletion of retained integration records.

OAuth tokens are encrypted on our server and are not exposed to API callers. Account/permission records and channel or advertising-account bindings are retained while your connection is active. Reports and upload results are displayed for your requested operation. Our hosting and database providers process data only to operate these features under our instructions.

Google user data is used only to provide and improve the user-facing connection, publishing, advertising account management and reporting features you request. It is not sold, used for personalized advertising, transferred to data brokers, or used to train generalized AI or machine-learning models. We do not allow human access except with your consent, for security, to comply with law, or for permitted internal operations on aggregated and anonymized data.

AdMapix's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements: https://developers.google.com/terms/api-services-user-data-policy.

Disconnecting in Console deletes active connection credentials and resource bindings and attempts to revoke Google access. Disconnecting Google Ads through the customer API removes local credentials and bindings without revoking Google access. Revocation at Google may affect other grants for the same Google account and Cloud project. You can revoke access from Google Account permissions: https://myaccount.google.com/permissions. Disconnecting does not delete uploaded YouTube videos or pause or delete Google Ads campaigns; manage those in YouTube Studio or Google Ads. Contact support@admapix.com to request deletion of integration data or other retained account records.

Connected YouTube and Google Ads data is not sent to our website's advertising pixels, used to build advertising audiences for our own marketing, or added to competitor-research or advertising-intelligence datasets. The site analytics and advertising-cookie practices below do not authorize these uses of connected account data.

YouTube API data follows the deletion requirements in the YouTube API Services Developer Policies: https://developers.google.com/youtube/terms/developer-policies. These include deletion as soon as possible and within seven calendar days when you request deletion of stored YouTube data or revoke consent through our service. Revocation through Google Account settings also requires removal of the associated API data under those policies. The general six-month account retention and 30-day support response periods below do not extend these platform-specific deadlines. Contact support@admapix.com with your AdMapix account or customer profile and the data you want deleted; do not send passwords or tokens.

Google also processes data under its own privacy policy: https://policies.google.com/privacy.

TikTok account connection and publishing — October 19, 2026

When you connect TikTok, AdMapix receives your account identifier, approved permissions, and OAuth access and refresh tokens. We retrieve your display name or nickname, avatar, and the creator settings needed to show the publishing options available to your account, such as visibility, interaction settings and video duration limits. We do not receive your TikTok password. Tokens are encrypted on our server and are not returned to API customers.

We use this data to connect the account you choose, publish content you approve, and show publishing progress and history. For Direct Post, we send TikTok your selected video or supported media, caption, visibility, interaction choices and applicable commercial-content or AI-content disclosures after your confirmation.

We store connection and permission records, publishing request identifiers, content fingerprints, status, timestamps and TikTok publishing identifiers. To display Posts and help you identify an operation, we also store a snapshot of the title or caption and media URL. Drafts and pending request details may remain in your browser for editing or recovery. Uploaded media is held in our Cloudflare R2 storage and delivered through our media service for preview and platform fetching; media bytes are not stored in the integration database. A source media URL can be accessed by anyone who has it while it remains available; selecting a private audience on TikTok does not make that source URL private.

TikTok receives the content and settings needed to perform your requested action. Our hosting, storage and database providers process the data to operate these features. If you connect through an authorized developer or SaaS application, that application's operator can request the operations you authorize and receive the associated account and publishing results for your customer profile. It does not receive your TikTok access or refresh tokens. Review that application's privacy policy before connecting. We do not sell TikTok account data, use it for competitor research or our own advertising audiences, or use it to train AI or machine-learning models.

Connection records and publishing history are kept while the connection is active. In Console, open Connections, select the TikTok connection and disconnect it. This deletes its stored credentials, related integration sessions and publishing records from active integration storage, and attempts to revoke TikTok access. If revocation cannot be confirmed, remove Admapix in TikTok's app permissions. You can also remove access there independently. Content already delivered to TikTok may remain there, and an action already submitted may finish; manage published content in TikTok.

Disconnecting TikTok does not automatically delete separately uploaded source media from R2 or drafts saved in your browser. Source media supports publishing and post previews and remains until removed from media storage. Clear local drafts in the publishing interface, and contact support@admapix.com to request removal of retained media or other integration data, providing your AdMapix account or customer profile and the relevant post or media reference. Backup copies follow the hosting provider's backup lifecycle. Do not send passwords or tokens.

TikTok also processes information under its own privacy policy: https://www.tiktok.com/legal/page/row/privacy-policy/en.

TikTok for Business — separate permissions

Business account analytics, comments, messaging, advertising and Spark Ads require separate platform permissions and feature availability; connecting TikTok for publishing does not grant them. These features access data only when the relevant integration is enabled, the necessary permissions are approved and you authorize the account and operation.

Where available, account and post identifiers and performance metrics support analytics; comment text, message content, attachments and conversation identifiers support the interactions you request; advertiser and asset identifiers, creatives, campaign settings, budgets, performance reports and Spark post authorizations support advertising management. Any additional data collection, retention or sharing is explained in the relevant feature before you authorize it. This section does not represent that every Business API capability is currently approved or available.

LinkedIn integration — October 2026

When you connect LinkedIn, AdMapix receives your LinkedIn member ID, name, profile photo, the permissions you approve, and OAuth access/refresh tokens. We also retrieve the LinkedIn Pages you administer so you can select the Page you want to manage. We never receive your LinkedIn password.

We use this access only to provide the features you request for your own Pages: publishing posts you approve, viewing and responding to comments and reactions, and showing Page and post analytics (such as impressions, clicks, engagement and follower changes) for the dates you select. Content is sent to LinkedIn only when you explicitly approve it.

OAuth tokens are encrypted on our server and are never returned to API callers or third parties. LinkedIn data is not sold, shared with data brokers or other customers, used for advertising targeting, used for competitor research or ad intelligence, or used to train AI or machine-learning models. We keep LinkedIn data only as long as needed to provide the feature you requested, in line with the LinkedIn API Terms of Use.

Disconnecting LinkedIn in AdMapix deletes your stored tokens and Page bindings. Existing posts remain on LinkedIn. You can also revoke access at any time in LinkedIn under Settings → Data privacy → Permitted services. To request deletion of LinkedIn integration data, contact support@ admapix.com; never send passwords or tokens.

LinkedIn also processes data under its own privacy policy: https://www.linkedin.com/legal/privacy-policy

1. Who we are

MIAOZHIAI PTE. LTD., registered in Singapore at 503 Canberra Drive, #02-10 Canberra Residences, Singapore 768125, operates AdMapix at www.admapix.com ("we", "us", "AdMapix"). We are the data controller for personal data processed through the Service.

2. What we collect

Account data: email, username, hashed password, avatar URL, display name.

Payment data: Stripe customer ID, subscription tier, purchase history, invoice amounts, last four digits of card (if used), refund records. Full card numbers or Alipay account IDs are processed directly by Stripe and never stored on our servers.

Usage data: API calls, search queries, report generations, credits consumed, feature access logs, login timestamps and IP address at login.

Marketing attribution: the referring URL when you first visited, UTM parameters, and the first-touch source/medium. Used to understand which channels drive signups.

Analytics and advertising measurement: Google Analytics 4, Meta Pixel, and X Pixel collect page views, browser/device signals, referral identifiers, and conversion events. X events measure visits, completed registrations, and the first manual search observed per account in the browser. Our X event code sends an opaque conversion ID, not search queries, email addresses, or phone numbers. When you register or subscribe, hashed identifiers may be sent through Meta Conversions API to match and deduplicate conversions.

Communications: support emails and in-app feedback submissions, including any files you attach.

3. How we use it

Provide the Service: authenticate you, meter credit usage, generate reports, deliver purchased features.

Billing: process subscription renewals, one-time credit pack purchases, and refunds via Stripe and Alipay (where applicable).

Safety and fraud prevention: detect unusual activity, block automated abuse, enforce quota limits, protect against account takeover.

Communication: transactional emails (verification, receipts, renewal reminders, service updates), optional marketing emails (you can opt out via unsubscribe link).

Analytics and product improvement: aggregate usage patterns to prioritize features.

4. Legal bases

Contract performance: processing required to deliver the subscription you purchased.

Legitimate interests: fraud prevention, security logging, product analytics.

Consent: marketing emails, non-essential cookies.

Legal obligation: tax record-keeping, law enforcement requests.

5. Who we share with

Stripe (payment processing, including Alipay).

Resend (transactional and marketing email delivery).

Google Analytics, Google Ads, Meta, and X (site usage, advertising attribution, conversion measurement, and event deduplication).

Cloudflare (CDN, DDoS protection).

Supabase / PostgreSQL providers (managed database hosting in Singapore region).

We do not sell your personal data to third parties.

6. Cookies

Essential cookies (authentication token, locale, theme preference) are required for the Service to function.

Analytics cookies (Google Analytics) track anonymized page views; you can disable them via your browser settings.

First-party attribution cookies (admapix_ft, admapix_lt, admapix_sn) record the page you first arrived on, the site that referred you, any campaign parameters in the link, and any advertising click identifier it carried (for example gclid or fbclid), plus the time of your most recent page request so we can tell one visit from the next, kept for up to 12 months so we can tell which of our own pages bring in users. They hold no name, email or account identifier. When you start a checkout, these values are attached to the Stripe payment record so a purchase can be traced back to the page that led to it; they are not otherwise shared.

Advertising cookies (Google Ads, Meta Pixel, and X Pixel, including _fbp/_fbc and X click identifiers) support campaign attribution, conversion measurement, and event deduplication. X Pixel follows the marketing consent choice; declining prevents our X tag from loading and sending events.

7. Data retention

AdMapix account and billing-reconciliation data: retained while your account is active, plus 6 months after deletion for refund/tax reconciliation, then permanently anonymized. Connected-platform data and OAuth credentials follow the platform-specific rules above; this period does not extend their retention.

Payment records: retained 7 years to comply with Singapore tax law.

Usage logs: rolling 12 months.

Support emails: 24 months.

8. Your rights

You can access, export, correct, or delete your personal data at any time by emailing support@admapix.com. We respond within 30 days.

If you are in the EU/UK, you also have the right to lodge a complaint with your national data protection authority. If you are in China, you have equivalent rights under PIPL.

9. International transfers

Our database is hosted in Singapore (Supabase ap-southeast-1). Stripe, Resend, Google, and Meta process data in their respective regions (US/EU/global). Where applicable, transfers outside your region are covered by Standard Contractual Clauses or equivalent safeguards.

10. Security

All traffic is encrypted with TLS. Passwords are stored as bcrypt hashes. We use Stripe's PCI-compliant infrastructure for payment details (we never see your full card number). Admin access is scoped and logged. Suspected breaches are reported to affected users within 72 hours.

11. Children

The Service is not directed at children under 16. If you believe a minor has provided us with personal data, contact us and we will delete it.

12. Changes to this policy

We may update this Privacy Policy. Material changes will be notified by email or in-app banner at least 30 days before taking effect.

X publishing prototype — September 18, 2026

Connecting X shares your account ID, username, display name, approved permissions and OAuth tokens with Admapix. Tokens are encrypted on the server; we never receive your X password or return X tokens to API callers. Your account name is cached at connection time to avoid unnecessary provider reads.

When you approve publication, your text, image, accessibility description and disclosures are sent to X. Drafts and pending requests are saved in this browser tab until you start a new Post or close the tab. Images and Post text are not stored in the integration database.

Disconnecting deletes active credentials and customer sessions and attempts to revoke X authorization. A provider request already in flight may finish. Minimal receipts (customer/account references, request ID, content hash, time, status and Post ID) are retained across reconnects to prevent duplicate publication until account deletion or an explicit deletion request. Existing Posts remain on X. If revocation fails, remove Admapix from X Connected apps.

The standalone X page and OAuth callback do not load analytics or advertising scripts. This is a limited invited prototype. X data is not sold, used for off-X advertising targeting, or used to train AI. Contact support@admapix.com to request access or deletion; never email passwords or tokens.

Pinterest publishing pilot — September 17, 2026

When you choose to connect Pinterest, Pinterest sends Admapix OAuth access and refresh tokens, account identity and the permissions you approve. We keep tokens encrypted on the server and use them only to provide the authorized account connection, board selection and original Pin publishing features. We do not receive your Pinterest password.

We retrieve your account and board information to display the connection and let you select a board. The image URL, title, description, destination link and disclosures you confirm are sent to Pinterest to create your Pin. We store connection identifiers and minimal request receipts (request identifier, content hash, status and Pinterest resource identifier) for isolation, retry handling and support.

If you connect through a developer or SaaS provider using Admapix, that provider can request operations for the customer reference associated with your connection and receive the resulting account, board and publishing responses. Pinterest access and refresh tokens are not returned to that provider. This processing is for the account-management and publishing service you authorize; Pinterest data is not sold or used to train AI models or perform competitor research.

Connection links expire after one hour. Disconnecting deletes the connection tokens and related session and publishing records from active integration storage. It does not delete Pins or boards already created on Pinterest and does not cancel a request already in flight. Remove Admapix in Pinterest Settings > Apps to revoke platform authorization. Backup copies follow the hosting provider's backup lifecycle.

The standalone Pinterest publishing and OAuth callback pages do not load advertising or analytics scripts. Other Admapix pages retain the practices described elsewhere in this policy.

For help accessing or deleting Pinterest integration data, email support@admapix.com with the relevant Admapix account or customer reference; never send passwords or access tokens.

Discord publishing pilot — September 18, 2026

Connecting Discord shares your Discord user ID and username, an authorized server ID/name, approved permissions and OAuth tokens. User tokens are encrypted on the server. The bot token remains in server configuration and is not returned to API customers. We never request your Discord password.

We verify the authorizing user’s current server-management role and both user and bot channel permissions when listing channels, binding a channel or publishing. Only supported channels accessible to both are returned. This pilot does not retrieve channel message history, member lists or presence data.

The text and attachment you approve are sent to the bound Discord channel by the Admapix bot. Drafts and pending requests remain in the current browser tab. Integration storage keeps encrypted credentials, server/user/channel references and minimal request receipts (ID, content hash, status, time and message ID); it does not store message text or attachment bytes.

Disconnecting deletes active local credentials and customer sessions and attempts to revoke the user OAuth grant. It does not delete existing messages or remove the bot from the server. Remove Admapix from Discord Authorized Apps and remove the bot from the server for complete platform removal. Receipts survive reconnects to prevent duplicate messages until account deletion or an explicit deletion request.

The standalone publishing page and callback do not load analytics or advertising scripts. Contact support@admapix.com for integration data access or deletion requests; never send passwords or tokens.

13. Contact

Data protection inquiries: support@admapix.com.