Privacy Policy

# Pidgebox — Privacy Policy

_Last updated: July 2, 2026_

This Privacy Policy explains how SciDaq LLC, a Wyoming limited liability company doing business as Pidgebox ("Pidgebox", "we", "us") collects, uses, and protects information when you use Pidgebox.
We collect the minimum needed to operate the Service and **use it only to provide and secure the Service** —
never to sell your data, target ads, or train models.

## 1. Information we collect
- **Account:** your email address; the identifier from your sign-in provider (GitHub or Google user id) if you
  use social sign-in; whether your email is verified; your plan and account status; timestamps.
- **API keys:** only a one-way (SHA-256) hash of each key — never the key itself.
- **Message data (transient):** sender/recipient mailbox aliases, subject, body, thread id, and timestamps,
  retained only until you delete the message or the mailbox is inactive for six (6) months (whichever is first).
- **Usage:** a per-tenant monthly message count, for enforcing plan limits and billing; and
  **usage events** — the type of operation performed (e.g. "send", "read", "signup") with your tenant
  identifier, a count, and a timestamp, recorded via Cloudflare's analytics infrastructure and retained
  there for approximately three months. Usage events never include message content, subjects, mailbox
  names, email addresses, or URLs. We use them (including simple aggregate summaries) solely to
  understand how the Service is used and to improve it.
- **Billing:** if you subscribe, your Stripe customer identifier. **Card and payment details are collected and
  processed by Stripe; we never see or store full card numbers.**
- **Webhook configuration:** for webhook boxes, the destination URL and a signing secret you control.
- **Network data (transient):** your IP address is used momentarily by our infrastructure provider for
  signup/rate-limiting; we do not store IP addresses in our own database.
- **Cookies:** the website sets one short-lived, strictly-necessary cookie during sign-in (CSRF protection for
  the OAuth flow). We do not use advertising or cross-site tracking cookies.

## 2. How we use information
To create and authenticate your account; to deliver and store messages and fire webhooks you configure; to
enforce plan limits and process payments; to prevent abuse and secure the Service; to send transactional email
(verification and account/payment notices); to understand aggregate product usage via the content-free usage
events described above; and to comply with law. That is the full extent of our use.

## 3. What we do NOT do
We do not read, analyze, or profile the content of your messages; we do not sell or rent your data; we do not
use your content for advertising or to train AI models; and we do not keep external backups of message content.

## 4. Legal bases (EEA/UK)
Where GDPR applies, we process data to perform our contract with you (providing the Service), for our legitimate
interests (security, abuse prevention, and service improvement), and to comply with legal obligations.

## 5. Service providers / subprocessors
We share data only with providers acting on our behalf to run the Service, or as required by law:
- **Cloudflare** — hosting, compute, and storage (Workers and Durable Objects).
- **Stripe** — payment processing and subscription management.
- **GitHub** and **Google** — optional OAuth sign-in (we receive your email and basic profile).
- **Amazon Web Services (SES)** — sending transactional email.
These providers are bound by their own data-protection commitments.

## 6. International transfers
The Service runs on Cloudflare's global network; transactional email is sent via AWS (United States) and payments
are processed by Stripe (United States). By using the Service you understand your data may be processed in the
United States and other countries, with appropriate safeguards where required.

## 7. Retention
Message content: until you delete it or six (6) months of mailbox inactivity. Account records and billing
references: for the life of your account and as needed for legal, tax, and accounting obligations.

## 8. Security
We use structural tenant isolation (a separate datastore per account), store only hashed API keys, transmit over
HTTPS, sign webhook deliveries, and apply rate limits. No system is perfectly secure; for sensitive content you
can additionally encrypt message bodies client-side (see below) so we only ever hold ciphertext.

## 9. Client-side encryption (zero-knowledge option)
Pidgebox does not read your messages. For cryptographic certainty, encrypt the body client-side with a password
only you and your recipient hold; we then store and relay only ciphertext we cannot decrypt. Never send the
password through Pidgebox.

## 10. Your rights
Depending on your location (e.g., GDPR, CCPA), you may have rights to access, correct, delete, export, or object
to processing of your personal data. Because we store little and you can delete your messages yourself at any
time, most requests are self-served; for account deletion or other requests, contact legal@pidgebox.com. We do not "sell"
or "share" personal information as those terms are defined under U.S. state privacy laws.

## 11. Children
The Service is not directed to, and we do not knowingly collect personal data from, anyone under 16.

## 12. Changes & contact
We may update this Policy; material changes will be posted here with a new date. Questions or requests:
legal@pidgebox.com (general support: admin@pidgebox.com).