Skip to content
English
Product / Settings

Clear settings, from your profile to your services.

See what belongs to you, what belongs to your project, and which services need attention.

Clear account paths. Explicit access.

Personal account settings, local project permissions and customer membership serve different jobs. Explore each path in the existing browser examples.

Browser examples only. No real account or service is connected. Kottoko organization accounts and deployed-project accounts are distinct.

Read-only guide

Manage a personal account

Read-only guide to the existing project-local account examples. Selecting a path does not sign you in.

  1. Verification follows the saved email

    Save an invented profile, inspect verification and recover from a failed sample check. Changing the saved email requires a new check.

  2. Choose supported account protection

    Inspect authenticator confirmation and passkey availability. A real account needs recent identity confirmation and compatible features and devices.

  3. Keep recovery private

    Inspect the recovery explanation without generating codes. Real recovery codes are private; replacing them invalidates the previous set.

  4. Review current and other sessions

    Inspect sample sessions and confirm removal of another sample session. The current sample stays active.

  5. Keep personal choices separate

    Try saved and unsaved communication choices. Sample appearance does not change project design; website language and browser consent remain separate.

  6. Review export and removal

    Preview saved sample data and a cancellable removal request. Owner safeguards and retained-record explanations remain visible.

How sign-in and recovery work

Installed Accounts supports registration, email verification, sign-in and password reset. Follow that project’s recovery flow if you cannot sign in. This public guide asks for no password, sends no email and does not authenticate you.

The examples are unavailable while this browser draft is loading or blocked. Your saved choices are kept.

The member destination is unavailable in this context. No account or access changes.

When access needs attention

A denied permission and an expired session need different recovery. In a real project, sign in again for an expired session, or ask its authorized owner about access. A verification failure does not grant more rights.

Organization access is separate

Kottoko organization roles, Creator seats and commercial entitlements are distinct from local project permissions and customer membership.

An organization role describes a responsibility. Creator-seat assignment is separate; payment alone does not assign a role or local permission. Billing access does not imply source access.

A deployed project controls its own users, content and access. Production content, submissions, secrets and local user directories are not synchronized to the organization service. There is no hidden support account.

Transactional email

Understand the email behind an action

Inspect the message, its source and the setup it needs.

Examples unavailable in this context

Verification example unavailable

The Profile example cannot be opened in this context. Your saved examples are kept.

Illustrative preview, not an installed message template. No email is sent.

What supplies this preview

The Profile example owns its verification state. This specimen explains the request without reading an email address or changing that state.

These browser records are not an email queue, attempt history or provider delivery event.

Unavailable actions stay off. Existing choices and sample records are kept; use the existing Settings controls when they are available again.

Example project

No live service connected
Illustrative only

Project settings

See what the project can do now and what needs setup.

Form responses

Responses are saved in this project.

Built in
Email notifications

Responses are saved. Set up email to send notifications.

Not configured
Project design and content

Edit supported page content and design in the website editor. Project identity and service setup belong to the owned project.

Explore the editor

Access and responsibility

Keep project access separate

Understand who can create projects, manage local access and maintain a delivered project.

Read-only guide and browser examples. No live organization, Creator seat, certificate or handover is connected here.

  1. Kottoko organization

    Organization membership covers commercial responsibilities and creation rights. It is separate from a delivered project’s people and customer member spaces.

    Roles, Creator seats and licensing
    Owner
    Manages the organization, administrative roles and ownership. Keep at least one Owner. A seat is needed only when also acting as a Creator.
    Billing administrator
    Manages purchases, payment methods and invoices. Billing access does not grant source, Pantry or local project access.
    License administrator
    Manages membership, Creator seats, project certificates and handovers. This does not grant billing authority.
    Creator
    Uses the reusable Pantry and creates projects only when the Creator role, an active seat and commercial entitlement permit it.
    Viewer/Auditor
    Reads organization, entitlement, project-registry and audit information without administrative authority.

    Roles are additive. Creator-seat assignment is a separate record. Payment alone assigns neither a role nor a local permission. Clients operating one delivered project do not consume Creator seats.

    A signed project certificate or project-scoped maintenance grant connects entitlement to the delivered project. This example has neither a certificate nor a grant to issue or download.

    Production content, form submissions, secrets, customer lists and local user directories are not synchronized to the organization service.

    Existing local and deployed projects have no continuous license-server requirement or remote kill switch. Revoking future account or download access cannot erase source already retained offline; that source remains governed by its license.

    Organization pricing, legal terms, sales and release approval remain separate. This guide does not offer seats or establish license eligibility.

    This destination is unavailable in the current example. The reference explanation remains readable.

  2. Local project people

    The deployed project owns its people, roles and explicit permissions. Organization membership or a purchase does not automatically change this access.

    Editing content, publishing, designing forms, reading submissions and restoring backups are separate permissions. Inspect the existing sample rather than assuming a role allows everything.

    The local-access example is unavailable here. No saved project or permissions are shown.

    This destination is unavailable in the current example. The reference explanation remains readable.

  3. Customer member space

    A project’s member space contains protected resources, courses or discussions for its members. Its plans, entitlements and assignments are separate from Kottoko organization membership and local operator permissions.

    This destination is unavailable in the current example. The reference explanation remains readable.

Who maintains the delivered project

Agree on responsibilities, then enforce each person’s permissions in the project. Reading a maintenance mode here does not change access.

Agency managed
The agency retains technical responsibility and assigns the client selected content and presentation permissions.
Shared maintenance
Agency and client responsibilities are explicitly assigned. Update assessment, approval, application and recovery remain separate permissions.
Client maintained
The client becomes the local Project Owner, appoints a Technical Maintainer and may remove the agency. A handover requires an explicit local acceptance flow.

An invited Project Steward grant may provide eligible updates, release notes and maintenance guidance for one paid delivered project. It grants no Creator seat, organization administration, unrelated project creation or general reusable Pantry access.

A central handover package does not remotely change the deployed project. An authorized local Project Owner must accept and apply it through the project’s recovery-aware process.

Client maintained handover and invited Project Steward access belong to the intended first public release. They are unavailable in this browser example, and do not open organization sales or release gates.

Agency access is a visible local account that an authorized Project Owner can revoke. At least one active Project Owner must remain. Sensitive changes require the project’s authority and confirmation safeguards. Kottoko has no hidden support account or remote super-administrator.

This destination is unavailable in the current example. The reference explanation remains readable.

Invented project details and local accounts. All changes stay in this browser example.

Project detailsTry changing displayed project content, then save or restore it.
More supported details

Use invented contact details only, such as an address ending in .test. Label and value must be entered together.

Saving displayed content does not rename the installed project identity, slug, domain or hosting.

People and accessPreview a sample role change and a separate submission-reading permission.

Project Owner · [email protected]

[email protected]
Saved sample permissions
  • Edit contentAllowedRole preset
  • Publish contentNot allowedRole preset
  • Design formsNot allowedRole preset
  • Read form submissionsNot allowedRole preset
  • Restore backupsNot allowedRole preset
Inspect owner safeguards
  • An owner cannot change their own access here.
  • Keep at least one active Project Owner before removing or changing another owner.
  • Only an active Project Owner with access-management authority can change access.
  • An owner cannot delegate permissions they do not have.
  • Revoked access cannot be reactivated through this change.

Installed access links an existing verified local account. This example sends no invitation and adds no account.

Local project access is separate from Kottoko organization roles, Creator seats and commercial entitlements.

Privacy choices have different scopes

Website choices, sample account data and project policies have their own controls.

Account and project examples stay in this browser. The website Privacy preferences page manages your real optional browser choice.

Visitor choices

Review whether this website remembers optional preferences. Analytics and marketing tracking are unavailable here; the project sample has separate controls.

Your account

Inspect existing sample choices, saved-data export boundaries and cancellable removal safeguards. Required account notices are separate from optional updates. These sample choices do not set website consent.

Project rules

Inspect the current tracking revision and feature-specific retention review. Opening a control changes no policy, permission or approval.

Current project example

These facts come directly from the existing Project privacy sample. Inspect its controls below to explore changes and recovery.

What a data request includes

Handle a request in the feature that owns the data. Built-in analytics exports aggregates, not an individual profile. Forms response values and separately retained lifecycle evidence have different policies.

An installed account requires fresh authentication for export and removal. Newsletter export or minimization uses expiring identity proof. Project access alone does not prove someone else’s identity; this example verifies nobody and sends no request.

The account preview uses saved sample profile and communication choices, not unsaved edits or website cookie choices. Installed exports exclude passwords, recovery secrets, session identifiers, passkey credentials, provider secrets and other people’s data.

The account example has a fixed seven-day wait, separate confirmation and cancellation before completion. Being the last administrator or organization owner can block completion. No account or other example is removed.

Removal does not promise to erase all project records. Shared content, media and purpose-bound evidence may remain. The project owner reviews installed collection purposes, retention, processors and final legal text.

Some privacy actions are unavailable

Unavailable actions stay off. Existing choices and sample records are kept; use the existing Settings controls when they are available again.

Tracking and marketing

Inspect an external analytics sample, its review and visitor consent. No script is loaded and no activity is collected.

Sample project: Example project
External analytics sample

Google Analytics 4 — page views only

A supported external preset, separate from built-in aggregate reports. Advertising signals are denied; privacy and provider terms need owner review.
Purpose
Measure page views on declared public content pages.
Optional analytics consent
No consent choice
Placement

Page head — fixed by the preset

Public content pages only. Account, editor and payment-return pages are excluded. Installed projects also validate language, environment and load timing.

Saved sample, not reviewed. Saved sample revision: 1.

No sample revision enabled.

Review and recovery examples

History is preserved. Using a previous revision requires a fresh review before enabling it again.

Custom code is restricted in installed projects: isolated execution, no host page access, cookies, storage or direct network. This example has no code editor or execution.

Marketing tracking unavailable

Marketing consent and remarketing presets remain unavailable. There is no marketing enable action.

Data and retention

Review collection purposes and feature-specific retention. Preview fixed sample impact and inspect safeguards without removing records.

Sample project: Example project

Forms receive declared participant responses. Submission retention defaults to 90 days, configurable from 30 to 365 days after project-owner review.

Lifecycle evidence has a separate 365-day default and requires owner and legal review. Removing response values does not remove every evidence record.

Sample policy needs review. Installed owners must validate purposes, retention, processors and legal text before release.

Inspect sample safeguardsThis readiness example follows the Forms removal safeguards. Other features use their own lifecycle and authority.
Individual data requests

Handle requests in the feature that owns the data. Account export needs fresh authentication; newsletter export or minimization needs expiring identity proof. Project access alone does not prove someone else’s identity.

Illustrative subject: [email protected]. No request is sent and no identity is verified here.

Personal settings

Profile, sign-in security, appearance, and account data belong to each person, separately from project settings.

Privacy and tracking

Built-in aggregate reports and external tracking have different purposes and consent choices.

See analytics choicesKottoko site privacy choices

Team access and credentials

An authorized project owner manages local roles and service credentials. Kottoko.com does not receive the deployed project’s users or secrets.

All example states on this page are illustrative. No project settings, provider connections, permissions, or credentials change here.