Account · Updated 2026-08-25

Google sign-in, sessions, and safe return paths

Learn how Google sign-in protects private projects, how sessions work, and which public pages remain available without an account.

Quick answer

Understand the boundary before taking action.

Public product and learning pages are readable without an account. Creating or opening a private project requires Google sign-in, and the sign-in flow carries only a validated return location—not an anonymous creative brief.

  1. 01Public reading stays public
  2. 02Google authenticates the account
  3. 03Return paths are validated
  4. 04Session state updates public navigation

Public reading stays public

Features, Use Cases, Prompts, Guides, comparisons, sizes, pricing, and Help pages can be explored without sign-in. Opening Home, Projects, Assets, Brands, Activity, or a project enters the private product surface.

Google authenticates the account

Retake requests basic OpenID identity scopes for name, email, and profile. Google handles the account credentials and consent screen; your Google password is never shared with Retake Design.

Return paths are validated

After sign-in, you return to a supported Retake page such as Home or a selected Result Skill. External destinations are rejected. Your creative brief is not sent through Google sign-in.

Session state updates public navigation

When the public site and product share the same origin, the Header checks the current Session. Signed-in visitors see their workspace action instead of another Sign in prompt. Signing out returns the Header to its anonymous state.

FAQ

Common questions about this path.

Why can I read a Prompt page without signing in?

Prompt pages are public learning resources. Sign-in is required only when you open the private workspace or create a project.

Does Retake carry my unfinished brief through Google sign-in?

No. The OAuth flow carries a validated return location, not anonymous creative input.