Privacy policy

1. Who provides the service

MMO Creator Studio is a Malaysia-based business founded by CS Ng. We provide Facebook Page content services and operate singapp. This policy covers our public website, client correspondence, cloud publishing platform and separate studio desktop application.

The public website is informational. Client accounts and Facebook authorisation are handled at app.mmocreatorstudio.site. The cloud application privacy notice gives further details of account controls, data handling and retention.

2. Information we use

• Website visits: this static website has no contact form, advertising pixels, analytics scripts or account database. Its hosting provider may process technical connection information, including IP addresses and request logs, to deliver and secure the site.
• Client accounts: username, display name, a salted password hash, account status, connected Facebook identity, login and access times, a general browser/system label and security events. Application usage records do not store raw browser headers, hardware identifiers or IP addresses.
• Facebook connection: Facebook ID and name, authorised Page names and IDs, Page tasks and access credentials. Facebook User access tokens are used during authorisation and are not saved by the application.
• Publishing: selected media, captions, Page destinations, schedules, publishing history, processing results, media IDs and available post links.
• Source rules: configured creator references, source identifiers, downloaded working media, rules and duplicate-protection records. The cloud collector uses a privately stored encrypted source session.
• Correspondence: contact details, instructions and content supplied when a client requests our services or contacts the studio.

3. How we use platform information

Facebook identity information links your account to the correct workspace. Page information displays authorised publishing destinations. Page credentials let the service submit the content you authorise. Page content and processing information help show publishing results and prevent duplicate attempts.

We also use account and operational records to provide support, diagnose errors, maintain account security and respond to access or deletion requests. Managed content work follows the scope and Page access agreed with each client.

4. Client and administrator access

Client workspaces are separated by the connected Facebook identity. Clients use their own authorised Pages. The administrator can manage platform accounts and view account activity, Page connection history, upload counts and recorded publication results across clients, including report exports.

Administrator reporting access does not itself authorise publishing to every client Page. A service engagement does not automatically share a client’s Pages with other platform users. Facebook access and agreed responsibilities remain necessary for managed publishing.

5. Storage and service providers

The public website is hosted on Cloudflare Pages. The web platform runs on an Alibaba Cloud server in Singapore, with Cloudflare providing HTTPS and relaying requests through an encrypted tunnel. Page credentials are encrypted in private server storage. Confirmed media, captions and required Page information are sent to Meta. Configured source services receive the requests needed for enabled source workflows.

The separate Windows application retains its own working media and operational records. Its saved Page credentials use Windows Credential Manager. Cloud deletion does not automatically remove desktop data.

Daily cloud database backups are kept privately on the same server for up to seven days; these do not include uploaded media and are not protection against loss of that server. Earlier migration or maintenance copies may also need operator review when handling deletion. Network and platform processing may take place outside Malaysia.

Service providers operate under their own policies: Cloudflare, Alibaba Cloud and Meta. This public website has no embedded third-party media or remotely loaded fonts.

6. Retention and protection

Cloud Studio keeps imported working videos, creator rules, source identifiers, captions, publishing history and duplicate-protection records until account data deletion. Removing a row from a working list does not erase those records. Incomplete uploads expire after 24 hours. Page credentials expire in the service after 24 hours and require renewed authorisation; browser sessions expire after one hour or a service restart.

Account security events are kept for 90 days. Account summaries remain while the account is retained. Diagnostic logs rotate by size rather than by age and may retain events beyond 90 days. Page reporting history can remain after disconnection until report or Facebook account-data deletion. Private report exports and backups require separate handling; restored data must respect later deletion requests.

App account records and security events are separate from the Facebook data-deletion control. Contact the studio about those records or any retained desktop, export, correspondence or recovery copies. Local desktop data is reviewed and removed by authorised operators rather than having one automatic expiry for all records.

Access controls, password hashing and encrypted credential storage protect the service. They do not guarantee absolute security. Further cloud-specific details are in the application privacy notice.

7. Requests and choices

You may request access to information relating to you, correction or deletion, or raise a privacy concern through the contact below. We may ask for limited information to establish your authority over the affected account or Page. Do not send passwords or access tokens.

You can revoke the app’s access through Facebook. Disconnecting or revoking access does not by itself erase retained records or posts already published on Facebook. Follow our data deletion instructions for the appropriate account or record.

8. Changes and contact

We update this page when our services or data practices change. The revision date is shown above.