Account and email verification

Account & Verification

Last updated: September 17, 2026

This guide explains SourceBoard account creation, email verification, authentication, account security, and identity-related status.

1. Creating an account

SourceBoard may require:

• a valid username;
• account authentication;
• an email address;
• security verification; and
• agreement to the Terms and policies.

Registration may be protected by anti-abuse or human-verification checks.

2. Sign-in methods

SourceBoard may support one or more sign-in methods, including:

• email and password;
• third-party sign-in providers; or
• other supported authentication methods.

Available methods may change.

3. Email verification

Email verification confirms control of an email address.

It does not prove a person's legal identity, employment, profession, age, public status, or authority to speak for an organization.

4. Third-party authentication

If you sign in using a third-party provider, SourceBoard may rely on that provider to authenticate the account.

The provider may have separate rules and privacy practices.

5. Account verification is different from source verification

Account or email verification should not be confused with Verified Source.

• Account/email verification concerns access to or control of an account.
• Verified Source concerns evidence and provenance for a source.

One does not imply the other.

6. Username and identity

A SourceBoard username is not automatically a verified real-world identity.

Users should not assume that an account represents a person, company, journalist, creator, or institution unless SourceBoard clearly provides and explains an applicable verification mechanism.

7. Security

Users should:

• use strong authentication;
• avoid reusing passwords;
• keep recovery methods secure;
• sign out from shared devices;
• report suspected compromise; and
• avoid sharing authentication links, codes, or tokens.

8. Suspicious activity

SourceBoard may require reauthentication, invalidate sessions, limit features, or request additional verification when account activity appears suspicious.

9. Account recovery

Recovery options may depend on the authentication method originally used.

Users should follow the current recovery flow rather than relying on outdated links or previously generated recovery requests.

10. Session management

Signing out ends the current session.

SourceBoard may also terminate sessions when:

• a password changes;
• a security event occurs;
• an account is suspended or banned;
• a user requests broader sign-out; or
• another account-security action requires it.

11. Deleted or anonymized accounts

A deleted or anonymized account may no longer be able to sign in.

Some historical contributions may remain in anonymized or integrity-preserving form where appropriate.

12. Support

If account verification or sign-in does not work, contact SourceBoard through its official support channels and provide only the information reasonably necessary to identify the issue.