One-Click to Hide Platform Traces: Make Your Site More "Pure," and the Boundaries I Must Honestly Discuss

Hide Platform Traces

The brand has changed, the domain is bound, and the price is set. The final step is to hide those "exposing it as Ace Data Cloud" little tails—making your site look more like an independent product.

In this article, I will discuss two things: what can be hidden with one click and how to hide it; and—equally important—what still cannot be hidden. I don't want you to go to clients with the expectation of a "completely trace-free" promise, only to be slapped in the face by some corner.

Customizable / Hidable Parts (More Than You Think)

Auth Bar: Select Login Methods (Email/Google/GitHub/Apple/Phone/WeChat), Default Method, Login Form, Custom SMS Signature

In the settings pop-up, there are now quite a few places you can change to "yours," let's go through them one by one:

  • Logo / Site Name / Theme Color (Site Settings) — the overall face of the site;
  • The name and icon of each app (Capabilities → Customize app) — replace "Midjourney" and "Suno" with your own named capabilities;
  • Your own domain (Custom Domain) — CNAME + free automatic HTTPS, the address bar directly changes to ai.yourbrand.com, this is now fully supported;
  • Login Methods + SMS Signature (Auth, see above image) — you can keep only the login methods that your target audience will use (WeChat / phone number / Google / Apple...), and more importantly, you can customize the SMS signature: the verification code SMS received by users when logging in with a phone number will have your brand as the signature, not the platform's. This step particularly enhances "hiding platform traces," which many people are unaware of.

Once you change these, users will primarily see your brand during normal browsing, chatting, generating, ordering, and logging in.

The operations are quite simple; just find the corresponding settings to change. The key is not "how to click," but to verify after the changes—see below.

⚠️ I Must Honestly Tell You: Currently, 100% Trace-Free is Not Achievable

This is something I must clarify.

Our goal is to make users completely unaware that this is Ace Data Cloud, and most obvious traces can indeed be changed (brand, icon, your own domain, SMS signature). However, the current situation is: it is not yet seamless. A few places still have minor traces pointing to the platform, mainly in these areas:

  • Login Process: Currently still using the auth.acedata.cloud domain—brand, login methods, and SMS signatures can be changed, but when users click to log in, the browser address bar will briefly show auth.acedata.cloud.
  • Certain Payment / Download Processes: A few nodes still have minor traces pointing to the platform, and we are cleaning them up one by one.
  • API Domain Names and CDN Resource Domain Names for Developers: Temporarily still the platform's, cannot be changed to your own.

I list these out because I would rather you know in advance than have you overpromise to clients. The current situation is: sufficiently resembles your own site, but not 100% trace-free. We are continuously working on this, and it will become cleaner—once any part is cleared, I will update this article.

After Closing, Conduct a "Spot Check" Acceptance

Open a trace-free window, use the perspective of a stranger, and specifically go to spot check—walk through the entire main process and look for any exposed areas:

  1. Homepage / Chat / Generation Page—does the footer still have "Powered by"? Are there links leading to the platform?
  2. Click to log in—does your brand appear? (The appearance of auth.acedata.cloud in the domain bar is the current known boundary, just keep it in mind)
  3. Go through the ordering and payment process—does any platform wording pop up during the process?
  4. Generate and download a file—are the download links clean?

Turn off anything you find that can be hidden but you haven't closed; for those belonging to the known boundaries above, keep it in mind, and don't promise clients that "it can't be seen at all."

Mentally, I Want to Give You a Piece of Advice

Don't get stuck at this step, hesitating to go live in pursuit of "100% trace-free."

To be honest: the vast majority of your end users will not go looking in every corner to find out whose it is. What they care about is "how good this AI is, whether it's worth the price, and if anyone is managing me." Making the parts that users will truly perceive—brand, appearance, customer service, pricing—solid is much more important than pursuing the last 1% in some hidden corner.

The trace-free aspect, leave it to us to continue pushing forward. What you should do is hurry up and push it to your users.

At this point, the "Build → Brand → Domain → Pricing → Hide Traces" process for white-label sites is complete. The final article, "Make Every Visitor Yours," will clarify the ownership aspect: how to ensure that people coming to your site, after registering, are truly bound as your users, and their consumption counts as yours. This is a key step in turning "traffic" into "your assets."