Version 1.0 · Effective 2026-08-29 · sha256 24e5a217183883d0a498e2a9039079c6de0be4bc91eccce25f302fbe0efdeca9
California Beta - Version 1.0
August 29, 2026
This Privacy Policy explains how BLUNA LLC, a California limited liability company, operating the BLUNA beta platform ("BLUNA"), collects, uses, retains, discloses, and protects personal information in connection with the California beta of the BLUNA website, applications, account onboarding, job coordination, communications, and related services (the "Platform").
The beta is a business-to-business property-services platform for Property Customers and Vendors. The primary property-side beta user is an individual property manager, with owner-direct and property-management-company accounts also supported. Residents are not Platform users or parties. BLUNA nevertheless may receive limited resident or occupant information incidentally through an authorized Property Customer or Job record, including through before-and-after Job Photos. This Policy addresses that information as well.
This Policy applies to personal information BLUNA handles for its own Platform purposes. In some Jobs, a Property Customer may be a "business" subject to the California Consumer Privacy Act (CCPA) and may provide personal information to BLUNA for processing on its behalf. For that customer-directed processing, the BLUNA California Data Processing Addendum may apply and BLUNA may act as a service provider or contractor. The role depends on the data and purpose, not merely the label used by the parties.
This Policy does not govern a Property Customer's or Vendor's independent privacy practices. Property Customers remain responsible for resident-facing notices and permissions that apply to their own collection, disclosure, or use of resident information.
Depending on how a person uses the Platform, BLUNA may collect the following categories:
| Category | Examples |
|---|---|
| Account and identifiers | Name, business name, role, email, telephone number, account ID, login/authentication records, and business address or service area. |
| Property and Job Data | Property address and unit number; service request and scope; paint colors; bulb counts and types; appliance type, manufacturer and model; flooring type; materials; property condition, repair and maintenance history; service history; before-and-after Job Photos; measurements; technician notes; hazards; completion records; rework/dispute information; and Restricted Access Data when operationally necessary. |
| Vendor business and compliance data | Business identity, service categories, credentials, licenses or permits supplied during onboarding, certificates of insurance, tax forms, payout information supplied to or through Stripe, and performance records. |
| Transaction data | Quotes, approved Change Orders, Job Price, charges, refunds, credits, payout status, commission, chargebacks, and transaction identifiers. Stripe generally receives payment-card or bank credentials through its own interfaces. |
| Communications | Support requests, email, SMS, in-app messages, chatbot or AI-assisted interactions, call metadata if calling is later enabled, and consent/opt-out records. |
| Device, security, and internet activity | IP address, browser/device type, operating system, authentication events, logs, cookies or similar technical identifiers, security events, and interaction with Platform features. |
| Incidental resident information | Information that may incidentally appear in an authorized Job Photo or Job record, such as a resident name, face, family photograph, mail, document, screen, personal effect, or limited access/coordination detail. The beta is not designed to build resident profiles or collect resident financial, medical, screening, or government-ID information. |
| Restricted Access Data and other sensitive/security information | Lockbox codes, gate codes, alarm instructions, key-location information, or similar unit-access credentials; Vendor tax identifiers in tax documentation; and account-authentication information. BLUNA treats unit-access credentials as high-risk security information whether or not a particular item falls within the CCPA statutory definition of sensitive personal information. |
| Derived or deidentified information | Service metrics, generalized building attributes, usage statistics, quality indicators, and aggregated or deidentified analytics created from Platform data after removing information reasonably capable of linking the dataset to a particular consumer or household. |
BLUNA may obtain information directly from a Property Customer or Vendor; from authorized personnel using an account; from Job activity and devices; from Stripe and other service providers; from a property owner or manager that authorizes a user; from public or professional sources used for onboarding verification; and from information generated in the course of coordinating or documenting a Job.
BLUNA may use personal information for the following business and operational purposes:
BLUNA may disclose information as reasonably necessary to:
BLUNA does not sell personal information and does not share personal information for cross-context behavioral advertising in the California beta. BLUNA does not use identifiable resident information or identifiable Job Photos to train a general-purpose AI model.
The beta may use cookies or similar technologies reasonably necessary for authentication, security, session continuity, preferences, and service analytics. BLUNA should not enable third-party advertising pixels, cross-context behavioral advertising, or unrelated tracking during the beta without updating this Policy and implementing any required choice mechanism. Because the beta does not use cross-context behavioral advertising, BLUNA does not treat a legacy browser "Do Not Track" signal as changing a practice that is not occurring. If applicable law requires recognition of an opt-out preference signal for a later practice, BLUNA will process that signal as required.
Job Photos should document the work area, condition, progress, completion, incident, or quality, not residents or private resident materials. Users are instructed to avoid unnecessary faces, minors, family photographs, mail, identification, medical or financial papers, computer screens, and unrelated personal effects. BLUNA may use automated detection, blurring, redaction, or cropping tools to reduce incidental resident identification before a photo becomes the long-term retained copy. Automated detection may be imperfect, so users remain responsible for photographing only what is reasonably necessary for the Job.
Restricted Access Data, including lockbox codes and unit-access instructions, is used only for authorized Job access. The beta should limit access to the assigned on-site technician and limited personnel with an operational need; use short, watermarked display windows where implemented; avoid including credential values in ordinary messages, exports, analytics, or AI prompts; log access events without logging the credential value; and automatically expire visibility when the access window or Job need ends. BLUNA schedules deletion of the credential value as soon as operationally practicable and in all events within 24 hours after Job closeout, cancellation, or reassignment, except where a specific incident or legal-preservation need requires narrower retained evidence.
BLUNA may retain address/unit-linked property records for authorized future service, estimating, maintenance history, quality, and support during the retention period below. BLUNA may also retain and use nonpersonal, aggregated, or deidentified building information for longer-term service analytics, benchmarking, pricing operations, quality improvement, and AI-assisted Platform features. Examples include paint colors, bulb counts/types, appliance makes/models, flooring type, fixture types, materials used, and generalized service history. Before information is used as a cross-customer deidentified dataset, BLUNA removes Restricted Access Data, resident names/contact details, identifiable resident imagery, and address/unit identifiers or other data reasonably capable of linking the record to a consumer or household. BLUNA will not attempt to reidentify information treated as deidentified and will maintain measures reasonably designed to prevent reidentification.
The Platform may use AI-assisted tools to organize, summarize, classify, route, or draft operational content. AI outputs may be inaccurate and users are expected to review them before operational reliance. BLUNA does not intend to use identifiable resident personal information or identifiable Job Photos to train a general-purpose AI model. The California beta is not designed to use automated decisionmaking to provide or deny housing, determine resident eligibility, set rent, make eviction decisions, or make comparable resident decisions. A feature that autonomously communicates with a user should clearly identify itself as automated or AI-assisted.
BLUNA uses the following beta retention schedule. These periods are selected to keep useful property/service information while limiting higher-risk resident and security data. A shorter period applies where the purpose ends sooner or a verified deletion obligation applies. A longer period may apply only when reasonably necessary for a documented legal, accounting, security, dispute, fraud, or preservation need. Where the CCPA applies, BLUNA also applies the reasonable-necessity and proportionality requirements of applicable California law.
| Data type | Retention approach |
|---|---|
| Account and ordinary contract records | Active relationship and five years after the last account or related Job activity, unless a shorter deletion obligation or longer documented legal need applies. |
| Address/unit-linked property and service record | Active Property Customer relationship and five years after the last related Job; after that, delete direct household/property identifiers or convert useful attributes to a deidentified dataset. |
| Restricted Access Data values | Only while needed for the current authorized access window. Remove visibility when the need ends and delete the credential value as soon as operationally practicable, and in all events within 24 hours after Job closeout, cancellation, or reassignment. If a specific security incident or legal hold requires preservation, restrict the retained evidence and do not restore routine access. |
| Restricted Access Data audit events | Three years. Retain who accessed the credential, when, for which Job/session, and relevant security metadata, but not the credential value itself. |
| Original unredacted Job Photos | 30 days after Job closeout. If a documented dispute, rework, security incident, chargeback, insurance claim, or legal hold is open, retain only until resolution plus 90 days. |
| Blurred/redacted Job Photos | Active Property Customer relationship and five years after the last related Job, then delete or deidentify unless a documented legal need requires longer. |
| Incidental resident information detected outside the retained redacted copy | Redact or delete as soon as reasonably practicable. Do not create a separate resident profile or retain unnecessary resident information merely because it appeared in a photo or Job record. |
| Transaction, tax, payout, and required Vendor compliance records | Ordinarily seven years, or the longer/shorter period required by applicable accounting, tax, payment, audit, or legal obligations. |
| Consent and SMS opt-out records | Four years after the last related message or consent withdrawal; suppression status may be retained longer as necessary to prevent unwanted messages. |
| Security and fraud logs not containing Restricted Access Data values | Ordinarily 12 months, with incident-specific records retained longer where reasonably necessary to investigate or document a security event. |
| Support and ordinary communications | Three years after the matter closes, unless incorporated into a Job, transaction, legal, or security record with a longer applicable period. |
| Deidentified or nonpersonal building data | May be retained for as long as useful for legitimate analytics, estimating, benchmarking, quality, and product improvement, provided it remains deidentified/nonpersonal and BLUNA does not reidentify it. |
BLUNA uses reasonable administrative, technical, and physical safeguards appropriate to the nature of the personal information it maintains. The beta should use least-privilege access, strong authentication for administrative accounts, secure transport and encrypted storage, vendor access limited to assigned Jobs, logging, controlled access to tax/payout records, and incident response. Restricted Access Data should receive additional controls: designated fields rather than free-form chat, short and technician-watermarked display where implemented, no routine export/copy, access-event logs that omit the credential value, automatic expiry, and prompt deletion after the access need ends. Job Photos should use automatic blur/redaction where technically feasible before long-term retention. No system is completely secure, and users must protect account credentials and promptly report suspected compromise.
Where the CCPA applies to BLUNA's processing of a California consumer's personal information, the consumer may have rights to know/access, correct, delete, and obtain information about certain disclosure practices; to opt out of sale or sharing where those activities occur; to limit certain uses or disclosures of sensitive personal information where the statutory right applies; and to receive nondiscriminatory treatment for exercising CCPA rights. The beta does not sell or share personal information for cross-context behavioral advertising.
Resident notice. The beta is not designed to collect personal information directly from residents and BLUNA does not sell or share resident personal information. Property Customers remain responsible for legally required resident notices, permissions, and lawful entry/photography authority. If BLUNA later begins collecting information directly from residents or communicating with residents, BLUNA will update the applicable point-of-collection notice, consent, and privacy controls before that feature is released.
A California privacy request may be submitted by emailing casey@bluprnts.io with "Privacy Request" in the subject line. BLUNA may need to verify identity and authority. An authorized agent may submit a request where permitted by law, subject to verification requirements. If BLUNA holds information solely as a service provider or contractor for a Property Customer, BLUNA may direct the request to the Property Customer that controls the information and will assist that customer as required by the applicable DPA and law.
The Platform is provided exclusively online for the beta. BLUNA will maintain a method for requests appropriate to its relationship and applicable law and will update this section if its collection model or statutory request-method obligations change.
The Platform is for business users and is not directed to children under 18. BLUNA does not knowingly solicit a child to create a Platform account. Users must avoid uploading identifiable information about minors unless it is genuinely necessary to document an authorized Job condition or incident and is legally permissible.
BLUNA may update this Policy as the beta changes. A material change will be presented through conspicuous notice appropriate to the affected data practice. If a new use would require consent or another choice under applicable law, BLUNA will obtain or provide that choice before using previously collected information for the new purpose where required. Privacy questions or requests may be sent to casey@bluprnts.io with "Privacy Request" in the subject line. The current version date is August 29, 2026.