Skip to main content
Your TLDT account owns one Profile. That Profile is the authority boundary for Career Memory, published versions, preparation sessions, public activity, shares, integrations, and lifecycle actions.

​
Sign in and Profile ownership

Use an email Magic Link/OTP or Google on the TLDT sign-in page. A successful sign-in provisions the owner Profile and lets you claim one public username. Owner pages under /admin require authentication. A published username page and an active saved-share link are public to anyone who opens them. Public visitors can use only the active published projection for the username or the visitor-safe snapshot addressed by the share token. They cannot choose another Profile id, storage path, or private source.

​
Privacy boundary

Public serialization excludes:
  • Private Memory and editable drafts;
  • source paths and internal citations;
  • prompts, policy reasons, and tool traces;
  • provider metadata and credentials;
  • tenant identifiers and internal storage authority.
Fast Check reports, simulations, and AI answers still need human judgment. Confirm important professional, legal, scheduling, and hiring decisions directly with the relevant people.

​
Export and deletion

Owner export and account deletion are protected lifecycle actions. Account deletion immediately unpublishes the Profile, revokes active shares, and schedules cleanup of Profile-bound data. The current maintenance flow can clean up Storage objects, but a downloadable export archive and complete Auth/database deletion may depend on the hosted lifecycle worker finishing its job. Treat the owner UI status as the current lifecycle state, not proof that every background step has completed.
Before deletion, copy any information you need and verify the exact account. Deleting an account is separate from hiding the public profile, revoking one share, or deleting one session.