givepeaches is peer recognition for Slack, made by Peach Parade Limited, a company registered in New Zealand ("we", "us"). this policy explains what we collect when your team uses givepeaches or our website, why, who we share it with, and what you can ask us to do with it. if anything here is unclear, email hello@givepeaches.com.
the short version
- we only see Slack messages that get a 🍑 reaction, mention Prince Peach, or contain an @mention and a 🍑, plus messages you send Prince Peach directly. we never read the rest of your workspace, and never anyone's private DMs.
- we keep a short snippet of a peached message (up to 300 characters) so the thank-you and the round-up can quote it.
- we don't sell your data, and we don't use it for advertising or to train AI models.
- payments are handled by Stripe. we never see or store card numbers.
what we collect
when your workspace adds givepeaches to Slack
| what | why |
|---|---|
| workspace ID and name, and who installed it | to run givepeaches for your workspace |
| a Slack access token for the givepeaches bot (stored encrypted) | so Prince Peach can post messages and see 🍑 reactions |
| for each person in the workspace: Slack user ID, display name, profile photo, timezone, email address, and whether they're an admin, a guest or a bot | to show names, reset everyone's daily peaches at their own midnight, let admins manage things, count your team size for billing, and match "sign in with Google" to the right person |
| every peach: who gave it, who got it, when, how many, the channel and message it was for, a snippet of that message (up to 300 characters) and any reason the giver wrote | this is the product: balances, thank-you messages, the activity feed and the Friday round-up |
| store items and redemptions, and who approved them | to run your team's rewards store |
| your settings (daily allowance, round-up channel, and so on) | to run givepeaches the way you've set it up |
Prince Peach only receives messages in channels he has been invited to. of those, he only acts on messages with a 🍑 (or your chosen emoji) together with an @mention, messages that get a 🍑 reaction, and messages sent to him directly. everything else is ignored and not stored.
when you sign in to the dashboard
if you sign in with Slack or Google, we receive your name, email address, profile photo and (for Slack) your workspace and user ID. we keep these in a signed cookie for up to 7 days so you stay signed in. we don't store your Google account password or have access to anything else in your Google account.
when you pay
Stripe collects your card and billing details directly. we receive your Stripe customer and subscription IDs, your plan, its status and renewal date, and the email used at checkout.
when you join the waitlist
your email address, the page you signed up on, where you came from (referrer and campaign tags, if any) and your country, worked out from your connection. we use it to email you when the Teams app is ready.
when you visit givepeaches.com
our marketing pages use Google Analytics, which sets cookies and collects things like the pages you visit, your rough location and your device type, so we can see which pages are useful. the dashboard at givepeaches.com/app doesn't load Google Analytics.
who we share it with
we use these companies to run givepeaches. each only gets what it needs to do its job:
| who | what for |
|---|---|
| Slack (Salesforce) | the platform givepeaches runs inside |
| Cloudflare | hosting the website and the givepeaches app |
| Supabase (hosted on AWS in the United States) | our database |
| Stripe | payments and billing |
| Resend | sending email (waitlist confirmations) |
| Zoho | our hello@givepeaches.com inbox |
| "sign in with Google", and analytics on the marketing site |
we may also share information if the law requires it, or with a buyer if givepeaches is ever sold (in which case this policy still applies to your data). we never sell personal information.
some of these providers store data outside your country, including in the United States. we rely on their contractual and security commitments to keep it protected.
how long we keep it
- while you use givepeaches: we keep your peach history so balances and history stay accurate.
- when you uninstall: the bot's Slack token is deleted straight away and we stop receiving anything from your workspace. your peach history is kept so it's still there if you reinstall. email us and we'll delete everything for your workspace within 30 days.
- billing records: kept as long as tax law requires.
- waitlist: until the Teams app launches, or until you ask us to remove you.
your rights
you can ask us to show you the personal information we hold about you, correct it, or delete it. you can also object to how we use it. email hello@givepeaches.com and we'll reply within 30 days. if your workspace's admins added givepeaches, they control your team's data too, and we may check with them first.
we follow the New Zealand Privacy Act 2020. if you're in the UK or EU, you have the rights the GDPR gives you, and we process workspace data to provide the service your organisation asked for. you can complain to the Office of the Privacy Commissioner in New Zealand, or to your local data protection authority.
security
Slack tokens are encrypted before they're stored, every request from Slack and Stripe is signature-checked, the database isn't reachable with public keys, and connections are always encrypted (HTTPS). no system is perfect, though. if something goes wrong that affects your data, we'll tell you.
children
givepeaches is a workplace tool and isn't meant for anyone under 16.
changes
if we change this policy in a way that matters, we'll update the date at the top and tell workspace admins before it takes effect.
contact
Peach Parade Limited, New Zealand. hello@givepeaches.com