Privacy Policy

Last updated August 4, 2026.

In plain language: Briskly stores the donor and volunteer records your organization enters, so you can use the product. We don't sell personal information to anyone, we don't use your donors' or volunteers' data for our own marketing, and you can export or delete everything at any time. Payments are handled entirely by Stripe — we never see or store card numbers.

Who this applies to

This policy covers getbriskly.com and the Briskly application. It applies to three groups of people, differently:

Account holders — the nonprofit staff or volunteers who sign up for and use Briskly.
Donors and volunteers — the people an account holder's organization tracks. Briskly stores this information on behalf of the organization that entered it; the organization, not Briskly, is responsible for having a lawful basis to collect and use it. If you're a donor or volunteer and want your information corrected or removed, the fastest path is contacting the organization directly — they control the record. Briskly will also act on a request sent to us, and organizations can give donors and volunteers a self-service link (described below) to view or update some of their own information directly.
Website visitors — anyone browsing getbriskly.com before signing up.

Information we collect

Category	What it includes	Source
Account information	Organization name, login email, password (stored as a salted cryptographic hash, never in plain text)	You, at signup
Donor & volunteer records	Names, emails, phone numbers, notes, custom fields, donation history, volunteer hours, task and shift assignments — whatever your organization chooses to track	Entered by the account holder, or self-entered by a donor/volunteer via a signup link or their personal portal, if the organization turns those on
Payment information	Subscription status and billing history. Briskly does not receive, process, or store card numbers.	Stripe, our payment processor
Support communications	The content of emails sent to support@getbriskly.com	You
Website analytics	Pages visited, approximate location (from IP address), device and browser type — aggregated, not tied to your name	Google Analytics

How we use information

To provide the service — store your records, render your dashboard, generate receipts and letters, run the reports and insights you ask for.
To process your subscription payment, through Stripe.
To respond when you email support.
To understand, in aggregate, which pages on the marketing site are useful — we do not use analytics data to build a profile of any individual visitor.
To detect and prevent abuse of the product's public, no-login pages (volunteer signup links, self-service portals) — see the security section below.

We do not sell personal information. We do not use the donor or volunteer data your organization enters to advertise to you, to them, or to anyone else.

Who we share information with

We use a small number of service providers to run Briskly. Each only receives what it needs to do its job:

Stripe — processes subscription payments. Stripe receives your payment details directly; Briskly never does. See Stripe's own privacy policy for how they handle payment data.
Cloudflare — hosts the application and stores account data (donor/volunteer records, account settings) in Cloudflare's infrastructure.
Google Analytics — provides aggregate website usage statistics for getbriskly.com. Not used inside the logged-in application.

We don't share personal information with anyone else, except if required by law (for example, a valid court order) or to protect the rights, property, or safety of Briskly, our customers, or others.

Data security

Everything runs over HTTPS.
Passwords are salted and hashed (PBKDF2, 100,000 iterations) — we cannot see or recover your actual password, even internally. Passwords must be at least 10 characters and include a letter and a number.
Repeated failed login attempts against an account are automatically throttled to slow down password-guessing.
The public, no-login pages (volunteer signup links, personal volunteer/donor portals, the public impact summary) only expose the specific information described on those pages, are only reachable via a long, unguessable link, and never expose your full account, other people's records, or login access.
Briskly never processes or stores your card number — that happens entirely on Stripe's own checkout page.

No system is perfectly secure, and we can't guarantee absolute security — but we've built Briskly to avoid handling more sensitive data than the product needs, and we take the security of what we do hold seriously. Briskly is a new, small product; it does not currently hold formal third-party security certifications like SOC 2, and we won't claim otherwise. If we ever discover a security incident that affects your personal information, we will notify affected account holders without undue delay after we understand what happened.

Data retention, export, and deletion

Your data is retained for as long as your account is active.
You can export every donor and volunteer record to CSV at any time, with no plan restriction — before, during, or after cancellation.
To delete your account and the data associated with it, email support@getbriskly.com. We'll confirm the request and remove the data from active systems; residual copies in routine backups age out on their own retention schedule rather than being individually purged, which is standard for a backed-up system.
If you're a donor or volunteer and want to see, correct, or remove your own information, check whether the organization has given you a personal link (it lets you view your own records and correct your contact info directly) — otherwise, contact the organization, or email us and we'll pass the request along.

Cookies

Getbriskly.com uses Google Analytics, which sets cookies to distinguish visitors and measure aggregate usage. The logged-in application sets one functional session cookie so you stay signed in — it isn't used for advertising or tracking, and it's deleted when you log out or expires automatically after 30 days.

Children's privacy

Briskly is a business tool for nonprofit organizations and is not directed at, or knowingly used to collect information from, children under 13. Briskly is deliberately not built for use cases involving children's personal information (for example, we don't support check-in or "kids ministry" style features). If you believe a child's information has been submitted to Briskly, contact us and we'll remove it.

Your rights, wherever you are

Regardless of where you live, you can ask us at any time to: tell you what information we hold about you, correct it, export it, or delete it. Email support@getbriskly.com to make any of these requests. If you're a California resident, these same rights are available to you under the CCPA; we don't sell personal information, so there is nothing to opt out of on that front.

Changes to this policy

If we make a material change to how we handle your information, we'll update the date at the top of this page and, for active account holders, note it somewhere you'll reasonably see it.

Contact

Questions about this policy or your data: support@getbriskly.com.