Privacy Policy
Effective November 7, 2026.
What this app is
This Slack app is used inside a workspace to coordinate volunteer shifts for community events. The app has no separate login and no interface outside Slack. A person's Slack identity is how the app recognizes them, and everything it does happens through Slack commands, messages, and modals. Our website is described separately under "Our website," below.
A few terms used throughout. An Event is a volunteer activity that a Coordinator sets up in the app, with one or more shifts that people sign up for (the Terms of Service call it an activity); its date is the date it takes place. The Organization is the organization whose Slack workspace installs the app, for example a school's parent club. An Administrator manages the app for the Organization, a Coordinator is anyone who creates an Event, and a Volunteer is anyone who signs up for a shift. The Terms of Service define these the same way.
What we collect
Only what's needed to run sign-ups:
- Your Slack identity (user ID and your name). Used to show who has signed up for a shift, to put your name on the rosters and exports a Coordinator prints or shares, and to send you confirmations, reminders, and cancellation notices. "Your name" means your name as your Slack profile has it: the app looks up your real name from your Slack profile where one is set, and otherwise falls back to your Slack display name or handle (see "What we read from your Slack profile," below).
- Event and sign-up data. Which shifts you've claimed, at which Events, and when. Emails and phone numbers supplied by volunteers are deleted 7 days after the Event; the rest is kept for the period of the Organization's plan (see "How long we keep your data").
- Phone number or email address (optional). You may choose to provide a phone number, an email address, or both at sign-up for same-day contact if Slack notification isn't reliable. This is never required. If provided, they are visible only to that Event's Coordinator(s) and to workspace Administrators, and are deleted 7 days after the Event (below). The app does not use them to contact you.
- Feedback you submit, if you use the app's feedback command. This is sent directly to the app operator; an email address is only included if you choose to provide one when submitting.
- Error logs. When something fails, the app writes a diagnostic line to the hosting provider's log. These lines carry technical identifiers: your Slack user ID and your workspace's ID, an Event or shift ID, and the error message Slack returned. They are meant for fixing faults and are not used for anything else. Our hosting provider keeps them for a limited period set by its plan terms, which the provider may change.
What we don't collect
No passwords (Slack handles your login), no location data beyond an Event's stated address (entered by a Coordinator, not derived from your device), and no information from outside Slack. The app never accesses your Slack messages, files, or channels beyond what a Coordinator directly uploads for import (below) or what you directly submit through the app's own commands.
The app does read part of your Slack profile. See the next section for exactly what, and what it does not read.
What we read from your Slack profile
When a workspace installs the app, Slack asks the person installing it to approve a list of permissions. One of them is users:read, which Slack describes, in its own scope reference, as "View people in a workspace" (Slack: users:read scope). The app requests it and uses it for three things, and only these:
- Your name, for the record the app keeps of who you are. Looking up your real name from your Slack profile, so rosters and exports show a person's name instead of a Slack handle.
- The installing person's timezone, once, at install. Used to set the workspace's default timezone for Event times. It is stored as the workspace's setting, not as a record about that person.
- Whether a person is a bot account, checked when a Coordinator assigns someone to a shift or an Administrator is named, so the app doesn't treat a bot as a Volunteer.
What we are not saying. Slack's documentation lists which Slack methods the users:read permission opens (user lookup, user listing, presence) but does not enumerate every profile field those methods return, so this policy does not promise that the permission is technically incapable of exposing any particular field. It describes what the app asks for and does with it. The three uses above are the app's actual uses.
Email addresses from Slack are not requested. Slack documents email access as a separate permission, users:read.email (same scope reference, above). The app does not request it, so it has no permission to read your email address from your Slack profile. The only email address the app holds is one you choose to type in at sign-up (see "What we collect").
The spreadsheet import feature
If a Coordinator imports a shift schedule from an uploaded spreadsheet, the app downloads that file from Slack to read it. It reads only the columns it recognizes and creates the schedule from them:
- Event name
- Event date
- Event location
- Each job's name, times, position, and number of spots
The app does not store the file or its contents. Once the schedule is created, nothing from the file remains in the app other than that schedule. The app cannot delete the uploaded file from Slack. The file is held by Slack in the Organization's workspace, under Slack's access controls, until the person who uploaded it deletes it or until any file retention setting the Organization's Workspace Owners have turned on removes it. Which retention settings are available depends on the Organization's Slack plan.
How long we keep your data
How long we keep data depends on the kind of data and, for Event and roster data, on the plan the Organization is on.
Phone numbers and email addresses: 7 days, on every plan. A phone number or email address a Volunteer gives at sign-up is deleted 7 calendar days after the Event has passed. A scheduled job does this daily, so deletion happens between 7 and 8 days after the Event. No plan, and no arrangement with an Organization, changes this.
Event and roster data: the period of the Organization's plan. This is the Event, its jobs and shifts, the roster of who signed up for which shift, and the names of the people on it. The Terms say which plan an Organization is on. The periods are:
- Core plan (the only plan offered today): deleted 7 calendar days after the Event has passed. A scheduled job does this daily, so deletion happens between 7 and 8 days after the Event.
If we offer other plans, each will be listed here with its period.
What this means for Volunteers. A plan can keep Event and roster data longer than the default. That is the Organization's choice about its own Volunteers. Volunteers do not buy the plan, and their agreement is not asked. If your name or sign-up history is kept longer than 7 days, the Organization's plan is the reason, and you can ask the Organization's Coordinator which plan applies. A plan never extends the 7 days for your phone number or email address.
Custom arrangements. We may agree on a custom arrangement with an Organization, such as a large institution, that departs from this Policy or the Terms. It applies only if it is in writing, confirmed by us and the Organization, and says what it changes. It cannot extend how long we keep a Volunteer's phone number or email address, and it never keeps data after the app is uninstalled.
Records the app needs to keep working for a workspace while it is installed, such as which workspace installed it, its timezone, and who its Administrators are, are kept until the app is uninstalled (see "Removing the app").
Exports. Data deletion only applies to data actually held within the app. When a Coordinator or Administrator exports a roster, the export is a file delivered into Slack. It can include Volunteers' phone numbers and email addresses, for the people allowed to see them. Any data previously exported is not covered by the app's data retention schedule and is the responsibility of the Organization.
Posts and messages the app sends into Slack belong to the Organization's Slack workspace and follow the Organization's own Slack retention settings. The app's deletion schedule applies to data the app stores, not to Slack's message store.
Backups. Our hosting provider keeps backups for up to 30 days, so data we have deleted may remain in those backups for up to 30 days after the deletion.
Other records. Deletion on uninstall is described under "Removing the app," below.
Who can see what
Visibility inside the app follows the same rules regardless of who's asking:
- Anyone in the workspace can see which shifts at an Event are open or filled, and its basic details.
- If provided, your phone number and email address are visible only to that Event's Coordinator(s) and to workspace Administrators, never to other Volunteers. The app never sends them outside the workspace. A roster export is a file delivered into Slack; once someone downloads or shares it, it is outside the app's control (see "How long we keep your data").
- Who signed up, and for what, is the Organization's information. The Organization owns the information about its own Events and Volunteers. It decides, through its Administrators and Coordinators, who inside it can see names alongside sign-ups, and how that information is used for its own purposes, such as rosters, attendance, volunteer-hours totals, and reports. Those uses may show your name and your activity to the people the Organization chooses, which can include other Volunteers, for example in a summary of hours. We hold this information on the Organization's behalf. This does not change the rule above for phone numbers and email addresses, which only an Event's Coordinators and workspace Administrators can see, and which the app removes 7 days after the Event.
- Feedback you submit goes only to the app's operator, not to your Coordinator or workspace Administrators.
- The app's operator can see the data held in the app when supporting or fixing it, including through software tools such as an AI assistant.
Data sharing
We don't sell your data, and we don't use it for advertising. The app and our website show no advertisements. We share data only with the services that run the app: Cloudflare, which hosts it, and Slack, whose platform it runs on, and the software tools our operator uses to maintain the app, including an AI assistant that can see customer records, such as names, while the operator is supporting or fixing the app. If you send us an email, the email service that receives it also holds that message (see "Contact"). If you tap an Add to Calendar link, the shift's name, time and place go to the calendar service you choose; the link does not include your name.
We do not use your data to train artificial-intelligence or machine-learning models. The AI tools our operator uses to maintain the app are set so that the company that makes them does not use what they see to train its models. The app itself has no artificial-intelligence feature.
Slack's own handling of data that passes through its platform is governed by Slack's separate privacy policy and Data Processing Addendum, not by us. Contact information shared through the form on our website is stored in a customer relationship management (CRM) technology of our choice, as described under "Our website". See Slack's Privacy Policy and Slack's Data Processing Addendum.
Our website
Our website is at joinvoluntree.com. It is served through Cloudflare, which receives visitors' IP addresses and basic request information as part of delivering the site, and may keep ordinary operational logs. Our website does not set cookies of its own and does not run analytics. Cloudflare's bot protection, which can run in front of the site, may set a security cookie in your browser. We do not collect personal information about your online activities over time or across other websites or services, so we do not respond to "Do Not Track" signals. No other party collects that kind of information through our website or the app, apart from the hosting provider's ordinary request handling described above.
If you send us an access request. Our website has a form for groups that want to use the app. It asks for your email address, your group's name, whether your group uses Slack, the kind of group it is, the kinds of events it runs, when its next event is, and anything you choose to tell us. It also has an optional box for a phone number. We use this only to read your request and reply to you, and to call you on the phone number if you gave one. We keep it in a customer relationship management (CRM) technology of our choice, provided by a third party. That provider handles what it stores under its own terms, not ours. When you send the form, your browser sends it directly to that provider, so the provider also receives your IP address and basic request information. Nothing goes to that provider unless you send the form. We also keep our own notes on each request, such as when we last were in touch and whether we think your group is a good fit for the app, and we delete them with the rest.
We keep what you send us for as long as we are in touch with you about your request, and we review everything we hold from these requests at least every 12 months and delete what we no longer need. If you tick the box asking us to email you when VolunTree opens to more groups, we use your email address and your group's name only for that one email. You can ask us to delete your details, or take back that request, at any time by replying to any email from us in your own words, or by writing to privacy@joinvoluntree.com, and we will delete them. Copies may remain for a period in the backups of that provider. This information is kept apart from the app's data and is not covered by the app's retention periods. If we invite your group and it installs the app, the rest of this policy applies to what the app holds. Please do not put personal details about other people in the form.
Where this app can be installed, and what that means for you
Today the app is offered only to Organizations we have approved. Slack does not give an app's developer a way to limit distribution based on an Organization's home country.
This policy is written for an Organization and its Volunteers operating in the United States, and the app is offered for use in the United States only (see the Terms of Service). By installing the app, the installing Organization acknowledges that it is offered for use in the United States only, and that using it elsewhere does not by itself give anyone rights under another country's laws. We cannot promise that another country's law will not apply regardless. This policy has not been reviewed for compliance with the data protection laws of any other country or region (for example, the EU/UK's GDPR, or Canada's PIPEDA), and it does not make any commitments specific to those laws. If a workspace outside the United States installs the app anyway, which Slack does not let us prevent, that use is outside the Terms; the app still handles data as this policy describes, on the infrastructure described in the Data sharing section above, and you should not assume additional rights beyond what this policy states.
Children's privacy
This app is not directed to, and is not intended for use by, children under the age of 13, and we do not knowingly collect personal information from anyone under 13. If we learn that we have collected personal information from a child under 13, we will delete it. For the U.S. government's description of the rules that apply to children's online privacy, see the FTC's children's privacy guidance.
Your privacy rights
Several of the laws summarized in this section, including the California law discussed here, apply only to businesses that meet specific size or revenue thresholds. Regardless of whether a given law legally requires it, the rights below are offered to every user of this app as a matter of policy, because they're consistent with what the app already does (delete phone numbers on a schedule, collect little, never sell data) and because Slack Marketplace reviewers and Volunteers alike reasonably expect a modern privacy policy to state them.
For all users, regardless of location:
- Right to know what we hold. You can ask what personal information we currently hold about you, through the Contact channel below.
- Right to correction. If something we hold about you is inaccurate (for example, a phone number typed incorrectly), you can ask us to remove it. In practice, you can already update your phone number or email address without contacting anyone. See "What we collect," above, and the product's own change/remove flow.
- Deletion and requests. You can write to privacy@joinvoluntree.com about personal information we hold about you. The app deletes a phone number or email address 7 days after the Event. A deletion request would not reach a roster export the app delivered into Slack, or a spreadsheet that remains in Slack after import and is subject to the Organization's own data-retention policy. Those files live in Slack, outside this app (see "The spreadsheet import feature" and "How long we keep your data").
- No sale of personal information. We don't sell your personal information, and we never have. This is true regardless of what any specific law would otherwise require of us.
For California residents, under the California Consumer Privacy Act (CCPA), as amended by the California Privacy Rights Act (CPRA):
California gives its residents specific, named rights over their personal information under the California Consumer Privacy Act of 2018, as amended (Cal. Civ. Code § 1798.100 et seq., on California's official legislative site). The rights described below are drawn from the statute and from the California Attorney General's own public guidance for consumers (oag.ca.gov/privacy/ccpa):
- Right to know what personal information is collected, used, disclosed, or sold (Cal. Civ. Code § 1798.100, § 1798.110).
- Right to delete personal information collected from you, subject to certain exceptions in the statute itself (Cal. Civ. Code § 1798.105).
- Right to correct inaccurate personal information (Cal. Civ. Code § 1798.106).
- Right to opt out of the sale or sharing of personal information (Cal. Civ. Code § 1798.120). As stated above, we don't sell personal information and we don't use it for advertising, so there is nothing to opt out of today; if that ever changed, this policy would be updated first.
- Right to non-discrimination for exercising any of these rights (Cal. Civ. Code § 1798.125). We will not deny you access to this app, charge you a different amount, or provide a different level of service because you exercised a privacy right.
How to exercise any of the above: contact us using the information in the Contact section below. A verifiable consumer request under the CCPA must be responded to within 45 calendar days, extendable once by an additional 45 days with notice to you (Cal. Civ. Code § 1798.130(a)(2)).
Removing the app
If a workspace administrator uninstalls the app, no new data is collected from that workspace. Our policy is that all data associated with that workspace is deleted 7 days after the uninstall, for every Organization, with no exceptions. If the app is reinstalled within those seven days, the Organization's data comes back as it was; the delay exists so that an accidental uninstall can be undone. The deletion job runs daily, so deletion normally happens between 7 and 8 days after the uninstall. Slack's own rules also require apps to delete an Organization's data after the app is removed, and our schedule is faster than the deadline Slack sets. Files the app delivered into Slack, such as roster exports, are in your Slack workspace and are not removed by this deletion.
Changes to this policy
We may update this policy. The current version is always at https://joinvoluntree.com/privacy, with its effective date at the top. If a change is material, we will tell workspace Administrators by message through the app while it is installed.
Contact
Questions about this policy, or to exercise any of the rights described above: privacy@joinvoluntree.com.
Messages you send to us by email are received and stored by the email service provider we use for joinvoluntree.com, and are read by us.