This Privacy Policy describes how Endenza (“we”, “us”, “our”) collects, uses, shares, and protects information when you use our website, the walkable neighbourhood where your home (your Cadenza) lives, and related services (collectively, the “Service”).
We operate from British Columbia, Canada and design this policy to be consistent with the Personal Information Protection and Electronic Documents Act (PIPEDA), British Columbia’s Personal Information Protection Act (BC PIPA), and: for visitors located in the European Economic Area or the United Kingdom - the General Data Protection Regulation (GDPR) and UK GDPR.
1. Who we are
Endenza is a solo-developer creator-platform project. The data controller for
purposes of GDPR is the developer of Endenza. You can reach us at
privacy@endenza.app.
2. Information we collect
We collect the categories of information described below. We collect only what we need to operate the Service.
2.1 Information you provide directly
- Your GitHub account details. You sign in with GitHub. We receive your GitHub user ID, handle, profile name and avatar URL, and your primary verified email address if GitHub provides one. We do not receive your GitHub password, and we do not keep the access token GitHub issues at sign-in: it is used during sign-in to read your profile and verified email, then discarded.
- Profile: the display name and bio you enter in Settings, and any social links you add.
- Your home in the neighbourhood: the lot you claim (its place on the street shows your handle), your home’s layout and furnishings, its welcome sign, wall art and front, your outfits, and your choices about whether visitors may come in and whether your guestbook is open.
- Your look and profile picture: the look you save for your avatar. If “Use as my picture” is on, we also store a small picture of it, and that picture is public: anyone who knows your handle can load it.
- Guestbook notes: notes you leave in other people’s homes are stored with your handle and shown to that home’s owner. Notes left in your home are stored for you.
- Tokens and games: a ledger of the tokens you earn and spend in the neighbourhood (including outfit pieces bought from the tailor), and the boards of table games you play.
- Your public GitHub work: when you furnish your home from GitHub, we read your public repositories, live sites and languages from GitHub’s public API and keep a copy for up to six hours. Anyone can view any GitHub user’s public work this way; we read nothing that is not already public.
- Feedback: the message and page address you send through a feedback form.
- Support communications: anything you send us by email.
2.2 Information we collect automatically
- Session records: when you sign in we record your browser’s user agent and a shortened prefix of your IP address with your session, so we can show where you are signed in and spot abuse.
- IP addresses: used briefly as a rate-limit key (for example, how often one address may join the neighbourhood’s live view), and present in Cloudflare’s standard request logs. We do not use them for analytics or profiling.
- Live presence: while you are in the neighbourhood, your position, facing and look are sent to other people in the same area so they can see you walk. This is live only and is not stored. You can hide yourself from others with the “Shown to neighbours” switch in the avatar panel.
- Account events: sign-in, sign-out, deletion and similar events are kept in an audit log for security.
- Browser storage: we keep a few small values on your device (theme, your home and look while signed out, and similar). See the Cookie Policy for the full list. These stay on your device unless a feature you use sends them to us, such as saving your home while signed in.
2.3 Information we do not collect
- We do not use third-party advertising cookies.
- We do not run cross-site tracking scripts.
- We do not buy or sell personal data.
3. How we use your information
We use information for the following purposes (and only these):
| Purpose | Categories used | Lawful basis (GDPR) |
|---|---|---|
| Operating the Service (sign-in, your home, guestbook, look, tokens and games) | Account info, GitHub details, home and look data, notes, session records | Contract (Art. 6(1)(b)) |
| Preventing abuse (rate limits, AUP enforcement) | IP, request logs | Legitimate interest (Art. 6(1)(f)) |
| Communicating product updates (only if you opt in) | Consent (Art. 6(1)(a)) | |
| Responding to support and legal requests | Whatever you sent us | Legitimate interest / Legal obligation |
We do not sell your information or use it for advertising, and we do not use it to train AI models.
4. Cookies and similar technologies
We use a very small number of strictly-functional storage mechanisms. We do not use third-party advertising cookies or cross-site tracking. See our separate Cookie Policy for the full breakdown.
If you are visiting from the EEA or UK, the cookie banner gives you the opportunity to dismiss the notice; non-essential storage will not load until you do.
5. Third-party processors
We share your information only with the third parties below, and only to the extent needed to operate the Service. Each processor is bound by its own privacy commitments.
| Processor | What they receive | Purpose |
|---|---|---|
| GitHub, Inc. | The sign-in handshake; requests for public profile and repository data | Signing you in; furnishing homes from public GitHub work |
| Cloudflare, Inc. (CDN, Workers, D1 database, R2 and KV storage) | Request metadata, IP, account and session records, everything in §2.1 | Hosting, storage, DDoS protection, sessions |
| Neon, Inc. (Postgres) | A replica of some account records, when enabled | Database migration and backup |
Two features in the neighbourhood embed outside sites, and each loads only after you click it: the BOO bar plays music and games from bunchofothers.com (which saves its own high scores) and videos through YouTube’s privacy-enhanced player (youtube-nocookie.com). Those sites receive your IP address and set their own storage under their own policies.
We do not share your data with advertisers, data brokers, or analytics networks.
6. International transfers
Your data may be processed in countries other than yours, including the United States (GitHub, Cloudflare, Neon). Where required, we rely on Standard Contractual Clauses or equivalent transfer mechanisms.
7. Retention
- Account data: kept for the lifetime of your account.
- When you delete your account (Settings → Delete account): your home and lot, home layout, settings, guestbook notes, tokens, games, look, picture, runner tokens and GitHub links are removed at once, and you disappear from the street. Your account record itself (handle, GitHub ID, email) and any billing records are kept for 30 days and then permanently deleted.
- Rate-limit records keyed by IP: kept only for the window they limit (minutes to a day).
- Copies of public GitHub data: up to six hours.
- Request logs: kept by Cloudflare under its standard retention.
- Security audit events: kept while the account exists; the link to your account is removed when it is permanently deleted.
8. Your rights
Subject to applicable law, you have the right to:
- Access the personal information we hold about you.
- Correct inaccurate personal information.
- Delete your personal information (subject to limited exceptions, e.g. legal hold).
- Export your personal information in a portable format.
- Withdraw consent at any time (where we rely on consent).
- Object to processing based on our legitimate interests.
- Lodge a complaint with your supervisory authority (in Canada: the Office of the Privacy Commissioner; in BC: the Office of the Information and Privacy Commissioner for BC; in the EEA/UK: your national DPA).
To exercise any right, email privacy@endenza.app. We will verify your
identity (typically by confirming control of the email on file) before
acting.
9. Children
The Service is not directed to children under 13, and we do not knowingly collect personal information from anyone under 13. Paid plans require the age of majority in your jurisdiction (see Terms of Service).
10. Security
We protect data with reasonable technical and organizational measures - TLS in transit, provider encryption at rest, session tokens stored only as hashes, least-privilege access, and limited retention. No system is perfectly secure; if we learn of a breach affecting your information we will notify you in line with applicable law.
11. Changes
If we make material changes to this Privacy Policy, we will notify you via email (where we have one) and post a banner on the site for 30 days. The “Last updated” date at the top is authoritative.
12. Contact
- Privacy questions / rights requests:
privacy@endenza.app - General contact:
hello@endenza.app - Mailing address: available on request until a formal business mailing address is published.
Subject to attorney review before billing. This Privacy Policy is a templated baseline drafted by the Endenza team without formal legal counsel. We will engage Canadian privacy counsel to review and refine this policy before charging users for any paid feature. If you spot something off, email
privacy@endenza.app.