The site now publishes the Terms of Service and Privacy Policy for Segredo de Arquivo, the TikTok auto-upload service on the forthcoming channel @segredodearquivo. Both pages follow the Editor drafts from Board facts only, reuse the established page pattern, carry footer links, and appear in the sitemap with canonical and social tags from the shared renderer. Board action required before publish: the contact line on both pages is a clearly-marked placeholder the Board must replace with the canonical contact.
Motivation
The TikTok app review needs public English Terms and Privacy addresses for the Segredo de Arquivo auto-upload service: what the service is, acceptable use, TikTok Terms and Community Guidelines compliance, what data the service handles and why, and where each promise lives. The assigned record asks for exactly two pages with footer entry points and search-engine listings, readable without scripts and free of outside requests. Shipping both pages together with this log entry keeps the change traceable under the standing rule.
What changed
Two new addresses now render as full pages: the Terms of Service and the Privacy Policy for Segredo de Arquivo. The footer navigation gains matching links while the header stays exactly as it was. Both pages join the sitemap, and each carries its own canonical address plus social tags from the shared page renderer. The copy follows the Editor drafts verbatim (service description, acceptable use, TikTok compliance, as-is service, liability limit, OAuth tokens and handle and video files and minimal logs for authentication and upload only, encrypted storage, retention, no sale except the TikTok API, user rights, dated policy), with the channel kept as unlinked forthcoming plain text and the contact line held as a Board-replacement placeholder.
How it was done
After the hosting preflight and a fresh feature branch from the main line, development added two static templates following the existing information page, wired them through the deterministic builder with no new dependencies, and extended the footer and the sitemap list only. The body reuses the linear article-body pattern with no sidebar, so it reads with scripts disabled and makes zero outside requests. The page copy tracks the Editor drafts from Board facts only; the one deliberate deviation from the first draft is the contact line, held as a loudly-flagged placeholder until the Board supplies the canonical contact. This log entry ships in the same change per the standing rule.
Verification evidence
The site build exits success, the full suite is green, a second consecutive build is byte-identical, and the presence gate prints success with this entry covering the change. The built footer links to both pages from every page, the sitemap lists both addresses, each page carries its canonical tag and social tags, and a scan of the diff finds no secrets. Security and quality reviews attach to the exact pushed head after this pull request opens.
How this entry was built.
Built in the same change it describes; each step traces to a real branch and commit.
- Development verified the remote and login, then branched from the fresh main line.
- Development added the two page templates with footer links and sitemap coverage.
- Unit tests, presence gate and deterministic rebuild green; entry shipped in the same change.
Pipeline.
Each stage ran in order; blocked stages looped back through fix and re-review.
the pull request · merge pending · the branch
- done — Hosting preflight and branchDEV · — Verified the remote and login, then branched from the fresh main line.
- done — Legal pagesDEV · — Added the two static pages with footer links and sitemap coverage.
- done — Pull requestDEV · — Opened the pull request with the pages and the log entry.
Verdict trail.
| Stage | Agent | Verdict | SHA | Why |
|---|---|---|---|---|
| Hosting preflight and branch | DEV | done | commit | Verified the remote and login, then branched from the fresh main line. |
| Legal pages | DEV | done | commit | Added the two static pages with footer links and sitemap coverage. |
| Pull request | DEV | done | commit | Opened the pull request with the pages and the log entry. |
Why each step ran.
- DEV
- The two pages reuse the established static page pattern with no new components, scripts, or styles, using a linear article body with no sidebar per the design clearance. The body copy tracks the Editor drafts from Board facts only, with the forthcoming channel kept as unlinked plain text and the contact line held as a Board-replacement placeholder that must be replaced before publish. The footer carries the new links while the header stays unchanged, and the sitemap plus per-page canonical and social tags come from the shared renderer. The deterministic build and the full test suite pass on the change.
- SEC
- Not evidenced in the linked record. The security verdict for the reviewed head is recorded in the review child issue.
- QA
- Not evidenced in the linked record. The quality verdict for the reviewed head is recorded in the review child issue.
- Director
- This change adds the two required legal pages through the existing page system with no visual or structural change elsewhere. Security and quality reviews are pinned to the exact pull-request head in parallel child issues. Release approval fires only when both verdicts pass that exact head.
Receipts.
●●●