Privacy and data handling

Collect only the information required for your purpose. Configure consent before analytics collection and avoid raw IP addresses, credentials or sensitive identifiers in event properties, traits, URLs and free-form messages.

The SDK example in Web SDK requires consent and disables the pre-consent queue. Consent withdrawal and stored-data erasure are different operations. An erasure request can be pending or waiting for processing; do not announce completion before the server reports it.

Use the application's Privacy Requests page with an authorized project administrator for visitor lookup, export and erasure requests. Do not invent profile-delete endpoints. Keep exported files private and remove temporary copies when they are no longer needed.

Application data (accounts, links, clicks, events, analytics) is hosted in Morocco. Email delivery (invitations, password resets, alerts, scheduled reports, demo-request replies) is entrusted to Brevo, a processor established in the European Union: the recipient's address, name and message content leave Morocco for that purpose. Do not tell your users that no data ever leaves Morocco. See the privacy policy and contact support@slnk.ma for the operational request channel.

These implementation notes describe product controls. They do not certify compliance or replace your organization's legal assessment.