Privacy notice · version 17

We collect only what is needed for the service you choose.

Each tool explains what it asks for and how the information will be used.

01

Nonresident petition participation

Both petitions accept optional wording endorsements and private feedback from nonresidents aged 18 or older. We store email, self-reported resident or nonresident role, optional endorsement, optional firsthand confirmation, approximate period and general location, feedback, date, language, wording version and a receipt hash. Nonresident records never enter resident support counts. A separate guest count shows only guests who endorsed the petition wording; feedback alone is not an endorsement. Emails, residency and accounts are unverified. Multiple accounts of one event do not establish multiple incidents. Identities and accounts are not shared with management without separate permission. Context may identify someone. We ask for no name, unit or host. Records reach retention review after 180 days and can be deleted earlier using the private code on Remove support.

02

What we collect

For text reports: submission type, topic, text, and selected choices. For files: the original photo or video, filename, type, size, SHA-256 fingerprint, and supplied context. For petition interest: topic, idea, proposed change, and an email for notices. For safety-petition support: email, residency and support confirmations, petition version, date, language, and an optional private note for Resident Relay. We also keep form language, receipt date, and the applicable notice version.

03

Paperwork to improve the site

This optional contribution stores only the PDF copy prepared in your browser, document type, page and block counts, size, SHA-256 fingerprint, language, date, consent version, and a hash of the private receipt. We do not store the source filename or ask for a name, unit, or contact details. Authorized reviewers may use the copy privately to test and improve Resident Relay's tools and educational materials. It is not published, sent to management, or used to train an outside model without separate consent. Context or missed details may still identify someone. It reaches retention review after 90 days and can be deleted earlier with the private code.

04

Bill comparison

To compare bills, we store the service month, whether it covers a full month, the printed multiplier, water, sewer, and trash charges, adjustment status, and bedroom and bathroom counts. We do not ask who lives in the home or who is on the lease. Entries are reviewed privately and are not published individually. They reach deletion review after 90 days; you can request deletion with the private code.

05

Shared rent

For Share Your Rent, we store only the monthly amount in cents, date, unverified status, this notice version, and a hash of the private code. We ask for no identity, unit, bedrooms, occupants, voucher, documents, or story. Only authorized reviewers can see individual amounts. Entries are removed after 90 days when the service is used; you can delete yours sooner with its code. The public rent reported by participants summary is closed. One entry does not establish a distinct household or representative Casa Lago rent.

06

Tow count

When this optional form opens for residents and guests, it will store how many times a vehicle was towed from Casa Lago and, if supplied, the month of the most recent tow. A ‘no’ answer is not sent. Only authorized Resident Relay reviewers can access answers. Each answer starts received and unverified; no unreviewed total is published, it creates no legal representation, and it does not file an official complaint. It reaches deletion review after 90 days and can be deleted earlier with the private code. We do not ask for a name, unit, plate, VIN, ID, email, documents, or another person’s details.

07

Calls for help

If you share a count, we store the number of times you say you called 911, the police non-emergency line, or property security about something at Casa Lago since living here, language, date, consent version, unverified state, and a hash of your private code. We accept counts of one or more calls only. We do not ask for your name, unit, reason, story, dates, or anyone else's details. Only authorized reviewers can see individual answers. We do not publish answers or unreviewed totals. A count does not prove a recorded call or the property-wide rate. You can delete it with the code; it reaches deletion review after 90 days. Earlier answers asked only about police calls and must be distinguished by consent version.

08

What we do not ask for

We do not ask for a name, unit number, or phone number. The petition-interest form asks for an email to deduplicate interest by topic and send activation notices. The support form asks for an email to count support once for that petition. Do not include other unnecessary personal details.

09

Private messages to management

Resend processes the subject, text and recipients to deliver your message. To count uses and outcomes, we retain only timestamps, opaque deduplication keys, provider message IDs, management-recipient roles and statuses. This ledger does not store message text, subjects, resident identity, email, unit, IP, device data or contact lists. We keep this metadata for 30 days and remove expired rows when the relay is used or the private dashboard is checked; we keep no lifetime totals. Resend retains emails and logs for 30 days under its current Free plan. We do not enable open or click tracking. Provider acceptance does not prove delivery, reading or response. Only authorized reviewers see the ledger; operator tests may be included.

10

Technical data

The form database does not store IP addresses or browser headers. Hosting and security providers may process an IP address, browser signals, time, and other technical data to deliver and protect the site. We therefore do not promise absolute technical anonymity.

11

How it is used

Every entry begins as resident-provided, unverified information. A private reviewer may review, hold, exclude, or delete material. A file or account never becomes a fact merely because it was submitted.

12

Interest is not a signature

Petition ideas are stored for private review. The associated email is kept in a separate contact table, supports one interest count per email and topic, and may be used to announce that a petition is ready for review. Registering interest does not support or sign a petition. Safety-petition support is stored separately and tied to the wording version the person reviewed. We do not verify residency by email. We do not share emails or identities with management without separate, specific authorization.

13

What may be published

Individual submissions and original files are not published. Only reviewed, de-identified text-experience counts may be shown, with at least five coded experiences in a category. Questions, suggestions, and files never automatically enter those counts. The site displays only the total number of petition supporters, without emails or notes. Residency is self-reported and not independently verified. Any photo displayed in the gallery requires specific permission to display it, identity review, and a separate minimized copy; the original and earlier submissions remain private.

14

How long it is kept

Raw text, petition ideas, and associated email contacts reach deletion review after 90 days. Files also reach a retention review after 90 days. Petition-support records reach retention review after 180 days and can be removed earlier with the private code. A special hold must be documented.

15

Private codes

After submitting, you receive a private code linked to the submission. It cannot retrieve, display, or edit the story or file. Resident-control functions may differ by submission type and must be confirmed on the relevant page.

16

Tracking and browser signals

We do not install advertising or behavioral analytics and do not try to track your activity across sites. A Do Not Track signal therefore does not change how the form works. Providers may still process technical signals for security and delivery.

17

Changes to this notice

A material change will appear here with a new version and date before it applies to new reports. We will not retroactively expand the use of reports already received.

18

Important limits

This is not a maintenance ticket, official complaint, legal notice, or emergency service. Information is not sold, used for advertising, or automatically sent to management or an agency.

Status Version 17: October 9, 2026. Earlier submissions keep the version in effect when they were received.