• Email address — required to create an account. You can sign in with a magic-link email or with Google (OAuth). We do not store passwords.
• Authentication tokens — secure, HTTP-only session cookies issued by our authentication provider (Supabase) to maintain your logged-in state.

When you complete onboarding you provide:

• Handle (unique username)
• Display name
• Bio / About section (optional)
• Profile avatar image (optional)
• Resident type (Owner, Renter, or Guest)

Public profile information (handle, display name, bio, avatar, and verification status) is visible to other verified residents of the Platform.

We do not collect residency documents. There is no utility bill, lease, or government ID to upload — we verify residency by mailing a card to your address and asking you to enter the code printed on it. Receiving mail at the house is the proof.

This means the most sensitive thing an earlier version of this service would have held about you — a scan of a household document — is something we never have. What we keep is the address itself, the fact that a card was issued for it, and whether the code has been used.

The code is not a password and cannot be used to sign in. It is single-use, stored only as a one-way hash, and spent the moment you verify.

• Street address and unit number — required, so we can mail your verification card. Stored privately and never displayed to other residents.

• Listing details: title, description, price, condition, and category for items you post for sale
• Listing images — processed server-side (resized, converted to WebP, and EXIF metadata stripped) before storage
• Private messages between buyers and sellers
• Reports you submit against listings

• Articles and stories submitted to the community newsletter (title, body, category, hero image URL)
• Community event submissions

• Business name, contact email, phone number, city, service area, service description, and business story submitted when claiming a free or paid advertising slot
• Stripe customer ID and subscription ID for paid advertising subscriptions
• Landing page view and interaction events (click-throughs and page views on business landing pages)

• Newsletter opt-in or opt-out status
• Email digest preferences
• Preferences for transactional notifications (listing messages, article status, ad status, monthly ad numbers)
• Email bounce and complaint status received from our email delivery provider

We do not run product analytics. No page-view, click, or session tracking service is loaded. The only automatic collection is the error reporting described in §2.10 and the request logs our hosting provider keeps (§4.1). The counts we keep ourselves are how many times a sponsored ad was shown on the homepage, how many times each article was opened, and, on an advertiser's landing page, how many times it was viewed and how many times its main button, phone number or offer code was tapped. Each count records the ad, the article or the page and the time, not the reader: no IP address, device or account is stored with it. An advertiser sees the totals for their own page. An article's heart count is the number of verified residents who favorited it; who they are is not shown.

We use Sentry to automatically capture application errors. Error reports may include browser type, operating system, page URL, and a stack trace. Error reports do not intentionally include sensitive personal data but may incidentally capture information present on the page at the time of the error.

• IP address (processed by Supabase and Vercel infrastructure)
• Browser type and version
• Device type
• Referring URL
• Pages visited and time spent
• Theme preference stored in your browser’s local storage (light/dark mode)

All administrative actions (approvals, rejections, account changes) are logged with a timestamp, the acting administrator’s identity, and before/after snapshots of affected data. These logs are used for accountability and are accessible only to QualityNeighbor administrators.

We use the following third-party service providers who process data on our behalf:

The following information is visible to other verified residents of the Platform:

• Your handle, display name, bio, and avatar
• Your verification status (verified/unverified)
• Marketplace listings you have published
• Articles and community content you have submitted and that have been approved
• Events you have posted
• Public business advertising landing pages

Your handle and bio are also public: they appear as the byline on any article you publish and on your author page at /by/your-handle, which anyone can read without signing in. Your display name is not shown there.

Your email address, physical address, verification code, and private messages are never displayed publicly to other residents.

We may disclose your information if we believe disclosure is required or permitted by law, including to comply with a subpoena, court order, or other legal process; to protect the rights, property, or safety of QualityNeighbor, our users, or the public; or to investigate fraud or security incidents.

If QualityNeighbor is involved in a merger, acquisition, asset sale, or similar transaction, your information may be transferred as part of that transaction. We will notify you of any such change by posting a notice on the Platform.

We use secure, HTTP-only cookies issued by Supabase to maintain your authenticated session. These cookies are strictly necessary for the Platform to function and cannot be disabled without preventing you from logging in. They do not track you across other websites.

We store your theme preference (light or dark mode) in your browser’s local storage under the key qn-theme. This data never leaves your device and is not accessible to us.

We do not use Google Analytics, Facebook Pixel, or any other third-party advertising, analytics, or cross-site tracking cookies.

You may request an export of the personal data we hold about you. Submit a data export request from your account settings page. We will process your request within 30 days.

You may update your display name, bio, and avatar directly in your account settings. If you believe other information we hold is inaccurate, contact us using the information in Section 13.

You may request deletion of your account and associated personal data from your account settings page. We will process your request within 30 days. Note that some information may be retained as described in Section 6, and content you submitted that has been incorporated into the published community newsletter may remain in archived newsletter editions.

You may opt out of analytics data collection at any time by toggling the analytics opt-out setting in your account profile. The opt-out is stored in your account and persists across devices and sessions.

You may manage your email notification preferences from your account settings, including opting out of the community newsletter, digest emails, and transactional notifications. Note that certain transactional emails (such as sign-in magic links and critical account notifications) cannot be disabled as they are necessary for Platform operation.

There is no residency document to delete — we never collect one. What exists is your address, the record that a card was issued for it, and the one-way hash of a code that has already been spent.

Deleting your account removes that record along with the rest of your data. The house ID slot then returns to the pool for whoever lives there next.

If you are a California resident, you have additional rights under the California Consumer Privacy Act, including the right to know what personal information we collect, the right to delete personal information, and the right to opt out of the sale of personal information. We do not sell personal information. To exercise your CCPA rights, contact us using the information in Section 13.