Verilux Privacy Notice

Effective date November 19, 2026
Version 1.0

Away Home, Inc., doing business as Verilux (formerly Away Home), is a Michigan corporation. We provide temporary housing and related claim services in the United States for policyholders and households displaced by insured property losses. This notice covers how we handle information for those services, our public websites and our internal case-management system, which we call the CRM. The signed Service Agreement governs our services. Any Assignment of Benefits applies according to its own terms.

For privacy requests, email privacy@veriluxmi.com. For other questions, email support@veriluxmi.com.

Information we handle

We handle the following information to arrange housing, manage cases and bill for our services.

  • Case, policy and claim information, including loss addresses, policy and claim numbers, insurance details and contact information for policyholders, household members, carriers and adjusters.
  • Accommodation needs and housing stays, along with correspondence, documents, receipts and billing amounts. At CRM launch, receipts are kept in our business Dropbox, not in the CRM.
  • Name, email address, phone number and message when you use the contact form at veriluxmi.com/contact or awayhomemi.com/contact.
  • Staff account, sign-in, security and activity information. Signed staff policy acknowledgments include the staff member’s name, policy version, date and signature.

An adult may give us a household member’s name and age, including information about a minor, so we can arrange housing for the household. We provide services through adults. The CRM is for authorized staff and has no client accounts.

We use claim information to communicate with the people involved, review documents and receipts, prepare forms and obtain signatures. At CRM launch, staff view receipts in our business Dropbox rather than in the CRM. We use staff records to manage access, review activity, protect the CRM and resolve problems. We use website contact-form information to respond to the inquiry.

Please don’t send Social Security numbers, bank or card numbers, or medical details unless we ask for them. If you send them, we use them only as needed for your claim and store them with your case records.

QuickBooks

We use Intuit QuickBooks Online for accounting. Staff enter billing details in QuickBooks separately from the CRM. The CRM’s optional QuickBooks connection is off at CRM launch.

If we enable the connection later, an authorized user will grant the CRM access through Intuit to the Away Home, Inc. QuickBooks company. The CRM will use authorization tokens and a company identifier to maintain the connection. The connection is designed for staff-requested reads. Bookkeeping entries and changes are made separately in QuickBooks.

When staff request information, the server receives QuickBooks records and extracts the fields used for the connection. QuickBooks responses may contain additional fields while the server processes them. The connection is designed to use these fields:

QuickBooks recordsInformation used
CompanyQuickBooks company identifier, company and legal names, and country when provided.
CustomersCustomer identifier, display name, active status and a parent-customer reference when provided.
InvoicesInvoice identifier and number, customer reference, invoice and due dates, currency, total, balance and linked transaction references.
PaymentsPayment identifier, customer reference, date, currency, total, unapplied amount, and amounts and references for payments applied to linked transactions.

The connection is intended to help staff review billing for cases. Staff choose the QuickBooks customer for a case and assign invoices when the customer is linked to more than one case. The planned view shows billing amounts on the relevant case screens and may temporarily reuse a previous read for about 15 minutes. Confirming that a payment cleared the bank requires separate evidence.

For help disconnecting QuickBooks, email support@veriluxmi.com. Disconnecting affects the CRM’s future access. Entries in QuickBooks remain in QuickBooks, and copies already in our case records follow the applicable retention rules below.

Service providers and other recipients

ServiceHow we use it
SupabaseCRM database and staff sign-in. The CRM does not store uploaded documents or receipts at launch.
NetlifyCRM hosting and delivery, including server functions.
SquarespaceHosting and site analytics for veriluxmi.com and awayhomemi.com. Contact-form submissions are stored as contact profiles in our account without automatic expiration.
Google WorkspaceBusiness email, including contact-form submissions delivered to our business mailbox.
SignWellElectronic signatures through SignWell’s website. SignWell processes the filled Service Agreement and Assignment of Benefits PDFs, including signer names and email addresses, policy and claim numbers, loss address, Coverage D details and other fields in the form. Its signature audit trail includes signing times and IP addresses.
Intuit QuickBooksAccounting and, if enabled, the connection described above.
DropboxBusiness storage for case documents and receipts at CRM launch, and separate business copies of signed agreements and SignWell completion certificates, organized by year and job.

We provide carriers and adjusters with claim and billing information, and hotels, Airbnb and other housing providers with details needed to place a household. We also share information with our accountant for accounting and with other recipients when disclosure is required by law. We do not sell personal information or share it for advertising.

Storage, cookies and staff access

Our Supabase CRM database and our Netlify CRM server functions are in Ohio, United States. Netlify uses a global network to deliver CRM pages. Squarespace hosts our public websites. Service providers may process information in other locations.

Squarespace uses cookies on both public websites, including cookies for site analytics. Non-essential cookies are restricted unless you allow them. Use “Manage cookies” on either site to change your choice. You can also manage cookies through your browser. Squarespace Cookie Policy

The CRM uses browser session storage to keep staff signed in. It uses no advertising, analytics or tracking. Browser behavior can affect how long a session persists. Our hosting providers also keep records for security and system operations.

We limit CRM access to authorized staff. We can suspend or remove accounts, and staff must protect their credentials and use information for authorized work. At launch, case documents and receipts are kept in our business Dropbox and SignWell, not in the CRM. Our backup schedule is described below.

Retention and deletion

We keep information for the periods below. We pause deletion of relevant records while a dispute, claim or legal request places them on hold.

RecordHow long we keep it
Website inquiries that do not become a caseWe delete them within 12 months from Squarespace and our business email. We review these inquiries for cleanup at least quarterly.
Website inquiries that become a caseWe keep them with the case record.
Case records, accepted documents, receipts (kept in Dropbox at CRM launch), and case activity historyThe life of the claim plus seven years after closure.
Rejected uploadsNot applicable at CRM launch; the CRM accepts no document uploads. If uploads are enabled later, we will delete rejected uploads within 30 days of rejection.
Quarantined uploads we never acceptNot applicable at CRM launch. If uploads are enabled later, we will delete them within 30 days of upload.
Provider sign-in, security and system logsThese follow the provider’s retention periods.
ExportsWe delete them within 30 days of creation. An export included in a case file follows the case schedule.
Signed agreements and completion certificatesThe life of the claim plus seven years after closure for case-file and Dropbox copies. We aim to keep SignWell copies for the same period, subject to SignWell’s storage and deletion options.
Signed staff acknowledgmentsWhile the staff member has access and for seven years after access ends.
Published versions of this notice and the staff policyWe keep them permanently with the version number and effective date.

We perform deliberate cleanup at least every two weeks for records subject to the 30-day deadlines. We correct case records by voiding or archiving the original with its history. Our backup schedule calls for daily encrypted offline copies of the CRM database. Documents and receipts kept in Dropbox are not part of those offline copies; they rely on Dropbox’s own file version history. We keep those backups for 30 days and keep backups taken before major system changes for the same period. Deleted information can remain in those copies until the backups expire. Supabase also keeps daily database backups for seven days.

Website inquiries received before this notice took effect follow the same rule: when this notice is published, we delete pre-launch inquiries older than 12 months that did not become a case, from Squarespace and our business email.

Unsigned or cancelled forms are kept with the case when one exists; otherwise we delete them within 90 days. We delete temporary and duplicate files and local downloads within 30 days. We disable staff accounts the day access ends and keep the account record for seven years after access ends. Business email about a case is kept with the case for the life of the claim plus seven years; other business email follows our general business-records practice.

AI document intake and email automation

AI document intake and automated receipt-mail intake are off at CRM launch. Our ordinary business email continues. We do not send client information to OpenAI through the launch CRM workflow.

If we later enable document intake through the OpenAI API, we plan to send only selected pages so the service can suggest details for a case. Staff will check the source before saving a suggested value as a confirmed case detail. The planned workflow excludes QuickBooks and other accounting data from what goes to OpenAI.

Under OpenAI’s standard API policy, OpenAI may retain submitted content and responses in abuse-monitoring logs for up to 30 days. It may retain them longer if the law requires it or to help prevent harm. This retention applies separately from settings that control saved application data. Features such as uploaded files and saved conversation state can keep separate copies under their own rules, in some cases until deletion. OpenAI does not use API content to train models by default. Its data controls and retention arrangements depend on the features and settings used. OpenAI API data policy

Your privacy requests

Email privacy@veriluxmi.com to ask to access, correct or delete your information. We verify your identity before acting and respond within 30 days. We honor access and correction requests. We honor deletion requests unless we need to keep the information for an open claim, billing, a legal hold or an applicable retention requirement. You may have additional rights under applicable law.

To verify a request, we reply to the email address we have on file for the case or ask you to confirm two case details. Someone acting for you must provide your written permission. We send requested information through an expiring secure link. We keep a record of each request for two years.

Changes to this notice

The official notice is at veriluxmi.com/privacy. It covers our former site, awayhomemi.com, which we also operate. We post updates with a new version number and effective date. We email active clients before material changes take effect.

The former site’s privacy page redirects to this notice. We archive a copy of every published version.