Privacy Policy
QRBuilding is operated by Serenae Meridian Group LLC. This policy explains how information is handled through our building-management workspaces, resident and staff hubs, public pages and private demo sandbox.
Last updated: November 1, 2026
Optional AI Operations
When an authorized portal user submits an AI request, QRBuilding sends the question and selected permitted building summaries or record fields to OpenAI to generate an answer. Building and role permissions limit retrieval; the current portal page does not limit which permitted workspaces can contribute. Uploaded file contents and private conversations are not currently read by this feature. Do not enter secrets or information you are not authorized to share.
AI questions, answers and editable drafts are encrypted in QRBuilding storage, private to the requesting account and available for up to 90 days while the account retains source access. Financial usage and purchase audit records are retained separately. Requests ask the provider not to store the response as application state; provider security, abuse monitoring and legally required retention may still apply. Generated text can be inaccurate and must be reviewed before use or disclosure.
Who we are
Serenae Meridian Group LLC operates the platform and handles account administration, subscription, security and support information. Building management determines what building and resident records it submits, the people it authorizes, the workflows it configures and the content it publishes. QRBuilding processes those building-controlled records to provide the service and carry out authorized instructions.
Information comes from account holders, residents, staff, contractors, building imports and connected service providers. The information involved depends on the features enabled for the building and the actions you take. Building management may have its own privacy notices and responsibilities.
Information you provide
Management accounts include contact and organization details, sign-in credentials, building information and staff invitations. We also process content you upload or create, such as notices, contact directories, events, images and service links.
Maintenance can keep encrypted drafts, processed attachments, pending staff updates and selected task details in this browser, scoped to the account and building. Offline access lasts at most eight hours and ends sooner when the authenticated session expires. Sign-out or ending resident verification locks saved work until the original user reconnects. Task copies expire after eight hours; pending updates older than seven days require review and are not silently deleted. Unsent work remains until accepted or explicitly discarded, within a 30 MB allowance and 100 queued updates per account/building. Browser or device storage may be cleared or evicted. Previously opened data cannot learn of access revocation while disconnected; do not hand an unlocked session to another person.
When building management creates an administration or staff invitation, QRBuilding sends the invited email address a private account-setup link. Links expire after seven days and acceptance requires authentication or setting a password. We retain invitation delivery and suppression records to prevent duplicate or unwanted setup messages. Opening an invitation link does not create an account or accept it.
An unfinished marketplace post can be kept in this browser tab for up to two hours so text and prepared photos can be recovered after using the camera or reloading. Submitting or discarding the draft clears this recovery copy. Forgetting this device ends verification and preserves the draft. A browser may remove its own storage sooner.
Resident marketplace and amenity requests may include your name, contact details, unit number, requested times, listing text and photographs. Quote requests include the contact and building information you enter. Provide only information you are authorized to share.
Operational records may include visitor and guest-pass details, arrival and departure times, package labels and collection records, maintenance requests, asset and inventory activity, move requests, staff assignments and attendance, vendor details, workflow forms, messages and attachments. These records can connect a person, unit, staff member or contractor to a specific building activity.
If management enables a staff clock-in location check, the device requests permission to share a fresh location and accuracy reading for that clock-in. The service checks it against the configured building area and retains whether the check was completed, not the staff member’s exact coordinates. This does not continuously track the device. If location is unavailable, staff can ask management to record attendance.
Public building pages and private requests
Resident hub URLs and building QR codes are public. A link or QR code does not verify that a visitor lives in a building. Published notices, public directory entries and events can be viewed by people who have the link. Marketplace and room browsing may require contact confirmation when building management enables that access mode.
Marketplace contact details are shown with the approved listing to viewers permitted by the building’s selected access mode. Unit numbers remain management-only. Booking request contact and unit details are available to authorized management; public availability does not disclose those details.
Private workspaces and resident or unit overviews display linked information according to the viewer’s current building access and permissions. They are separate from the public directory. Building management controls publication to resident pages and lobby displays. Review the intended audience before publishing or downloading material.
Resident profile, emergency contacts and saved reading
Verified residents can propose corrections to their name, phone number or email address. QRBuilding stores the proposed details, request status and management’s review response. Management must approve a correction before it replaces the approved contact record; a proposal cannot assign a unit, establish occupancy or grant access. Withdrawing or declining a request does not erase its review history.
Residents can save up to three emergency contacts, including names, relationships and phone numbers, after confirming permission to share them with building management. These details are encrypted and available to authorized building personnel through the resident overview. Saving a contact does not send a message, place a call or enroll that person in communications.
Saved notices, saved document links and notices explicitly marked as read are stored against the verified contact for that building. These preferences are encrypted and are not exposed as management read receipts. Marking a notice read applies to its reviewed version; it does not constitute a signature, legal notice acknowledgement or consent to new terms. A saved reference does not preserve access to content that management unpublishes or your current access no longer permits.
Incident and shift-handover evidence
Authorized staff can record incidents, shift handovers, key or equipment custody, follow-up actions and associated people or locations. Supported PDF and image attachments are stored with the specific record. Original attachments are retained in encrypted storage and may include personal details or metadata contained in the uploaded file.
Access to a restricted incident and its files requires the corresponding permission; ordinary workspace access does not make every incident visible. Search and downloads follow the same building and record permissions. Include only the information needed for the operational purpose, and avoid unnecessary sensitive details about residents, staff or visitors.
Optional resident contact confirmation
Building management may maintain a private approved list of units, phone numbers, email addresses and optional resident names or notes. Authorized staff can import, review, approve and update that list. It is separate from the public building directory and is not exposed as a resident search directory.
The private resident list records per-unit resident/owner relationships and email or SMS preferences as Yes, No or Not recorded. Building communication requires approved contacts with a Yes email preference and documented permission. Management may send an expected or resident-requested subscription confirmation to a No or blank contact; opening the link makes no change, and explicitly subscribing sets Yes. Invitations expire after 24 hours and are limited. Opt-out links set No across matching building email records and stop future building communication and separately enrolled visitor alerts. Existing delivery blocks are not cleared by consent, imports or invitations. The legacy SMS design preview does not collect building-alert consent. The separate Building SMS alerts action requires the resident’s own verified-phone enrollment and remains disabled until launch readiness.
When a feature requires confirmation, you enter your unit and one approved phone number or email address and explicitly request a link. We privately match those details and, when eligible, send a single-use link that expires after ten minutes. SMS is limited to U.S. phone numbers. The response does not reveal whether a unit or contact appears in the list. You do not create a resident account.
We use scoped cookies, confirmation times, delivery status and limited security records to provide access and prevent abuse. A Contact confirmed label tells management that a person accessed an approved contact channel; it does not establish identity, ownership, occupancy or voting eligibility. Contact details from the private list are not automatically published in a listing or booking request.
A confirmation message contains the building and feature name and a temporary link, not your request text, photographs or private directory notes. Protect your inbox and phone and do not forward the link. SMS is not end-to-end encrypted; carriers and message providers process the information needed for delivery. Amazon SES may scan email content to prevent abuse. Requested confirmation and building communication emails do not include open or click tracking. Building email may contain shared public branding images and a Hub QR or calendar link. Providers and email clients may load those images to display the message. Communication history is retained for 90 days; unsubscribe links remain usable for up to 180 days. Minimal consent evidence is retained while the building contact record is maintained. Removing a saved design does not recall already delivered email images.
Where enabled, resident-requested visitor alerts and opted-in service updates use the approved contact, selected categories and current request or service status. These preferences are separate from one-time verification. You can change available preferences in the resident hub or use the message’s unsubscribe control. Delivery records, complaints and suppression information support those choices and prevent inappropriate retries.
Optional browser notifications require device permission and enrollment. QRBuilding stores the push-service address, notification keys, device association and selected categories. The browser’s push provider processes delivery, and notifications may appear on a device’s lock screen. You can disable them in the hub or browser settings. A saved hub shortcut alone does not authorize notifications.
Projects and contractor records
Where Projects is enabled, building management, participating residents and assigned contractors can submit scope, estimates, work updates, messages, photographs, verification documents and entry arrangements. Access depends on the person’s assignment and permissions. Keep access codes, identification documents, health information and unrelated personal details out of work descriptions and attachments.
Electronic signing records the exact document revision, the signer’s stated capacity, consent wording, authenticated account or approved-contact session, and signature time. A confirmed contact channel does not establish ownership or authority to order work. Account invitations and project-tracker invitations grant different access; their links expire after 48 hours. Document-upload invitations expire after seven days. Opening a link does not sign a record or authorize work.
The current Projects implementation preserves issued plans, signatures, messages, evidence, approval history and financial records without automatic deletion. A redaction restricts ordinary viewing but retains the underlying evidence. Link expiry, withdrawal of electronic signing, removal from a project and account closure do not erase those records. Ask building management or the privacy contact below for access, correction, a paper copy or a deletion review. Retention exceptions must be assessed for the particular records; restricted access is not deletion.
Where records-disposition controls are enabled, removal of selected primary work content requires a reviewed scope and preservation checks. Approval of a deletion request is not confirmation that removal has occurred. Audit receipts, independent recovery records, backups and copies previously downloaded or delivered can have separate retention and handling requirements.
QRBuilding processes building-controlled project records to provide the service and assist management with authorized requests. We also handle account security and delivery records for service operation. A privacy request does not require a new account. You may contact the same privacy address to appeal a refusal; include the prior request reference and the reason for your appeal. Applicable legal rights and response deadlines are unaffected by these product controls.
Finance, receipts and accounting exports
Finance processes account and fund classifications, journal entries, budgets, receivables and payables, counterparties, payment references, bank-statement rows entered or imported for reconciliation, and supporting documents. Linked inventory, staffing and project records can supply costs and source references. These records may contain resident, employee or vendor information, including amounts owed or paid.
Receipts and supporting documents are attached to the specific purchase or income item. QRBuilding retains their originals, reviewed extracted fields, links to accounting entries, and dated evidence of later uploads. Sensitive narratives and files use application encryption; dates, amounts, account classifications and other operational metadata support reporting and access checks. Posted entries, finalized reconciliations and their audit evidence are retained; a correction or reversal does not erase the original record.
Accounting exports can contain names, descriptions, amounts and references from the selected records. Excel/CSV and accounting-system mapping profiles produce files for an authorized user to review and transfer. They do not automatically send data to QuickBooks Online, AppFolio or ClickPay or authorize a connection to those services. Protect downloaded files and review the receiving system’s requirements and privacy practices before importing them.
Community fund contributions
Published campaign purposes, beneficiaries, terms, dates and aggregate progress are visible on the building page. Contributions require current approved-contact access. We retain the campaign version, amount, consent wording, resident/contact and unit references, anonymity choice, payment-provider references and confirmation, refund or dispute status. Private receipts are available to the verified contributor; authorized ledger readers can review the building’s contribution records.
Choosing anonymity hides your name and unit in the campaign ledger and its exports. It does not make the payment anonymous to Stripe, the receiving association’s payment-account operators or authorized processing and support functions. The association receives funds directly through its connected Stripe account. QRBuilding does not store complete card details. Campaign and payment evidence is retained after closure; ending verification does not erase it.
Governance and meeting materials
When management enables resident guest meetings, a separately reviewed title, description, agenda labels and optional guest meeting link are available to verified residents during the live session. Guest access does not include the private packet, source attachments or member ballots. Recent connection records identify board participants and resident guests to authorized board readers; guests see board participant names and a guest count. Connection indicators expire after 90 seconds without a response and do not establish attendance. Questions and moderator responses are retained as meeting records and are visible only to the submitting resident and authorized moderators. Ending a session removes live guest access and connection indicators; it does not erase retained questions or decisions.
Published agenda reviews and questions are attributed to the authenticated account and packet version. A live session retains selected eligible accounts, configured rules, moderator actions and each member’s final ballot for that round. These are named ballots, not secret ballots; closed results are available to authorized session readers and appear in the meeting motion register. Project approvals and justified exceptions retain the reviewed scope and actor. Changes in access are checked on subsequent requests.
Governance can combine selected building records with agendas, summaries, presentations, minutes, recorded motions and votes, action assignments, attachments, and risk, insurance, contract or reserve-planning registers. The selected source records, reporting period, capture time and included permissions accompany the captured meeting material.
Captured versions, publication decisions and export evidence are retained for review. Publishing a package inside Governance makes it available to authorized readers with the required source permissions; it does not automatically create a public page or email it to residents. PDF, Word and PowerPoint exports contain the selected material and applicable attachments or attachment references. A later access change cannot recall a copy someone already downloaded or distributed.
Document reading and generated summaries
Receipt, package-label and contractor-document reading can extract text or suggest fields from a file or camera capture. Browser-based text recognition processes the selected material on the device; saving or uploading sends the information and files needed for the chosen workflow to QRBuilding. Review suggestions against the original before applying them.
The current meeting-content generator uses selected authorized building records and predefined summary rules. It does not send those records to an external generative-AI service. Generated summaries, charts and discussion prompts remain subject to human review and the recorded source coverage.
How information is used
Information is used to operate accounts and resident hubs, publish building content, manage permissions and workflows, process requests, prepare reports and meeting materials, maintain accounting and operational evidence, provide subscription features, prevent abuse and respond to enquiries. Activity histories record relevant actors, actions and times for review and accountability.
For weather, management can choose a city or explicitly share a browser location. The selected coordinates are saved as the building weather location. Browser location is requested only when that option is used; it is not tracked continuously. A configured forecast or location provider receives the information needed for that lookup.
The service records usage events such as page views and feature interactions for building analytics. Hosting and analytics services also process technical request information to operate and measure the website. Authentication cookies and browser storage support sign-in, preferences and demo sessions.
Service providers and external links
Hosting, database, file-storage, analytics and billing providers process information needed to supply their services. QRBuilding uses Vercel hosting and analytics, Neon-hosted PostgreSQL and configured storage services, and Stripe for subscription checkout and billing records. QRBuilding does not store complete payment-card details. Where a separately enabled building-payment flow uses a payment provider, that provider also processes the submitted payment information.
Amazon SES processes enabled resident email. The QRBuilding toll-free SMS programs use Twilio when separately approved and enabled; this release does not activate the earlier AWS SMS transport. Messaging providers and carriers process destination numbers, message content and delivery or opt-out feedback as needed to supply messaging. Processing may occur outside the building’s location. U.S.-only SMS describes supported destination numbers, not a promise that all processing stays in the United States.
SMS opt-in and consent information is not shared with third parties or affiliates for marketing or promotional purposes. Necessary messaging service providers process this information to deliver requested verification and separately opted-in building alerts, manage suppression, prevent abuse and provide support.
Building payment links, websites and document links can lead to services controlled by other organizations. Clicking a telephone or email link hands the number or address to your device’s calling or email application. Their privacy practices apply when you use those services. Information may also be disclosed when required by applicable law or to address security, fraud or legal claims.
SMS consent, preferences and delivery records
QRBuilding’s toll-free SMS numbers are (888) 906-6886 and (855) 811-8208. Requested verification and optional building alerts depend on separate registration approval and launch readiness. Program and consent information is available at /sms and /sms/opt-in.
For requested verification and optional building alerts, we store the normalized phone encrypted at rest, a protected matching digest, building and resident/contact references, program, consent status and times, exact consent page, versioned wording and its hash, affirmative action and subsequent withdrawal or re-enrollment events. We retain provider message identifiers, delivery status and suppression events. SMS consent evidence does not store raw verification tokens or IP addresses and user agents; separate minimized verification rate-limit digests protect against abuse.
Authorized support personnel can inspect a building-scoped audit history; staff cannot enroll residents or clear provider STOP blocks. Web alert withdrawal stops that building’s alerts. Provider STOP can cover verification and alerts across the sender or service. Phone changes or lost roster eligibility invalidate affected enrollment. Ask support about access, correction or deletion; consent and suppression evidence may be retained to honor preferences, investigate disputes and meet applicable obligations. A universal deletion period is not promised. SMS is not end-to-end encrypted.
Hub shortcuts and remembered verification
Adding a hub shortcut is optional. Services assigned to the same building email control can share a new verification; earlier feature-only sessions keep their original scope. When you opt in, a secure cookie can remember this browser or app for the period shown, up to seven days from email confirmation. Opening the hub does not extend that deadline. A browser and a Home Screen app may keep separate storage. Forget this device revokes verification here and leaves the icon, drafts, posts and bookings in place.
Shortcut measurements use a random identifier scoped to a building, app display mode, event type and time. Reports distinguish browser-reported additions from observed app opens and estimate app instances rather than people. Email addresses, units and verification credentials are excluded from these measurements. Clearing storage or blocking signals affects coverage. Events and inactive instance identifiers are scheduled for deletion after ninety days; active identifiers remain while used. Rate-limit digests are separate security records.
Retention and your choices
Building and account records support the ongoing service. Archiving or expiring a notice or listing removes it from public display but does not necessarily delete its management record. Downgrading a plan preserves saved content, which may become read-only above the new allowance.
Private contact fields and import payloads use application encryption. Raw import files are cleared after approval or discard and are scheduled to expire after 24 hours. Temporary link/session and delivery records have bounded cleanup schedules; aggregate usage and request confirmation history may be retained longer. Archiving a resident contact revokes access but does not permanently delete that record or existing request evidence. Ask management to correct an approved contact, stop unwanted confirmation messages or help you use an alternative contact. Hard bounces and complaints may suppress further delivery. Contact us about a deletion request.
Contact support@qrbuilding.com to request access, correction, a copy or deletion of information associated with you, or to ask about rights available under applicable law. Include enough context to identify the building and request, but do not email passwords, verification links, full payment-card details or unnecessary identity documents. We may need to verify your identity and authority before acting. Building management should handle changes to the content and resident requests it controls; contact us if you need help identifying the appropriate route. You do not need to create a new account to make a privacy request.
If you disagree with a privacy-request decision, contact the same address with the request reference and reason for review. Applicable rights, appeal routes and response deadlines are not limited by the product’s self-service controls.
Account and transaction records may need to be retained for ongoing service, dispute resolution, security or legal obligations. The sandbox is temporary and intended for fictional information; do not enter real resident or sensitive personal data.
There is no single automatic deletion period for every workspace. Operational histories, incident evidence, posted financial records and captured governance packages may remain after a task is closed, a person’s access ends or an account is cancelled. Deletion reviews consider the purpose, applicable retention duties, preservation holds, security needs and copies in backups or external systems. Access expiry, archiving and removal from public view are distinct from permanent deletion.
The private demo is normally available for a 30-minute session and uses a fictional 54-unit condominium. Demo buildings and temporary access are isolated from customer accounts; ending or expiring the session prevents continued access. Demo guide measurements record progress and interactions without resident names or contact details. Changes made in the demo do not transfer to a new account.
Questions and changes
Contact Serenae Meridian Group LLC at the support email below for privacy enquiries. This policy may be updated as the service changes; the date above identifies the latest version. Where applicable law requires notice or consent for a change, that requirement still applies.