People, consent and identity: reach only people who agreed

Events and links are anonymous. To send in-app messages or push notifications to a person, Vela Links needs two things: proof of who the person is, and their agreement. This guide shows both. If you only want links, QR codes and analytics, skip it.

On this page

• Know what is stored, and why
• Make the identity secret
• Keep the secret on your server
• Sign the proof when someone signs in
• Give the proof and the person's answer to the app
• Ask for consent the right way
• Optional: use your server to send facts, contacts and consent
• Turn on Strict identity when you are ready
• Keep people in control of their data
• No server of your own?

Questions people ask

Why do I need a server?

Only a server can keep a secret. The app can be unpacked by anyone, so the secret must stay on your server. Without one, events and links work, but push and consent cannot be tied to a person.

Where do I keep the identity secret?

In an environment variable on your server, or in whatever secrets store your team already uses.

Is a phone number sent from the app?

Never. The app can send a push token and consent. Phone numbers and emails come only from your own server, with your server key.