Data and privacy
What WebActivity collects, who can see it, and why.
From the people who use the app
The WebActivity app has no sign-up. It keeps only what it needs to deliver cards and notifications:
| What | In plain words | Why |
|---|---|---|
| Device id | A random code the app makes the first time it opens. It is not linked to the person or to the phone itself. | So the service knows which phone each activity belongs to. |
| Push tokens | Addresses that Apple and Google give the app, so messages can reach the phone. | Without them, nothing can be delivered. |
| Phone type | iPhone or Android. | Apple and Google deliver messages in different ways. |
| Joined activities and groups | Which activities and push groups the person added. | To show them in the app and keep them up to date. |
| Website | The website address where the person tapped the launch button, for example acme.com. | So the app can show where each activity came from. |
| App usage | Taps, screens opened, errors, phone model, and system version, recorded by Microsoft Clarity. The notification history screen is not recorded. | To find and fix problems in the app. |
The app never collects a name, email address, phone number, contacts, or location. QR code scans and notification history stay on the phone.
From teams
- Account details, team members, and billing (card details stay with Stripe).
- Everything a team sends: activity content, push notifications, brands, images, and links. Content is encrypted when stored.
- Delivery and webhook logs, and a copy of each push notification. These are deleted after 90 days.
- The website and the dashboard use Microsoft Clarity to record clicks, scrolling, and pages viewed.
Who can see content, and why
WebActivity staff can see the content teams send: each activity's latest card, every push notification from the last 90 days, the links and images in them, how many phones each reached, and which account sent it.
Why: Apple and Google require apps that show content from other people to review that content, remove harmful content, and block the people who send it. If WebActivity could not do this, Apple or Google could remove the WebActivity app from their stores, and every team's activities and notifications would stop working.
- Staff review content to find phishing, scams, and other abuse, and when someone reports it.
- An account that breaks the Terms of Service can be suspended. Its API calls then answer 403
ACCOUNT_SUSPENDED. Staff can also remove its content: its cards are replaced with a "Removed" card and ended, and its launch buttons and push groups stop working.
What teams should do
- Put no personal data in a card beyond what the card needs.
- Anyone with an activity's link can see its content. Put nothing in a card that should not be in a link.
The full details are in the Privacy Policy.
