Privacy Policy

1. Who this covers

Two groups of people appear in the Service:

• Account users — the nonprofit staff who sign up and use Because of You.
• Donors — the people a nonprofit thanks, whose details the nonprofit adds so we can personalise an experience. Here the nonprofit is responsible for that data and we act on its instructions (see section 6).

2. Information we collect

• Account information — your name, email, and organisation details such as organisation name, website, tax/registration identifier (e.g. EIN) and brand assets.
• Content you provide — website material, impact reports (including uploaded PDFs), photos, and the donor information you add (such as donor names, gift amounts and any fields you choose to include in personalized links).
• Website addresses entered into our public demo — if you try the demo on our homepage, we keep the website address you entered, the organisation name we read from that public site, and whether the demo built successfully. We use this to fix demos that fail and to follow up with organisations who tried us. We do not ask for or store your email address to run the demo, and there is no account involved. If you’d rather we didn’t keep yours, email us and we’ll delete it.
• Thank-yous made in ChatGPT: if you use our ChatGPT app, we receive what ChatGPT sends to make the thank-you: your organisation’s name and website, the words written for it, photos you attach, and an anonymised ChatGPT user ID that OpenAI provides. We store a one-way hash of that ID, never the ID itself, and use it only to limit how much one person can make and to check that a thank-you is theirs to change. We do not receive your name, email or the rest of your conversation. A donor first name or gift amount used for a preview or a personal link is placed in the link and is not stored by us. We copy photos (yours, or ones from your website) into our storage so the page can show them.
• Usage and analytics — how experiences are opened: opens, completion, time on page and shares, plus basic device/browser information needed to serve pages and keep them secure. Our public marketing pages, resource hub and published articles use daily aggregate page-view, referral-source and click counts. These analytics events contain no full URLs, query values, raw referrers or visitor identifiers and use no analytics cookies or persistent browser storage. They are not collected on donor experiences or signed-in app pages, and respect browser Do Not Track and Global Privacy Control. Counts are removed after 90 days through daily maintenance. The nonprofit’s own donor experience reporting is separate and continues. Google Analytics is disabled. Previously collected Google Analytics data remains subject to that provider’s property settings and any separate deletion request.
• Payment information — handled by Stripe. We receive billing status and limited details (such as plan and the last digits/brand of a card); we do not store full card numbers.
• Cookies — we use essential cookies to keep you signed in and to run the Service, including anti-bot protection during signup. We no longer load the Google Analytics script. Earlier analytics cookies may remain in your browser until they expire or you clear them. We do not use donor information for advertising.

3. How we use information

• to provide, personalise, host and improve the Service;
• to generate experiences from the content you give us;
• to process payments and manage subscriptions;
• to show you analytics about your own experiences;
• to provide support, keep the Service secure, and meet legal obligations.

We do not sell personal information, and we don’t use donor data for advertising.

4. Automated content extraction and support (AI)

Website text, impact reports, uploaded PDFs and content you ask us to draft or revise are processed by AI and automation providers, including OpenRouter and its model and OCR providers. Messages you send to the in-app AI help assistant are also processed by OpenRouter and its model provider. Please do not include donor lists, confidential records or information about people that is not appropriate for this processing.

Donor CSV imports and the fields used to personalize donor pages are not sent to AI services as part of those workflows. A source PDF is different: it is uploaded to private storage and a read link valid for five minutes is supplied for OCR. We attempt to delete the source after processing, including failed processing. A daily job discovers abandoned private uploads older than 24 hours and retries failed removals. With successful runs and no backlog, abandoned files are usually removed within 24–48 hours; failures can extend this. Photos extracted from reports and images you publish are hosted at public URLs. Only upload material suitable for your published experience.

5. How experiences are shared

Donor experiences are unlisted links, marked “no-index” to ask search engines not to list them. This is not access control or a guarantee against indexing. The visible page does not display a donor’s email address. Anyone with the link can view that page, so treat the links as you would a private URL.

6. Donor information and the organization’s role

The nonprofit decides which donor information to provide and why. We process it on the nonprofit’s behalf to provide the Service. You can choose how much to share:

• Shared link: no donor list or personalization fields are needed.
• Personalized link: fields you include in the URL are processed to display the page. They do not create a stored donor record through this workflow, but URLs may appear in browser history, forwarded messages and infrastructure logs. Do not put email addresses or sensitive information in these URLs.
• CSV import: the file is read in your browser. Only mapped fields are sent to us; the original CSV and ignored columns are not stored by this workflow. Name, email and amount are optional. You can use a supporter or gift reference on its own, then match the exported page link in your CRM. Email is excluded from automatic mapping.

References remain information that can be linked to a person; using an ID does not necessarily make a record anonymous. Supporter and gift references are retained for your link exports and are not displayed on donor pages. Stored donor pages have individual links, so engagement events can be connected to the donor record. Shared-link reporting does not identify each recipient from a donor list.

If a donor sends a reply, we store their message and the supplied or existing first name, and may email that message to the organization’s owner. Organizations can disable replies on ordinary experiences; Wrapped recaps currently include replies. Sending a message does not itself grant permission to publish it as a testimonial.

If you are a donor and want to access, correct or remove your information, contact the organization that sent the experience; we will help that organization respond.

7. Service providers and where data is held

We share information with providers who help us run the Service. Their terms, processing roles and retention settings vary; our data-handling guide explains verified details and points that still need confirmation. Because these providers (and our own hosting) operate outside Australia, using the Service involves disclosure of personal information overseas — principally to Japan and the United States:

• Supabase — database, authentication and file storage. Primary data is hosted in Tokyo, Japan (AWS ap-northeast-1).
• Vercel — application hosting and delivery. Server processing runs in the United States (iad1), with a global edge network for delivery.
• Stripe — payment processing (United States / global).
• Resend — transactional email such as sign-in, notifications (including donor replies), and individual experience emails requested by an account user (United States).
• OpenRouter and Firecrawl — AI processing and website reading, including the model and OCR providers used through OpenRouter. Processing locations depend on the provider; contact us for the current provider details before supplying restricted material.
• Cloudflare Turnstile — anti-bot checks during signup, including browser and network signals. Cloudflare operates a global network.
• Google Analytics — previously used for website/app measurement; new collection is disabled. Existing provider-held data requires separate retention/deletion review.

We may also disclose information if required by law, to protect our rights or safety, or as part of a business sale or reorganisation (in which case this policy continues to apply).

8. Security

We protect information with encryption in transit, access controls, and database rules that isolate each organisation’s data. No system is perfectly secure, so we can’t guarantee absolute security, but we take reasonable steps to protect personal information and to respond to incidents.

9. How long we keep information

A thank-you made in ChatGPT that isn’t saved to an account, and its photos, is deleted 30 days after it was made or published. Saving it to an account keeps it under the same terms as the rest of your experiences.

We keep account and content information while your account is active and as needed to provide the Service. Deleting an experience removes its stored donor rows, pages and associated page events. Organization-level supporter records and donor replies can remain: replies are managed separately in the Replies inbox. Removing an email from a new import does not automatically erase a previously created supporter record.

Workspace owners can review and delete linked donor records, supporter identities, personal links, replies and related events in Settings → Data & privacy. Older replies without a donor link need separate review. Deletion receipts retain counts and internal record IDs for 90 days. Contact us for account deletion or retained copies outside the live application. Backup and provider retention may differ from live application data. We will explain the applicable retention and any records we must keep, such as tax or legal records.

10. Your privacy rights

Subject to the law, you can ask us to access or correct your personal information, or to delete it. Email hello@because-of-you.com and we’ll respond within a reasonable time. If you’re a donor, contact the organisation that sent your experience (see section 6).

11. Children

The Service is intended for organizations and their staff, not for children, and is not directed to anyone under 16. Where an organization’s content refers to a child, that organisation is responsible for having the right to use it.

12. Changes to this policy

We may update this policy from time to time. We’ll change the “last updated” date above and, for material changes, take reasonable steps to let account users know.

13. Contact us and complaints

For any privacy question or request, email hello@because-of-you.com. If you’re in Australia and aren’t satisfied with our response, you can contact the Office of the Australian Information Commissioner at oaic.gov.au.