HappyProto Privacy Policy
Effective date: 2 November 2026
Last updated: 2 November 2026
This policy explains how HappyProto LLC (“HappyProto”, “we”, “us”), a Wisconsin limited liability company at 2800 E. Enterprise Ave, STE 333, Appleton, WI 54913, handles personal data. It covers:
- the marketing site and waitlist at https://happyproto.at;
- HappyProto accounts, the dashboard and api.happyproto.at; and
- the HappyView instances we host for our customers (“Instances”).
There are two very different roles here, so this policy is split in two:
- Part A: data about you, our visitors and customers. For this data, we are the controller. We decide what to collect and why.
- Part B: data about your end users that you store in your Instance. For this data, we are a processor (a “service provider”). We handle it on behalf of the customer who runs the Instance and follow their instructions.
If you use an app built on a HappyProto Instance, that app’s operator is responsible for your data. Please read their privacy policy and contact them first.
Part A: Data about our visitors and customers
A1. What we collect
| What | Examples | Where it comes from |
|---|---|---|
| Waitlist details | Email address, anything you write in the sign-up form | You |
| Account details | Your atproto DID, handle and display name; the email address on your atproto account, which you allow us to see when you sign in; and any contact email you give us | You and your atproto identity |
| Instance details | Instance name and slug, domains, plan, settings, HappyView version | You |
| Usage metering | Per-Instance CPU time, memory, disk use, egress and ingress traffic, number of seats and API clients, sampled about every minute and rolled up hourly | Our systems |
| Service logs | IP address, request times, URLs, user agent, error logs, audit logs of account actions | Our systems |
| Support and feedback | Emails, bug reports, survey answers, call notes | You |
| Analytics | Pages viewed, referrer, country, device and browser type, measured without cookies | The marketing site and waitlist |
| Payment details (not during the closed beta) | Billing name and address. Card details are collected by our payment processor, not by us | You, via our payment processor |
We don’t sell personal data, and we don’t use your data for targeted advertising.
A2. Why we use it
- To provide the Service: create and run your Instances, sign you in, and route your domains. (Legal basis where GDPR applies: performance of a contract.)
- To meter usage during the beta: to enforce resource limits and to set future plan limits and pricing. (Legitimate interests; contract.)
- To verify requests about your account, such as closing it, using the email address on your atproto account. (Contract; legitimate interests.)
- To communicate with you: service notices, data-loss and reset warnings, beta invites, and answers to your questions. (Contract; legitimate interests.)
- To keep the Service secure: detect and prevent abuse, spam and attacks, and enforce our Terms. (Legitimate interests; legal obligation.)
- To understand and improve the marketing site: using cookieless analytics. (Legitimate interests.)
- To follow the law: respond to valid legal requests and keep required records. (Legal obligation.)
We may send you occasional product updates about HappyProto. You can unsubscribe at any time. Service notices (such as data-loss warnings) aren’t optional while you have an account.
A3. Cookies and analytics
The marketing site at happyproto.at uses Cloudflare Web Analytics to count visits. It doesn’t use cookies or similar storage, and it doesn’t track you across visits or across other sites. It records the page you viewed, the referring site, your country, your device and browser type, and page performance.
We don’t use advertising or tracking cookies anywhere. The dashboard uses only the cookies or storage needed for sign-in and security. Analytics isn’t loaded on the dashboard or on Instances.
A4. Who we share it with
We share personal data only with providers who help us run the Service (“subprocessors”), and only as much as they need:
| Subprocessor | Purpose | Data | Location |
|---|---|---|---|
| Hetzner Online GmbH | Hosting for the control plane and tenant Instances; encrypted backup storage | All data stored in the Service, including Instance data | Finland (Helsinki) |
| Cloudflare, Inc. | DNS for happyproto.at, hpy.at and happyview.dev; network proxy and security for the hpy.at redirect and happyview.dev; cookieless analytics on happyproto.at | Domain names and DNS lookups; for traffic it proxies, IP address, request details (such as URL, browser type and time) and security signals; for site visitors, pages viewed, referrer, country, and device and browser type | US / global |
| Vercel Inc. | Hosting the HappyView documentation site at happyview.dev, until it moves to wisp.place (listed below) | IP address and request details (such as URL, browser type and time) in server logs | US / global |
| Atmosphere Mail LLC (Comail) | Sending beta invites and service email | Recipient addresses, email headers and delivery logs (message bodies are not stored) | US |
| nekomimi LLC (wisp.place) | Hosting the happyproto.at website and the dashboard | Request paths, status codes and timings (no IP address, user-agent or referrer logs; aggregate hit counts only) | US, EU (Germany, Finland), Singapore |
| Supabase, Inc. | Waitlist database | Waitlist details (email address and sign-up form answers) | US (Oregon) |
| Discord Inc. | Beta tester community and support chat | Your Discord username and anything you post in the beta server | US |
We’ll keep this list up to date and give customers 14 days’ notice before adding a subprocessor that handles Instance data.
We may also share data:
- when the law requires it, or to respond to a valid legal process;
- to protect the safety, rights or property of people, our customers or HappyProto, including reporting CSAM to NCMEC;
- with a buyer or successor if HappyProto is merged, acquired or sells its assets. We’ll tell you before your data becomes subject to a different privacy policy.
A5. Public atproto data
When you sign in with your atproto identity, we receive your DID and handle, which are already public on the atproto network. We also ask your atproto account’s host for the email address on your account; you’ll see this permission request when you sign in. We keep that email address as part of your account details, for service email and to verify requests about your account. The dashboard doesn’t write any records to your atproto repository.
A6. How long we keep it
| Data | How long |
|---|---|
| Waitlist details | Removed when you join the beta through an invite or ask to be removed; otherwise 12 months after the waitlist closes |
| Account details | While your account is open, then deleted within 30 days of closing it. Copies may remain in encrypted control-plane backups for up to 6 months |
| Instance data | Deleted from our hosts after a 7-day restore window once you delete the Instance. Backup copies normally expire within 30 days of deletion (see A7 and Part B). Operational records about the Instance (settings, usage, encrypted credentials) may remain in encrypted control-plane backups for up to 6 months |
| Usage metering | Raw per-Instance data for 12 months, to set and review pricing. After an account closes, its usage records are pseudonymised: they’re no longer stored with the account, but our audit logs can still link them to it until those logs expire. After 12 months, kept only in aggregated form |
| Service and access logs (including server sign-in logs) | Up to 30 days |
| HappyProto platform audit and security logs | 12 months |
| Support emails | 24 months after the conversation ends |
| Billing records (paid plans) | As long as tax law requires |
Encrypted control-plane backups may also hold copies of logs and audit records for up to 6 months.
An Instance’s own HappyView audit and event logs are Instance data, controlled by the customer who runs the Instance (see Part B).
We may keep data longer if the law requires it, or to resolve disputes or enforce our Terms.
A7. Closing your account
During the beta, you can close your account by emailing support@happyproto.at. We’ll complete the closure within 30 days of your request. To verify a request, we accept it if it comes from the email address on your account. Otherwise, we’ll ask you to confirm from that address, or to send a direct message to @happyproto.at on Bluesky from your atproto account. When we close your account:
- Your Instances are stopped and their public routes removed straight away.
- For 7 days we can restore them if you ask. Then we permanently delete the Instance data from our hosts. Copies in our encrypted backups normally expire within 30 days of deletion.
- We delete your account details within 30 days, except what we must keep for legal, billing or security reasons.
- Instance slugs are never reused, so we keep the slug and a record that it was used. This prevents someone else from taking over your old address.
Copies in rolling logs expire on their normal schedule (see A6). Account details and operational records about your Instances (such as settings, usage history and encrypted credentials) may remain in encrypted control-plane backups for up to 6 months before they expire. Data you or your users published to the atproto network stays on the network. Deleting your HappyProto account doesn’t delete your atproto identity or your PDS data.
A8. Your rights
Depending on where you live (for example, the EU, UK or certain US states such as California), you may have the right to:
- access the personal data we hold about you and get a copy;
- correct it;
- delete it;
- object to or restrict some processing;
- withdraw consent where we rely on consent;
- port your data to another service;
- opt out of “sale” or “sharing” for targeted advertising (we don’t do either);
- not be discriminated against for using these rights.
To use any of these rights, email privacy@happyproto.at. We’ll verify your identity in the same way as for closing an account (see A7). For a waitlist entry, we’ll ask you to confirm from the waitlist email address. We’ll reply within 30 days, or within the time the law requires. If you’re in the EU or UK, you can also complain to your local data protection authority.
A9. Security
We use reasonable technical and organizational measures to protect personal data. These include encryption in transit (TLS), isolated containers and private networks for tenant Instances, mutual-TLS between our internal services, and access limited to staff who need it. No system is perfectly secure, and this is a beta. Please also read the data-loss section of our Terms. If a breach affects your personal data, we’ll notify you as the law requires. For breaches affecting End User Data in an Instance, see B6.
A10. International transfers
HappyProto is based in the United States, and our providers operate in the US, the EU (Finland and Germany) and Singapore. If you’re outside the US, your data will be transferred to and processed in the US and other countries. Where required, we rely on appropriate safeguards for these transfers, such as the European Commission’s Standard Contractual Clauses or the EU-US Data Privacy Framework where a provider is certified.
A11. Children
The Service is not for children under 13, and we don’t knowingly collect personal data from children under 13. If you think a child under 13 has given us personal data, email privacy@happyproto.at and we’ll delete it.
Customers whose apps may be used by children are responsible for complying with children’s privacy laws such as COPPA. See Part B.
Part B: Data in customer Instances
B1. Our role
Customers use their Instances to store and process data about their own end users (“End User Data”). This may include:
- public atproto network data that the Instance indexes, such as posts, profiles and other records published by anyone on the network;
- sign-in data for people who sign in to the customer’s app (DIDs, handles, OAuth session tokens);
- private data stored in atproto spaces, which isn’t public on the network;
- any other data the customer’s scripts store.
For End User Data, the customer is the controller and HappyProto is the processor. We process End User Data only:
- to host and run the customer’s Instance;
- to keep the Service secure and prevent abuse;
- to comply with the law; and
- as the customer otherwise instructs us.
We don’t use End User Data to market to end users, train models, or build profiles. We don’t look at private space data except where needed to provide support the customer asked for, investigate abuse or a security problem, or comply with the law.
B2. Usage metering of Instances
Our usage metering measures resources (CPU, memory, disk, traffic, seat and API-client counts) at the Instance level. It doesn’t record the contents of End User Data. Seat and API-client figures are stored as counts, not as lists of end users.
HappyView telemetry. Managed Instances run HappyView with telemetry turned on, and identify themselves to us as HappyProto-managed. Customers can’t turn this off for a managed Instance; we use it to operate, support and improve the Service and HappyView. Each Instance sends one report a day, containing:
- identity and versions: the report format version, a random Instance ID (not linked to your account ID), report time, process start time, HappyView version, and a marker saying the Instance is HappyProto-managed;
- totals: counts only, such as numbers of records, users, sessions, jobs and lexicons, plus counts for up to 25 fixed event types;
- activity since the last restart: network events received, matched and skipped; bytes in and out; API request counts (including how many used credentials); script runs and run time; and job wait times;
- feature use: for each feature (such as scripts, jobs, plugins, labelers, spaces and API keys), whether it has ever been used and whether it’s in use now;
- host health: CPU cores; memory use and limit; whether it runs in a container; network bytes in and out; database and log sizes and free disk space; which built-in settings are configured (names only, never their values) and how many other settings exist; and database maintenance status, including timestamps, sizes and any error message;
- lexicon summary: the number of lexicons, and what share of records falls in each of up to 10 collections, without naming them.
Telemetry doesn’t include End Users’ DIDs or handles, records or record contents, lexicon names, schemas or documents, or the customer’s contact details. Our telemetry server sees the Instance’s IP address in transit, as any web server does, but doesn’t store it or the user agent. Telemetry is kept for 12 months.
B3. End-user requests
If you’re an end user of an app built on HappyProto, please contact that app’s operator to access, correct or delete your data. If you contact us, we’ll forward your request to the operator where we can identify them, and help them respond.
B4. Deletion and retention of End User Data
End User Data is kept for as long as the customer keeps it in their Instance. When a customer deletes an Instance or closes their account, we delete the Instance’s End User Data after a 7-day restore window, as described in A7. Encrypted backup copies normally expire within 30 days of deletion.
During the beta, Instance backups are best-effort. We back up Instance data automatically, but we don’t promise that a backup will exist or restore successfully. End User Data in an Instance could be lost if a host fails or if we have to reset an Instance. Customers are responsible for keeping their own copies and for telling their end users anything their own policies require.
B5. Public network data and deletions
Instances index data that people publish publicly on atproto. When an author deletes a record, or their account is deleted or taken down, HappyView processes those events from the network and removes or hides the data. If you’ve published something on atproto and believe a HappyProto-hosted Instance is still showing it after deletion, email privacy@happyproto.at with the record URI and Instance URL.
B6. Security incidents
If we confirm a security breach affecting End User Data in a customer’s Instance, we’ll notify the customer without undue delay, and within 72 hours of confirming it, with what we know and what we’re doing about it. We’ll help the customer meet any notification duties they have to their end users or regulators.
Changes to this policy
We may update this policy. If a change is material, we’ll email account holders and post a notice in the dashboard at least 14 days before it takes effect, unless the law requires a faster change. The “Last updated” date always shows the current version. Earlier versions are available on request.
Contact
HappyProto LLC 2800 E. Enterprise Ave, STE 333, Appleton, WI 54913 Privacy: privacy@happyproto.at General: support@happyproto.at