Anonymous UUIDs & Metadata

Guide Updated: August 30, 2025

SkiveCore minimizes personal data by using anonymous UUIDs (random identifiers) and collecting only the minimum metadata needed to operate the service securely. This page explains what those IDs are, how we use them, and what metadata is and isn’t collected.

What Is an Anonymous UUID?

A UUID is a 128‑bit random identifier (like 550e8400‑e29b‑41d4‑a716‑446655440000). In SkiveCore, “anonymous” means:

  • It is not derived from your name, email, phone, device serial, or other personal attributes.
  • It is used as a pseudonymous reference to route requests or associate temporary state.
  • It is separate from your login credentials and can be rotated or expired without exposing your identity.

Where We Use Anonymous UUIDs

  • Sessions and requests: Identifying a browser/app session or request flow without storing personal data in the ID.
  • Internal routing: Linking actions that belong together (e.g., retries, background jobs) while avoiding personal identifiers.
  • Diagnostics: Grouping related error events to fix issues faster without tying them back to a real‑world identity.

These UUIDs help the platform function while reducing personal data exposure.

Rotation & Expiration

We prefer ephemeral, rotating identifiers wherever feasible. Rotation limits how long any single UUID can be used to correlate events. When a UUID is rotated or expires, new actions use a fresh ID.

What Metadata We Handle

Metadata is information about an action—not its private contents. Typical examples include:

  • Timestamps (when a request happened or a message was delivered).
  • Technical context like HTTP method, status codes, and non‑identifying error details.
  • Operational IPs seen by servers in standard logs for security and abuse prevention.
  • Size and type indicators for files/media to route and store them correctly.

For private chats, message contents are protected by end‑to‑end encryption and remain unreadable to SkiveCore.

What We Don’t Use Metadata For

  • Behavioral ad profiling: We don’t build cross‑site advertising profiles.
  • Selling data: We don’t sell your personal data or message contents.
  • Covert identity linkage: We avoid combining metadata with personal identifiers unless strictly required for account security or legal compliance.

See also: What We Don’t Track.

Important Limitations

  • Metadata exists: Networks and servers need some metadata (e.g., time, IP, status) to function and defend against abuse.
  • E2EE scope: End‑to‑end encryption hides message contents, not all metadata like who contacted whom or when. We minimize what we retain.
  • Early access: During early testing, we keep collection narrow and focus on reliability and security. Details may evolve before public launch.

Learn More & Contact

Questions? Email support@skivecore.com.