Write your community's own terms of service and privacy policy, and link your cookie policy. Members see them when they sign up and at the bottom of every page. The same page sets a minimum age for new members.
Who can do this: Community owners and admins. · Where: Web (admin console). Members see your documents on the web and when they sign up in the Mateflow app. The minimum age applies in the app too. · Plan: Available on every platform plan.
Write your terms of service and privacy policy
- Go to Admin → Settings → Legal. The page is called Legal & Compliance.
- Under Legal Documents, find Terms of Service or Privacy Policy and click Start writing, or Edit if it already has text.
- Write the document in the editor, then click Done. A document that's too long can't be saved.
- Click Save Changes at the bottom of the page to publish your changes.
Until you write a document, its row says "Not written yet. Members only see Mateflow's Terms of Service." (or Privacy Policy). After you save, View page opens the published document. You're responsible for what your documents say; Mateflow only hosts them.
Saving doesn't notify existing members or ask them to agree again. To see earlier text, click Version history on the document. Versions are kept from the time this feature was added; anything older can't be recovered.
Links to terms or a privacy policy on your own website, set here earlier, are no longer used. Paste the text instead.
Link your cookie policy
Under Cookie Policy URL, enter the address of your cookie policy, starting with https:// or /, then click Save Changes. While the field is blank, it shows "Leave blank to use the platform default:" followed by the Mateflow page that members see instead.
Where members see your terms and privacy policy
On the web, members find your documents in these places:
- Your community's pages:
/termsand/privacyon your community's address, for exampleyour-community.mate.so/terms. Each shows when it was last updated and notes that Mateflow's terms also apply. Visitors can open them even in a private community. - Footer: Terms, Privacy, and Cookies always appear in the footer area, even when Show copyright and social icons is off. See Customize navigation, links, and footer.
- Sign-in and sign-up pages: "By continuing, you agree to {your community}'s Terms of Service and acknowledge its Privacy Policy." Below it, "The platform terms and privacy notice also apply." opens Platform terms and privacy, with Mateflow's Terms of Service and Privacy Policy. The links open in a new tab.
- Cookie banner, if your community shows one: Learn more opens your cookie policy.
Mateflow's Terms of Service and Privacy Policy apply alongside yours. The sign-in line links your own documents, and Mateflow's stay one click away. If you've written only one document, the line uses Mateflow's for the other, for example "By continuing, you agree to {your community}'s Terms of Service and acknowledge Mateflow's Privacy Policy." Until you write either, the line lists only Mateflow's: "By continuing, you agree to Mateflow's Terms of Service and acknowledge its Privacy Policy." The footer link and /terms or /privacy then open Mateflow's page in the member's display language, as a blank Cookie Policy URL does. If your platform plan removes Mateflow branding, these places say "the platform provider" instead of Mateflow.
In the Mateflow app, the sign-up form shows the same line and the same link to the platform terms, and your documents open inside the app. The app's welcome and sign-in screens list only Mateflow's Terms of Service and Privacy Policy.
The cookie consent banner
A community shows a cookie banner only if you've set a Google Analytics or Meta Pixel ID (see the next section). Without one, there are no optional cookies to ask about, so no banner appears, and the Cookies link stays in the footer.
With an ID set, the first time someone opens your community on the web, the banner says: "We use necessary cookies to run this community. With your consent we may also use optional cookies." The visitor clicks Necessary only or Accept all, and Mateflow remembers the choice. Cookie preferences in the footer lets them change it.
You can't change the banner's text. You only set where Learn more goes, with Cookie Policy URL.
Add Google Analytics or a Meta Pixel
To measure visits and conversions, add your IDs on the same page, then click Save Changes:
- Google Analytics 4 Measurement ID: an ID like G-XXXXXXXXXX. Google Tag Manager containers aren't supported.
- Meta Pixel ID: the 6 to 20 digit ID from Meta Events Manager.
These are optional and available on every platform plan. They load only for visitors who accept analytics cookies, and never in the admin console. A visitor who changes their mind stops being tracked. Say that you use them in your privacy policy.
Set a minimum age for new members
Under Age & minor protection, you decide how old new members must be and how sign-up checks it (GDPR Article 8 protection of minors).
- In Minimum registration age, enter the age in years. It's 16 unless you change it. Enter 0 to stop asking about age at sign-up.
- Choose how the age is checked with Require date of birth (unavailable when the age is 0):
- Off: the email sign-up form shows the checkbox "I confirm that I am at least 16 years old." (with your age). People must tick it to create an account. For social login, sign-up on the web and in the app shows "By continuing with a social account you confirm that you are at least 16 years old." under the buttons instead.
- On: sign-up asks for the Month and year of birth, or a Date of birth in the Mateflow app. People younger than your minimum age see "You must be at least 16 years old to join." and can't register.
- Click Save Changes.
Regulators such as US COPPA and the UK Online Safety Act don't accept a checkbox as age assurance.
The age check applies to email sign-up, including paid sign-up, where it runs before payment, on the web and in the Mateflow app. With Require date of birth on, people who sign up with social login aren't asked for their date of birth; to put everyone through that check, turn off social login. See Set up social login. Members who join through single sign-on (SSO) aren't covered, because their identity provider manages those accounts.
Members can see what was recorded about their age when they joined, but can't change it.
Handle members' data requests (GDPR)
Members can download their own data and delete their account themselves. See Export your data or delete your account.
When a member asks you instead, use Data subject requests on the Legal page: click Manage members, open the member's page, and choose from the actions menu:
- Export data (GDPR): queues a full export of the member's data.
- Anonymize member: scrubs the member's name, email, and avatar. It can't be undone. The community owner can't be anonymized.
The member's page also shows their Consent records under Data & Privacy: what they agreed to or withdrew, and when, with the version of your terms or privacy policy.
Related articles
Was this guide helpful?