Skip to content

Link the Terms of Use and Privacy Policy from TBv3, the Mapper, TBv2 and the sign-up screen #2844

Closed
2 of 2 issues completed

Description

@paynejd

Using the apps means accepting the Terms of Use, but none of the apps links them: a search of oclweb3, oclmap and oclweb2 on 09-28 found no link to the Terms or the Privacy Policy. This is the remaining half of making the Terms available in TBv3.

Split on 2026-10-13 so each app's change can be worked on its own. TBv3 and the Mapper have their own tickets; TBv2 and the SSO sign-up screen stay here.

Acceptance criteria

Activity

  1. added this to the P2 · TBv3: Beta milestone on Sep 29, 2026
  2. ocl-automation commented on Sep 29, 2026

    @ocl-automation
    Collaborator

    Automated Triage — 2026-09-29

    Dimension Score
    Complexity 2
    Scope 4
    Clarity 4
    Dependency 2
    Risk 2

    Decision: decision/planning-needed
    Type: type/feature
    Signals: signal/quick-win, signal/low-risk, signal/large-scope, signal/well-specified

    The change is simple (add two links) but spans four separate codebases (oclweb3, oclmap, oclweb2 and the Keycloak login theme), so scope is 4. Acceptance criteria are explicit and the canonical URLs are named; the gap is that the exact footer or user-menu placement and the Keycloak theme deployment path are unspecified. Risk is low, since a missing or wrong link is easy to revert, though the legal pages should be checked.


    Generated by ticket-triage pipeline v3. Model: anthropic/claude-sonnet-5.5 (openrouter).

  3. self-assigned this
    on Oct 2, 2026
  4. added a commit that references this issue on Oct 13, 2026
  5. paynejd commented on Oct 13, 2026

    @paynejd
    MemberAuthor

    Both remaining pieces are up for review:

    Both were checked in a browser in every language at desktop and phone widths. The Codex review and the simplification review are on each PR.

    To finish: merge both. oclsso has no CI, so the sign-up line goes live only once the SSO image is rebuilt and redeployed after the merge. TBv2 ships with its next deploy. TBv3 (#2899) and the Mapper (#2900) are still on their own draft PRs.

  6. added 3 commits that reference this issue on Oct 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

component/webTermBrowser frontendsignal/large-scopeAffects multiple areas or systemssignal/low-riskSafe to execute with minimal downsidesignal/quick-winLow complexity, high clarity — easy winsignal/well-specifiedClear requirements and acceptance criteriastage/triagedAI triage complete — scored and classifiedtype/featureNew or improved functionality

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions