Security Center

How CreateMe protects accounts, chats, and payments — without overclaiming certifications we do not hold.

v2.0 Neural Protocol

Operational Status

System Status: All Studio Nodes Operational. Our global infrastructure is monitored 24/7 to keep image, video, voice, and assistant workflows available.

Encryption & Protocols

We use AES-256 encryption for stored neural memory and chat data at rest. Access to private logs is restricted; staff do not browse user conversations in day-to-day operations. Transport security uses industry-standard TLS/SSL on createme.pro.

Payments & PCI

Checkout is processed by payment partners (including Midtrans for Indonesian methods). Those partners maintain PCI-DSS compliance for card handling. CreateMe does not store full card numbers on our servers. Accepted channels typically include cards, QRIS, e-wallets, bank transfer, paylater, and retail outlets subject to merchant activation. Learn more about partner security in Midtrans documentation. For refunds, see our Refund Protocol (unused accounts, request within 72 hours).

Sign-in & Sessions

Account access uses Google OAuth 2.0 for sign-in. Free tier users can start without entering a card. Session cookies are transmitted over HTTPS. You can cancel renewing subscriptions from your dashboard at any time.

Core Safeguards

AES-256 storage encryption
TLS / SSL transport
PCI via payment partners
Google OAuth sign-in

Related: Compliance · Refund Protocol · Midtrans security docs

Neural Ethics Framework Compliance

This documentation is part of the **CreateMe AI Transparency Node**. Our legal frameworks are dynamically linked to our operational ethics. In cases of discrepancy, the Master English Protocol remains the primary authority.