Set up as a solo creator

Everything a solo creator needs, in the order it needs doing. Set aside twenty minutes and you are finished.

1. Verify yourself#

Solo creators verify directly: no invite flow, no third-party session. Open Solo Content and the verification form is the first thing shown until it is complete.

What it asks for:

• Your legal name and date of birth, exactly as they appear on your ID.
• The front of a government photo ID: a driver's license, passport, or state ID. The back is optional for passports.

A usable image shows the whole document, in focus, with every corner visible. The legal name has to match the document because the record being created is that a specific, identifiable adult made this content. A stage name on your public profile is fine; the verification carries the document's identity.

Where it goes: encrypted storage, kept apart from ordinary account data, with a SHA-256 digest recorded for each image the moment it uploads. That digest is what makes the record verifiable later.

2. Log your content#

A content log entry ties a specific depiction to your verified identity, with a date and the place it was published.

1. 1

   Describe the depiction

   A title you will recognize later, the content type, and when it was made.

2. 2

   Record where it is published

   The published location is part of the record, not a nicety. An inspection works from the published content back to the records behind it, so the URL is the thread that connects the two.

3. 3

   Attach the reference

   The entry stores the content's published URL, an optional thumbnail, and a SHA-256 digest computed in your browser from your local copy of the file. Nothing uploads except the thumbnail. The digest still lets you prove, years later, that the file you hold is the file you logged.

One entry means one piece of content. The same video published in three places is one entry with three published locations, not three entries. Content produced before you started using Easy2257 belongs in the log too: enter it with its real production date, not today's.

Log as you publish rather than in batches. Entries that cluster suspiciously are the first thing a reviewer notices, and an incomplete log reads as exactly that.

3. Publish your statement#

Every place your content appears should carry a notice naming who holds the records. Easy2257 generates yours as a public statement page tied to your account: find it under 2257 Statement, where the link is ready to copy.

Because Easy2257 acts as your Custodian of Records, the address on the page is the platform's, never yours. Your home address does not appear anywhere in the notice. What the custodian role is, and why the law wants a named keeper of records, is explained under The rules in this Help Center.

4. Link it from your platforms#

A statement page does nothing if nobody can reach it from your content.

Every platform gives you at least one field that can carry the link: a bio, an about section, or a website slot. Put the statement URL there. On your own site, the footer is the conventional place.

Two practical notes. Some platforms limit or strip outbound links in bios; a link-in-bio page you control is the reliable carrier in that case. And character limits usually leave room for exactly one short URL, which the statement link has earned.

Finish with a verification pass: open the link signed out, from a phone, and confirm it resolves to your statement.