Flows

Notice delivery vs acceptance

The product app must persist these records in its own database. This page demonstrates the correct UX pattern on the marketing site — it is not a fake completion of in-app compliance.

Back to legal hub

Join flow — notice ≠ consent

Demo of the required separation: privacy notice delivery is logged without being optional consent. Participation confirmations are separate. Optional processing is never preselected.

View Privacy Notice View Community Rules View Security Information Report Invitation

Privacy notice (information)

The Secret Community Privacy Notice is shown for information. Viewing it is logged. This is not a consent checkbox for “all processing”.

I have been shown the Privacy Notice (delivery logged — not optional consent).

Participation confirmationsI have reviewed the Secret Community Rules and agree to comply with them.I understand that I must not share passwords or verification codes.I understand that other members may copy or redistribute content I share.

Rules version: sc-rules-aup@1.0.0

Incorrect pattern (disabled): “I consent to all processing in the Privacy Notice.”

Continue stays disabled until notice delivery and the three required confirmations are checked.

Creator flow — verification notices

Phone and voice-call notices are shown first. Calls are not recorded by default. Optional recording consent is never preselected and must not block creation.

Open phone notice Open voice notice Open creator terms

Creator confirmationsTelephone verification notice shown sc-phone-verification@1.0.0Voice-call verification notice shown (no default recording) sc-voice-call-verification@1.0.0I accept the creator responsibilities (versioned) sc-creator-terms@1.0.0Optional: verification-call recording (future; not preselected)

Creator flow additionally requires phone-verification notice, voice-call notice (no default recording), and versioned acceptance of creator responsibilities. · sc-security-notice@1.0.0