Privacy Policy

Version 1.0 — effective 18 September 2026.

This notice covers the Moklex website, invitation-only application and enabled integrations. It explains what information Moklex handles, why, who receives it, how long it is kept and what you can ask for.

Responsible operator / controller

Daimyo International GmbH (CHE-295.167.208)

Location

Zurich, Switzerland

Privacy contact

info@moklex.com

1. Scope and responsibility

Moklex’s operator is the controller for the personal information it uses to run the service: accounts, authentication, security, support and its own business records.

When a workspace submits personal information about its own clients or other people, that workspace is the controller for it and Moklex acts as its processor, handling the material only to carry out the workspace’s instructions. The workspace is responsible for having the authority and a lawful basis to supply it. A data-processing agreement covering that role is available at the privacy address above and applies to business customers who need one.

The public website presents simulated product screenshots. It has no product signup, contact form, checkout, advertising pixel or website analytics. It is served through Vercel, whose hosting records are separate from the product data described below.

2. Information you provide

• Account and workspace details: your email, profile information, invitations, memberships, role and recorded policy agreements.
• Source material: text, article addresses, documents, transcripts, audio, titles, attribution and extracted text supplied for content preparation.
• Drafts and media: prompts, generated output, edits, images, video, captions and other files you add to a workspace.
• Publishing instructions: selected accounts, schedule and time-zone choices, audience settings, disclosures and consent for a submission.
• Communications: the information you choose to include in support or privacy requests.

Provide only material you are authorized to use and share. Moklex is not intended to hold medical records, identity documents, payment-card details or other sensitive personal records. If required account information or platform permissions are missing, the corresponding feature cannot operate.

3. Connected-account information

When you authorize a supported social account, Moklex receives information permitted by that authorization. This can include account identifiers, handles, display names, profile images, the pages or channels you manage, authorization credentials and their expiry, and information needed to submit your chosen content. Publishing records include destination post identifiers, links, processing status, errors and available metrics for posts sent through the service.

The implementation supports Instagram professional accounts, Facebook Pages, Threads, TikTok, YouTube channels, Pinterest, LinkedIn member profiles, X and Bluesky, subject to activation and access decisions. Facebook uses your manageable Pages; TikTok also supplies account publishing options and restrictions. Pinterest permissions cover the board and Pin access needed for posting; no board-management interface is offered. Bluesky can return email-verification status and account provider information needed for its authorization and media features.

Live connections use the provider’s authorization flow; Moklex does not ask you to enter your social-account password. The integration guide describes supported account types and requested access. During the private beta, only LinkedIn, Bluesky and X can be enabled for live connections, together with YouTube for the test accounts Moklex has registered with Google while Google’s review is pending, during which Google keeps every upload private, and Instagram, Facebook Pages and Threads for the accounts that hold a role on Moklex’s Meta app while Meta’s review is pending, and TikTok for the test accounts Moklex has registered in its TikTok sandbox while TikTok’s review is pending, during which every TikTok post is visible only to its author, and Pinterest while Pinterest grants Moklex Trial access, during which every board and Pin created through Moklex stays in Pinterest’s test environment and is visible only to its creator; the other listed providers remain disabled, and listing them is not evidence of approval or collection.

Account and post statistics. Where statistics are switched on for a platform, Moklex reads the numbers that platform reports for your connected account and for posts published through Moklex: followers, reach, views, likes, comments and shares. The numbers come from the platform’s own interface, are collected once a day and are shown to you on the Analytics page. Moklex stores numbers only. It does not read or store the text of comments, the identity of people who interacted with your posts, or direct messages.

4. Technical and usage information

The product handles sign-in and session records, IP addresses and browser information associated with authentication, API-key records, request and error information, publishing activity and service-usage measurements. These records help control access, apply limits, diagnose failures and account for processing. Hosting and network providers may also process request metadata to deliver and secure the service.

Billing currently operates in test mode. The product keeps test customer and subscription references, plan status and credit or usage records. This website does not collect payment-card information or accept real payments. When paid plans are introduced, payment card details will be handled by the payment processor and not stored by Moklex.

5. Why information is used

The product uses this information to authenticate invited users, maintain workspaces, prepare content, carry out authorized publication, display delivery results, enforce permissions and usage limits, send service messages, investigate failures and carry out disconnection or deletion requests. It does not provide advertising profiles or automated decisions about employment, credit or similar eligibility.

Where data-protection law requires a legal basis, these are the bases Moklex relies on:

Where Moklex relies on legitimate interests, it balances them against your interests and rights before relying on them, and you can object as described in section 12. A platform permission does not by itself settle every data-protection legal basis.

6. AI processing

When enabled, writing generation sends the source text, attribution, selected platforms and writing instructions to DeepInfra. Media generation sends the prompt and any supplied inputs to fal. Output and usage information return to the workspace. Uploading content does not authorize publication of generated results without a publishing instruction. Both remain disabled during the private beta.

Audio transcription and spoken narration run on Moklex’s own ingestion service, hosted in the European Union, rather than at a third-party AI provider, so that material is not sent outside the suppliers listed in section 8.

Moklex does not train its own general-purpose AI models on customer content or connected-platform data. YouTube account information and API results are not sent through its writing or media-generation flow. Material you independently supply for generation is processed as your source content.

Each AI supplier’s own terms govern how long it retains a request and whether it uses inputs to train models. Moklex does not send customer material to a supplier that is not named in this notice, and will update this notice before adding one.

7. YouTube and Google data

When activated, Moklex uses YouTube API Services to identify your authorized channel, upload videos you supply and retrieve statistics for uploaded videos. Stored information includes channel identity, authorization credentials, video identifiers, upload progress, delivery links, status and returned statistics. Moklex does not download YouTube videos or extract their transcripts.

These features are available only in the signed-in browser. Customer API keys, including MCP and n8n connections, cannot retrieve YouTube account information, metrics or provider notifications, or access posts containing a YouTube destination.

The use of Google data is limited to the requested visible features and permitted supporting operations. It is not used for advertising, data resale, credit decisions or training general-purpose AI models. Access by people is limited to permitted support, security or legal purposes, with specific user agreement where required.

Google’s Privacy Policy describes Google’s own processing. You can revoke Moklex’s access through your Google account permissions. You can also disconnect the YouTube account in Moklex. Revoking access and removing stored data are related but distinct steps; the deletion guide explains what Moklex removes and what remains, including content you supplied independently.

8. Who receives information

• Your workspace: authorized members can access shared sources, drafts, media and publishing activity according to their permissions.
• Your selected platforms: the destination receives the content, media and instructions necessary for the post you authorize. Its own privacy practices govern its copies.
• Service suppliers: the companies listed below receive the information needed for their assigned service.
• Authorized tools: an API key can give an external client access within its granted permissions. Choose the tools you connect carefully; browser-only restrictions still apply.
• Legal and security recipients: necessary information may be disclosed to meet a lawful obligation, address abuse or protect rights, subject to applicable restrictions.

During the private beta, live social integrations are limited to LinkedIn, Bluesky, X, Pinterest’s test environment and, for registered test accounts, YouTube, TikTok, Instagram, Facebook Pages and Threads; AI processing remains disabled, and billing remains test-only.

The product has no data-sale or advertising-sharing feature. Media delivery links are temporary, but anyone holding a valid link can retrieve the media until it expires. Connected platforms need access to these links to ingest a post’s media. Public posts may be viewed and copied by others outside Moklex.

9. Cookies and browser storage

The product uses cookies to keep you signed in and to bind a social authorization attempt to the browser that started it. Sign-in sessions last up to seven days and can be renewed during use; authorization-attempt cookies expire after ten minutes. Blocking necessary cookies can prevent sign-in or account connection.

Browser session storage keeps the selected workspace and temporary draft or navigation context; a demonstration session can also be kept for the tab. You can clear this storage through browser settings, but doing so can lose temporary work. Clearing cookies or local storage does not delete server-side workspace records.

The website adds no analytics, advertising or security cookies. Introducing any optional tracking would require updated disclosures and any consent the law requires, before it is enabled.

10. Retention and deletion

Account and post statistics are kept for 400 days. Statistics from YouTube are kept for 29 days. All statistics of a connected account are deleted when you disconnect that account, when you delete your workspace, and when the platform sends Moklex a deletion or deauthorization request for it.

Disconnecting an account stops new work for that connection and disables its active credentials. It does not erase the whole workspace or recall a request already sent to a platform. The YouTube removal process also clears the stored channel profile, related delivery information, cached responses and linked notifications. Google and Bluesky authorization removal can require retries, with an encrypted credential retained for that limited purpose and a seven-day cutoff.

Workspace deletion is an owner-authorized process that removes stored workspace media and associated records. Removing one workspace is not necessarily deletion of your user identity or another workspace. Published copies must be managed on the destination platform.

Backups. Deleting content removes it from the live service, but an encrypted backup snapshot can still contain it until that snapshot expires, currently within seven days. Backups are not used to bring deleted content back: before a restored copy is used, the deletion records below are replayed against it, and sign-in sessions, connected accounts, invitations, queued emails and API keys in the restored copy are cleared so that an old credential cannot become active again.

Deletion records. When a workspace is deleted, Moklex writes a short record — an opaque workspace identifier, a request identifier and the time — to storage held outside its databases and backups. The record contains no content, no name and no email address. It exists so that a workspace deleted after a backup was taken stays deleted if that backup is ever restored. It is kept for as long as a recoverable copy could exist, and the deletion it records does not remove it.

Some request records are kept as markers after their content is erased, so that a repeated request cannot be mistaken for a new one and carried out twice.

Read the deletion guide for the steps and what each one removes.

11. Security and international processing

The product includes workspace access controls, encrypted stored social credentials, hashed API-key authentication and browser-bound authorization attempts. Some retry records retain sensitive values in encrypted form so interrupted requests can be completed safely. Backup copies are encrypted, including their file names and metadata. Security also depends on the hosting configuration, operational access and your account practices; no service can eliminate all risk.

The suppliers in section 8 process information in Switzerland, the European Union and, for Railway, the United States. Some are established outside those countries and may access information from elsewhere for support and operational purposes. Where that happens, Moklex relies on the transfer safeguards in the supplier’s data-processing agreement — the European Commission’s Standard Contractual Clauses together with the amendments recognised for Swiss data, or the supplier’s certification under the EU–US Data Privacy Framework and its Swiss extension. Write to the privacy address for information about the safeguards that apply to a particular supplier.

12. Your rights and choices

Depending on the law that applies, you may request access to your personal information, correction, deletion, restriction of processing or a portable copy, and may object to processing based on legitimate interests. Where processing relies on consent, you can withdraw it without affecting the lawfulness of processing before withdrawal.

Write to info@moklex.com. Identify the account or workspace and explain your request. Do not send passwords or social tokens. Moklex verifies requests by writing to the email address registered on the account; where a request concerns information that is not tied to an account, it may ask for proportionate additional detail to confirm your identity and authority, and to separate your information from other workspace members’ information.

Moklex answers within 30 days. Where a request is complex or there are several, it may extend that once and will tell you why within the first 30 days.

If your information was provided by a workspace acting for its own clients, that organization may need to handle the request, with Moklex’s assistance under the applicable processing arrangements.

You can complain to the Swiss Federal Data Protection and Information Commissioner (FDPIC) in Bern. If you are in the European Economic Area or the United Kingdom, you can also complain to your local supervisory authority.

13. Children

The service is intended for adults aged 18 or older and is not directed to children. Do not create an account for a child. If you believe a child’s information has been submitted improperly, use the privacy email listed above so the circumstances and appropriate removal can be reviewed.

14. Updates and contact

This notice shows its version and effective date at the top. Material changes will be explained through the service or to your account contact as required. New uses of connected-account information will require updated disclosures and renewed consent where applicable before that use begins.

The operator and privacy email are listed at the top of this page and on the contact page. Related documents: Terms of Service and data deletion.