Privacy policy
Last updated: September 14, 2026
Privacy of connected accounts and services
Account authorization and granted permissions determine the data Mollkom can access to provide the functions a merchant chooses. The platform-specific sections on this page describe data use, retention and deletion, and continue to apply to each integration.
Authorization can be revoked in the provider’s account settings. Data deletion requests and questions can be submitted through the contact methods in this policy. Merchants must provide required notices and obtain necessary consent before enabling measurement tools or sending customer data to advertising services, in accordance with applicable policies and requirements.
Google and YouTube data in Mollkom
Section updated September 12, 2026. Mollkom uses YouTube API Services.
Connection and data accessed
When you connect a YouTube channel to Mollkom, you authorize the application directly with Google. Mollkom does not ask for or store your Google password. We store authorization and refresh tokens, channel ID, granted scopes and channel information needed to display the connection. Depending on the features and permissions you choose, we access video metadata, visibility, processing and statistics; comments, author display names and replies; playlists; caption tracks; broadcast and live chat data; and watch, engagement and subscriber analytics. This connection does not request YouTube revenue access.
How we use the data
We use this data to provide the features the merchant requests: identify their channel, show its content and results, upload their original files, execute their edits and replies, manage comments, playlists, captions, thumbnails and broadcast events, and refresh the connection. The merchant chooses visibility and audience and authorizes actions before execution. We do not download or store copies of YouTube videos. Original video files you choose to upload pass through temporary chunks while being sent to YouTube.
Sharing, protection and AI
Channel data is available only to the merchant and authorized store members according to their roles. Mollkom keeps credentials on its servers, separate from the browser, and uses HTTPS in transit. Hosting and database providers process data on our behalf to operate the service. Content you choose to publish is sent to Google/YouTube. We do not sell Google data, use it for advertising targeting, or share it with data brokers. This connection does not send YouTube data or audience comments to AI models or use it to train general-purpose models. Users may prepare independent original copy in content tools and review it themselves before posting.
Retention, deletion and revocation
We retain connection tokens while the connection remains active and periodically verify authorization. We refresh stored channel data, retain action records and inactive upload records for up to seven days, and delete connections not successfully verified within seven days. Video lists, comments and analytics are fetched on demand; action logs may retain the YouTube result of a change for the retention period stated above. “Disconnect & delete connection data” revokes Google access and deletes connection data and its history from Mollkom immediately after successful revocation; it does not delete your YouTube videos. When we detect Google revocation, we delete related data. Contact info@mollkom.com to request deletion or ask questions, or revoke Mollkom access in Google settings below. Revocation may include other permissions granted to the same app.
How to delete your data and revoke access
1. Sign in at app.mollkom.com. Open Settings → Social accounts (Connection center), then choose YouTube. 2. Select “Disconnect & delete connection data” and confirm. This revokes Google authorization and removes tokens, channel data, upload records and related action history from Mollkom’s active systems; it does not delete your videos from YouTube. 3. You may also open the Google Account connections page linked below, select Mollkom, choose Delete all connections, and confirm. This can also revoke other permissions granted to the same application. We delete related data when revocation is detected, and no later than seven days after revocation. 4. If you cannot sign in to Mollkom, email info@mollkom.com from your store account email with your store name or channel ID and request deletion of Google/YouTube data. After verifying ownership, we delete the requested data within seven days and confirm completion; never send passwords or authorization tokens.
Refresh and cleanup frequency
Video lists, comments and analytics are fetched from YouTube when opened or refreshed. The browser memory cache becomes stale after 30 seconds and unused results are removed after 60 seconds; these lists are not persisted to disk. Connection maintenance runs hourly and refreshes stored channel data when its last successful check is over 24 hours old. Failed checks do not mark old data as refreshed. Daily cleanup removes action records, inactive upload records, and unverified connections after six days so that the daily interval keeps their retention within seven days. Authorization for successfully verified channels remains until disconnection or revocation.
Limited Use
Mollkom’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
X platform data
X integration update: September 11, 2026.
Account connection and permissions
Merchants authorize Mollkom Social Studio on X’s official authorization screen. We do not request an X password. Account identity, granted scopes, access tokens and refresh tokens are stored on our server and used only for the store that connected the account. Merchants choose account reading, publishing and media, messages, or expanded management.
How data is used
Depending on granted permissions, we display account information, posts, mentions, engagement, audiences, lists and available legacy direct messages. Authorized users review posts, replies, messages and account actions before sending them. They can enable or disable event delivery. X requests and events consume the platform’s API credits and remain subject to X limits.
Retention and deletion
X action logs, received events and temporary uploaded media are retained for up to seven days and removed by scheduled cleanup. The older legacy message cache may remain for up to 30 days. Connection tokens remain until disconnection or authorization revocation. Disconnecting X in Mollkom revokes authorization and deletes connection data and its logs; we also clear data on receiving X’s authorization-revocation event. Disconnecting Mollkom does not delete posts or messages already sent on X.
Agent drafts and encrypted chat
The available agent mode creates drafts for human review. With user consent, we send their entered text and store style instructions to OpenAI to create the draft. We do not automatically send the inbox or use X data to train Mollkom models. Autonomous replies are disabled. Encrypted X Chat requires separate key setup; the legacy inbox does not decrypt it or request users’ encryption PINs or private keys.
Control and contact
Store owners and administrators can disconnect X in Mollkom’s X workspace. Users can also revoke authorization in X’s connected-app settings. For data deletion or privacy requests, contact privacy@mollkom.com.
Threads platform data
Threads integration update: September 11, 2026.
Connection and use
Store owners and administrators connect a Threads account through Meta’s official authorization screen and choose permissions. Mollkom does not ask for a Threads or Instagram password. We store account identity, username, granted permissions and the access token on our server for the connected store. Subject to authorization and Meta approval, features include posts, replies, mentions, analytics, public content and profile discovery, locations and optional sharing to the linked Instagram Story.
Publishing and conversations
An authorized user reviews content and actions before approval. Mollkom may publish at the time chosen by the user and track media processing. Reply, mention, publishing and deletion events are received when Meta permits delivery. The current Threads API does not provide private messages, likes or following management.
Retention and deletion
Received events are retained for up to 30 days and action records for up to 90 days after creation. Temporary media is removed after 31 days unless attached to an active publishing operation. Authorization data remains until disconnection or revocation. Disconnection stops new operations, waits for in-flight operations, then deletes the connection, settings, action records, events and uploaded media. Cleanup retries after service failures. We also process signed deauthorization and data-deletion requests from Meta. Disconnecting Mollkom does not delete posts already published on Threads.
Agent drafts
With the user’s consent, their entered text and store style instructions are sent to OpenAI to prepare a draft for human review. We do not automatically transfer Threads replies or mentions to the AI provider, or use Threads data to train Mollkom models. Autonomous publishing and replies are disabled.
Control and contact
Store owners and administrators can disconnect the account in Mollkom’s Threads workspace or revoke authorization in Threads app settings. For privacy questions or deletion requests, contact privacy@mollkom.com.
Instagram platform data
Instagram integration update: September 11, 2026.
Connection and control
Store owners and administrators connect a professional Instagram account through Meta’s official authorization screen. Mollkom does not request an Instagram or Facebook password. Account and Page identifiers, username, granted permissions and access tokens are stored on our server for the connected store. One connection flow may include both Page authorization and a Facebook user grant for additional features. User consent does not establish general Meta approval or shopping eligibility.
Content and conversations
Subject to permissions and account eligibility, we process posts, media, comments, replies, mentions, insights, collaboration invitations, catalog data and partnership settings. An authorized user reviews publishing, replies and management actions; publishing may execute at the time they selected. We receive messages and events sent by Meta and retain conversation history for customer service. Standard replies are limited to Meta’s 24-hour window. The separately approved human-support extension is never used for automated replies.
Optional assistant and processing providers
With merchant consent, draft requests and store instructions are sent to OpenAI to generate editable text. When automatic replies are enabled, the necessary message context and store information may be sent to Google through Vercel AI Gateway. If voice processing is used, audio may be sent to ElevenLabs or OpenAI for transcription, and OpenAI may generate a spoken response. The merchant can disable the assistant or take over a conversation. We do not use Instagram data to train Mollkom models. Supabase provides data storage and backend services; Vercel provides frontend hosting and the gateway where used.
Retention and deletion
The Instagram workspace retains events for up to 30 days and completed action records for up to 90 days. Temporary workspace media is removed after 31 days unless linked to an active publishing operation. Message history and participant data are retained for conversation service while connected, until disconnection or a valid deletion request is processed. Disconnection stops new operations, waits for in-flight operations, and removes the account authorization, settings, records, messages and associated local media; cleanup retries after failures. We process signed deauthorization and data-deletion requests from Meta. Disconnecting Mollkom does not remove posts on Instagram; deleting a published post is a separate explicit action.
Contact
Disconnect the account in Mollkom’s Instagram workspace or revoke authorization in Meta settings. For privacy questions or data-deletion requests, contact privacy@mollkom.com.
Facebook and Messenger data
Facebook integration update: September 11, 2026.
Page connection and control
Store owners and administrators connect a Facebook Page through Meta’s official authorization flow. Mollkom does not request a Facebook password. Access tokens, Page identifiers, granted permissions and Page management tasks are stored on the server for the connected store. User authorization, Page eligibility and Meta app approval are separate requirements; displaying a feature does not make it available.
Content and customers
Subject to granted permissions, we process Page posts, photos, videos, Stories, Reels, comments, ratings, insights and Page details. Authorized users can publish, schedule and manage content, receive Messenger conversations and reply with text, media, buttons and cards. Lead-form data and approved utility templates are processed when their permissions are available. Messages are subject to Meta’s response window, message purpose and customer consent; the human-support extension is never used for automated replies.
Optional assistant
Facebook assistant settings are independent; merchants can disable the assistant or hand a conversation to staff. With merchant consent, draft requests are sent to OpenAI. Automatic replies may process necessary conversation context and store information using Google through Vercel AI Gateway. If voice-message processing is used, audio may be sent to ElevenLabs or OpenAI for transcription, and OpenAI may generate a spoken response. We do not use Facebook data to train Mollkom models. Supabase provides storage and backend services; Vercel provides hosting and the gateway where used.
Calls
Where Meta enables Messenger calling, authorized users can place and receive browser audio calls. Microphone use begins only when the user starts or accepts a call. Outbound calls require the customer’s current Meta call permission. Mollkom does not record call audio. We process call signaling, participant identifiers, status and duration. Temporary WebRTC negotiation data is erased after one hour by a cleanup cycle running every ten minutes.
Retention and deletion
Facebook events are kept for up to 30 days; completed action records and drafts for up to 90 days. Temporary workspace media is removed after 31 days unless linked to a draft or active publishing operation. Conversation messages and participant data are retained while connected, until disconnection or a valid deletion request is processed. Disconnection stops new operations, waits for in-flight work, and removes Facebook authorization, settings, records, messages and associated local media; cleanup retries after failure. We process Meta-signed deauthorization and data-deletion requests. Disconnecting Facebook does not disconnect Instagram or delete public Page posts. For privacy questions or deletion requests: privacy@mollkom.com.
Introduction
Welcome to the privacy policy of Mollkom (مولْكوم), owned and operated by Phitek, whose legal name is شركة الصناديق العربية لتقنية المعلومات (ARABIAN BOXES), Commercial Registration No. 7030996412, Kingdom of Saudi Arabia. We provide ecommerce solutions and are committed to protecting user privacy to high standards.
This policy applies to:
- Merchants: who use our platform to create and manage stores.
- Customers: who shop from stores built on our platform.
- Visitors: who browse our website.
Data we collect
We collect different types of data to provide and improve our services:
Account data
- Full name and email address
- Phone number and address
- Business name (for merchants)
- Payment information (encrypted and protected)
Usage data
- Order and transaction history
- Products added or updated
- Your interactions with platform features
- Pages visited and time on site
Technical data
- IP address and browser type
- Operating system and device type
- Cookies
- Geolocation (with your permission)
Content you provide
- Product images and descriptions
- Logos and trademarks
- AI-generated content
- Messages and notes
How we use your data
We use your data for the following purposes:
- Providing services Create and manage your account, process orders, enable payments.
- Improving your experience Personalize content, suggest features, improve the UI.
- Communicating with you Important updates, order notifications, and support.
- Security and protection Detect fraud, prevent abuse, protect your rights and ours.
- Analytics Understand how services are used to keep improving them.
- Legal compliance Meet applicable laws and regulations.
We will not use your data for direct marketing without your explicit consent.
Legal basis for processing
We process personal data on the following legal bases:
- Contract performance Data needed to deliver the services you requested (store setup, orders).
- Consent Where you explicitly agree to processing for specific purposes (e.g., marketing).
- Legitimate interests To improve services, prevent fraud, and keep the platform secure.
- Legal obligation When the law requires us to process data (e.g., taxes and invoices).
Data sharing
We never sell your personal data. However, we may share data in the following cases:
Service providers:
- Payment gateways (Tap, Mada) - to process payments
- Cloud hosting - to store data
- Analytics services - to understand usage
- Email services - to communicate with you
Legal requirements:
We may disclose data in response to lawful requests, to protect our legal rights, or in emergencies to protect safety.
Business transfers:
In a merger or acquisition, data may transfer to the new entity with the same level of protection.
Assurance: All third parties we share data with are contractually required to protect it and use it only for defined purposes.
Meta Tech Provider commitments
Mollkom is a Meta-registered Tech Provider serving merchants who need to build storefronts, connect Facebook and Instagram accounts, run and manage ad campaigns, and auto-reply to customer messages. As part of this role we make the following commitments to you and to Meta:
- We never request more Meta permissions than are strictly required to power the feature you yourself enabled (principle of least privilege).
- We never share, sell, or reuse your access tokens for any other merchant — every merchant has isolated tokens stored in a tenant-scoped row.
- Access tokens are encrypted at rest (AES-256) and we proactively refresh long-lived tokens before expiry so your service does not silently break.
- We comply with Meta Platform Terms, Developer Policies, and Data Use Policy, and we honor any advertising restrictions Meta places on content or audiences.
- When you remove Mollkom from Facebook's Apps and Websites, Meta sends a signed deauthorization request. We verify its signature, stop new operations and remove the affected authorization and local connection data. In-flight operations and temporary failures can delay cleanup; failed cleanup is retried.
- When Meta sends your signed data-deletion request, we verify it and process deletion of the related local integration data. We return a confirmation code starting with 'mollkom-del-' and a status URL. The confirmation acknowledges the request; cleanup may continue while in-flight work finishes or a failed step is retried.
- We run periodic security reviews of our Meta integration and respond to any App Review or security inquiries from Meta within the timeframes their policies set.
Data security
We take strong measures to protect your data:
- Encryption Data encrypted in transit (TLS 1.3) and at rest (AES-256).
- Authentication Multi-factor authentication and hashed passwords.
- Monitoring Continuous monitoring for threats and suspicious activity.
- Limited access Data access is limited to authorized staff.
- Backups Regular backups stored securely across locations.
- Testing Periodic security testing and ongoing updates.
Your responsibility: You must keep your password secret and notify us immediately of any unauthorized access.
Your rights
Under Saudi PDPL and GDPR principles, you have the following rights:
- Right of access Request a copy of personal data we hold.
- Right to rectification Correct inaccurate or incomplete data.
- Right to erasure Request deletion of your personal data ('right to be forgotten').
- Right to portability Receive your data in a machine-readable format.
- Right to object Object to certain processing activities.
- Right to restrict processing Request limits on how we use your data.
- Right to withdraw consent Withdraw consent where processing is consent-based.
How to exercise rights: email privacy@mollkom.com and we will respond within 30 days.
Data deletion
We give you four separate ways to delete your data from Mollkom — choose whichever fits your situation:
1. Disconnect a single social account
Open the connected channel's workspace or its connection settings in your store dashboard and choose Disconnect. This stops new channel operations and removes its authorization and associated local integration data, according to the channel-specific retention section above. Cleanup may wait for in-flight work and retry after a failure. Your products, orders, other social connections and public provider posts are not deleted by this action.
2. Delete your full Mollkom account (Self-service)
From your store dashboard → Settings → Account → 'Delete account', type the confirmation word and click Delete. The system runs a single atomic transaction that deletes: your stores and everything cascading from them (products, orders, shipping settings and themes, Meta / Instagram / TikTok / WhatsApp / YouTube / X / Snapchat accounts and their tokens, ad accounts, Pixels, catalogs), your profile, your roles, your team members, push notification tokens (mobile + web), notification preferences, store customers, storage files (images and attachments), and finally your auth user record (auth.users). All technical error logs and AI usage logs are anonymized (user_id stripped) — analytics signals stay, but no link back to you. An audit row is written to account_deletion_events so platform super-admins can later prove deletion to regulators.
3. Email request
Email your deletion request from the address registered on your account to privacy@mollkom.com and we will respond within 30 days max. This option is useful if you cannot sign in (e.g., lost password or device). We verify your identity before executing.
4. Request via Meta (User data deletion request)
In Facebook's Apps and Websites settings, select Mollkom and request deletion of your integration data. Meta sends us a signed request; we verify it and delete the affected local authorizations, connections and associated integration records. Processing handles in-flight operations and retries temporary failures. We return a confirmation code starting with 'mollkom-del-' and a status URL. This does not delete public posts on Meta or unrelated store data.
What is kept and not deleted?
- Invoices and financial transaction records: kept 7 years (regulatory tax requirement — Zakat, Tax and Customs Authority).
- Technical error logs and AI usage logs: anonymized — user_id is stripped but the row body is kept for performance tuning and bug detection.
- The deletion audit row itself (account_deletion_events): kept to prove deletion to regulators later. It contains user_id, deletion timestamp, and store count — no access tokens, no store content.
Official Meta callback endpoints:
- Data Deletion Request: https://xpqboxafsvkwejwufdam.supabase.co/functions/v1/meta-data-deletion-callback
- Deauthorize: https://xpqboxafsvkwejwufdam.supabase.co/functions/v1/meta-deauth-callback
Data retention
We retain data for the following periods:
| Data type | Retention period |
|---|---|
| Account data | For the life of the account + 1 year |
| Transaction records | 7 years (legal requirement) |
| Support records | 3 years from last contact |
| Analytics data | 26 months |
| Cookies | Depends on cookie type (1 day - 2 years) |
After retention ends, we delete or irreversibly anonymize data.
International data transfers
As a Saudi company serving customers globally, we may need to transfer data outside Saudi Arabia:
Transfer safeguards:
- Transfer only to jurisdictions with adequate protection.
- Use approved standard contractual clauses (SCCs).
- Ensure recipients meet the same protection standards.
- Encrypt all data in transit.
For EU users: we follow GDPR transfer requirements and approved EU Commission mechanisms.
Children's privacy
Our services are not directed at children under 18, and we do not knowingly collect their data.
If you are a parent or guardian and believe your child provided personal data, contact us at privacy@mollkom.com and we will delete it promptly.
Policy updates
We may update this policy from time to time to reflect changes in practices or law.
- We will publish updates on this page with a new date.
- For material changes, we will email a notice.
- Continued use means you accept the updated policy.
- We encourage you to review this page periodically.
Contact us
If you have privacy questions or concerns, contact us:
- Data protection officer (DPO) privacy@mollkom.com
- General support support@mollkom.com
- Company Phitek — شركة الصناديق العربية لتقنية المعلومات (ARABIAN BOXES)
- Commercial Registration 7030996412
- Address Kingdom of Saudi Arabia
We aim to respond to privacy inquiries within 30 days.
Right to complain: If you are not satisfied with our response, you may lodge a complaint with the competent authority (Saudi Data & AI Authority - SDAIA).