Privacy Notices
Create and maintain privacy notices that clearly explain data usage, purposes, individual rights, and available grievance mechanisms.
A privacy notice page holds the regulatory notice text you publish for individuals: what personal data you collect, why you process it, what rights they have, and how to raise a grievance. This is the text a GDPR Article 13 or 14 notice or a DPDPA Section 5 notice requires you to give people, in your own words. A notice page supports multiple languages, a configurable header, and a version history you can always look back on.
Open Privacy Notices > Pages to see every notice page for your tenant, with its name, description, brands, regulations, and tags.
Creating a page
Click Add New and fill in:
| Field | Notes |
|---|---|
| Name | Required. |
| Description | Required. |
| Brands | The brand or brands this notice applies to. |
| Regulations | One or more regulations, for reference and tagging. This does not enforce any particular content or clause on the notice. |
| Tags | Optional. |
Your plan sets how many notice pages you can create. At the limit, Add New is disabled and a tooltip asks you to contact the Neostra team.
Click Page Contents on a page to open its editor.
Regulations are metadata only. Choosing GDPR or DPDPA here helps you and your team find and organise notices; it does not add or check any specific clause in the notice text. You are responsible for the wording that meets each regulation's requirements.
Writing the content
The left sidebar has Language Settings, Contents with one entry per language, Published Versions under History, and Embed Script under Integration.
Language Settings opens a panel where you choose a Default Language and tick which of your tenant's languages the notice offers. The languages available here are your tenant's supported languages, set elsewhere in your account, not a list specific to this notice.
Select a language under Contents to open its editor:
- A Header switch turns the page header on or off. When on, its gear icon opens header settings: a background colour or a background image with an overlay colour and opacity, a heading shown as text or a logo, heading text colour, and header height in pixels.
- Below the header, a rich text editor holds the notice body for the selected language.
Save stores your changes as the current draft, and Preview shows the page as visitors will see it. Every enabled language needs its own content before you can publish, so add or update translations for each language you offer before publishing.
Publish and version history
Click Publish. Neostra checks that every enabled language has content filled in and asks you to confirm. Once published, that content is frozen. Any further edits start a new draft, and only one draft can be open at a time, so publish or discard your current changes before starting another round of edits.
Published Versions lists every publish with its date and a Preview button that opens that version exactly as it was published. Because a published version is frozen, this list becomes your record of what the notice said and when, which is useful if you ever need to show what individuals were told at a given point in time.
Embed or link the notice
Once a page has been published at least once, its Embed Script tab shows an iframe snippet you can place on your website:
<iframe src="https://<your-neostra-host>/public/notices/privacy-notice-pages/<tenant-id>/<page-id>"></iframe>
Before the first publish, this tab shows "You have to publish the privacy notice page first."
The same URL also works as a direct link, and it takes a few query parameters: hideHeader=true to drop the header, hideLanguagesDropdown=true to hide the language picker, and preSelectedLanguage=<code> to open the page in a given language.
Instead of embedding a notice on its own, you can add it as a section inside a Privacy Center, which brings several notices and other links together on one public page for individuals to browse.
A Privacy Center keeps its own list of languages, separate from your tenant's supported languages that a privacy notice page uses. If the two lists do not match, a visitor could reach the Privacy Center in a language your notice has no translation for. Check both language lists when you link a notice into a center.