Privacy Policy

We verify that donations happened. To do that we need to know the amount of a sale, not who made it. We do not read or store your customers' personal information.

Merchant account information. Your name, email address, company name, and website when you create an account. Your logo, tagline, and public contact details if you choose to add them to your public verification page.

Sale event data. When your store reports a sale, we receive an order identifier, an amount, a currency code, and an idempotency key. Nothing else. We use these to calculate the donation your impact rule specifies and to avoid recording the same sale twice.

Charity selections and impact rules. Which charities you support and how much of each sale you give.

Payment connection metadata. If you connect Stripe, we store the connection state and the identifier of each event we have processed, so the same event is not counted twice. We do not store the contents of those events.

Billing information. Subscription status and your Stripe customer identifier. Card details are handled entirely by Stripe and never reach us.

Team members. The email address of anyone you invite to your account.

We do not read or store the personal information of your customers. No name, email address, postal address, card detail, or IP address of any end customer is written to our systems.

Where a payment provider delivers a webhook to us, that webhook may contain customer details as part of its standard payload. Our code does not read those fields and does not save them. They exist in server memory only long enough to verify the message signature, and are then discarded.

One thing we ask of you. Order identifiers are stored exactly as you send them. Do not put personal information in an order identifier. Send your store's internal order number, not a customer email address or name.

When a charity confirms an impact rate (for example, that one dollar provides two meals), we record the representative's name, title, email address, and IP address. This is an attestation record. The IP address exists so that a claim about what a donation achieves can be traced to the person who made it. This information is not published and is not visible to merchants.

We scrape publicly available contact information from charities' own websites to help merchants request rate confirmations. We do not scrape social networks. A charity may ask us to remove its contact record at any time.

Your verification page shows verified donation totals, the charities you support, dates, and blockchain transaction references. It shows your company name, and your logo, tagline and contact email if you have chosen to add them.

Individual proof pages, which you may link from customer receipts, show the amount of a single donation and its verification status. They contain no customer information and are excluded from search engine indexes.

Blockchain anchoring writes a cryptographic hash to the Polygon network. A hash is a fingerprint of the batch record, not the record itself. Nothing readable is written on chain, and nothing written on chain can be removed.

We use the following services. Each receives only what it needs to function.

• Supabase, database and authentication
• Vercel, hosting
• Stripe, subscription billing and, if you connect it, sale events
• Every.org, donation processing
• Resend, transactional email
• Firecrawl, website scraping for logo and contact discovery
• Anthropic, charity alignment analysis
• Alchemy, Polygon network access

We do not sell data. We do not share data for advertising.

Account and donation records are kept for as long as your account is active, and afterwards for as long as needed to keep public verification records accurate. Verified donations are a permanent record by design. If a donation is verified, the fact of it does not go away when you close your account, though we will remove your account details and unpublish your page on request.

You may request a copy of your data, ask us to correct it, or ask us to delete your account. Write to contact@master22solutions.com.

Deletion has one limit. Blockchain anchors cannot be deleted by anyone, including us. What is anchored is a hash, not personal information.

We use cookies necessary to keep you signed in. We do not use advertising or tracking cookies.

We will post any change here and update the date at the top. Material changes will be emailed to account holders.