VT: Lintelz Privacy Policy
Effective date: October 26, 2026 Last updated: November 2, 2026 (§2 and §5: what apps your company connects with an API key send us, and what we send them) Operator: Vivid Tokenz Studios, LLC ("Lintelz," "we," "us") Privacy requests: support@vividtokenz.io
1. Summary
Lintelz keeps permanent construction records for properties. We designed it so personal information stays out of those permanent records. What's permanent is public; what's personal is kept separately and can be deleted.
2. Information we collect
| Category | Examples | Where it's kept | Can it be deleted? |
|---|---|---|---|
| Account details | name, company, email, phone, trade or license description | Our account systems | Yes |
| Names you type for others | company names you give crew members | Your device only. The name an account signed up with is shown to other signed-in users on the same property. | Yes, by clearing it |
| Sign-in and keys | email or phone, one-time code (stored as a hash, never the code), session, a copy of your device signing key, locked with a key only our servers hold and handed only to a new device you approve or that waits 24 hours | Our account systems | Yes |
| Team membership | who invited you, your company and role | Our account systems; your activation on the public record stays (§4) | Yes |
| Property records | lot or job label, city, account IDs of the holder and crew, roles, phases, dates, work descriptions, dollar amounts a contractor chooses to show, notes, inspection results, lien waiver confirmations, file fingerprints | Public, permanent record (§4) | No |
| Approval and verification documents | business registration, license numbers, insurance certificates, owner identity documents | Our records systems, access-limited to the VTS records desk. Only "approved builder" and a "verified until" date are added to the public record. | Yes, the documents (subject to any legal retention period). Status history on the public record stays (§4). |
| Adjustments, disputes and damage reports | adjustment reasons, responses, hold reasons, damage descriptions and optional photos | Same as invoices: private to the builder and the contractor involved; never on the public record | Yes, subject to any legal retention period |
| Invoices and payments | invoice numbers, amounts, dates, who billed whom, payment method and reference, optional invoice file | Our private-records server, in access-controlled channels. Visible only to the builder and the contractor on each invoice. Never on the public record. VTS records-desk accounts can't open them in Lintelz (see §7). | Yes, subject to any legal retention period |
| Budgets, supplier invoices, lien waiver details, punch lists, documents (titles and fingerprints), warranty claims | as entered by the builder, crew or homeowner | Same private-records server; each is visible only to the people the app's rules allow (builder; builder and one contractor; crew; or homeowner after closing). Every version is kept. | Yes, subject to any legal retention period |
| Referrals | your referral code, which company's code you used, and the status of each reward | Our account systems; visible to you, the VTS records desk, and (name and status only) the company that referred you | Yes, subject to tax record retention |
| Banking details | name on the account, bank, routing number, account type and the last four digits of the account number, for VTS to send referral rewards | Our account systems; visible only to your company's owner and to the VTS records desk for payouts. We never store a full account number. | Yes |
| Notifications | your delivery choices and the messages we sent you | Our account systems and our email and text providers | Yes |
| From apps your company connects | job drafts (a job's name, city and phase names), work descriptions, inspection results and notes, and photos or reports, sent by an app your company gave an API key (such as Procore or Zapier), with that app's own ID for each | Our account systems and private-records server. Seen only by your company and, if your company passes an entry on, the crew member it's passed to. Street addresses, prices, phone numbers and email addresses are refused or removed when they arrive. Nothing is added to the public record unless a person on the job reviews it and adds it themselves (§4). | Yes, while it waits for review. What a person adds to a property record is then part of that record (§4). |
| Job site location | the lot's street address and its latitude and longitude. The builder types them, or taps Use my location in the app or on the website while standing on the lot, which asks your permission and reads the device's position once. | Our private-records server. Shown only to the property's current holder (the builder before closing, the homeowner after) and the crew working on it now; former crew and the builder after closing lose access. Only a fingerprint of the coordinates is added to the public record. | Yes, the address and coordinates. The fingerprint stays (§4) but can't be turned back into a location. |
| Files | photos and documents you add | Saved on your phone first, then in our private file storage (Cloudflare R2). Each file is shown only to the people allowed to see the record it belongs to; there are no public links. | Yes, except files that are part of another party's business records (for example, an invoice the other party relies on) |
| Change-order acknowledgments | the customer's typed name, email the link was sent to, time, IP address and browser | Our account systems; visible to the builder's owner and office | Yes, subject to the builder's record-keeping needs |
| Job credit purchases and plans | your plan and its changes, number of credits, amounts, dates, Stripe references (we never receive card numbers) | Our account systems and Stripe | Per tax law |
| Demo requests | name, company, email, phone if you give it, your role, how many homes you build, your message | Our account systems | Yes, on request. Requests that don't lead to an account are deleted after 12 months. |
| Terms acceptances, text consent and permission to record | which version of the Terms you accepted, when, IP and browser; when you agreed to texts or opted out; when a builder confirmed it may record a property (who, which job, when, IP and browser) | Our account systems | Kept while your account exists, plus 4 years |
| Billing | billing contact and payment details | Our payment processor, Stripe. We don't store card numbers. | Per the processor's retention rules and tax law |
| Usage and device data | pages viewed, errors, browser type, approximate location from IP | Our hosting and analytics providers | Yes, after 90 days or on request |
The only precise location we collect is a job site's, as described above: the device's position is read once, when you tap Use my location, and never in the background. We don't track where you are. We don't collect biometric data or information from children under 13. Lintelz is for people 18 and older.
3. How we use it
To run Lintelz, show the right records to the right people, prevent misuse, bill builders, meet legal and tax obligations, and improve the product. We don't sell personal data and don't use it for targeted advertising.
4. Public, permanent records
Property records are saved to a public, permanent record that anyone can read and no one — including us — can change or delete. This is what makes the history trustworthy. Because of this:
- We tell users not to enter street addresses or anyone's personal details in a record (Terms §6), and the app reminds them.
- Files and site coordinates are never saved to the record, only their fingerprints. A fingerprint can't be turned back into the file or the location.
- Account IDs in a record are random identifiers. Your name, email and phone are kept separately in our account systems and are not written to the record.
If you ask us to delete your data, we delete everything we hold about you (§2), but we can't remove entries already in a public record. Those entries will remain, linked to an account ID that no longer connects to your name in our systems.
5. Who we share it with
- Other users: anyone can read property records. Your account details are shown only to people working on the same property.
- Service providers that host and store data (Cloudflare), process payments (Stripe), and send email (Resend), text messages (Twilio) and, if you allow notifications in the phone app, push notifications (Apple and Google, to that phone's notification address) for us, under contracts limiting their use of the data.
- Apps your company connects: when your company's owner connects QuickBooks Online, Zapier or another app with an API key (such as Procore, Autodesk Build or Salesforce), we send that app what the Apps screen describes, at your company's direction: for QuickBooks, your company's invoices, payments and the customer, contractor and supplier names on them; for Zapier or another app, what the key allows: your company's jobs (name, city and phases), whether what the app sent was approved or declined (with the reason, if one is given), and the events your company has it listen for (such as a job opened, work logged, or an invoice or payment added), with the job's name and city, sent to the web address set up in that app. The app's own terms and your company's account with it govern what happens next. Disconnecting QuickBooks or revoking a key stops anything more being sent.
- Within VTS: the records desk sees account names, contact details, approval and verification documents and transfer requests. It does not have access to private records (invoices, budgets, punch lists, documents, claims).
- Legal reasons: when required by law, or to protect users or Lintelz.
- Business transfer: if Lintelz is sold or merged, under this policy.
5A. Text messages (SMS)
- Vivid Tokenz Studios, LLC texts you about Lintelz only if you agree, at sign-up or in your Profile, and only about your properties and account (sign-in codes, reviews, invoices, warranty and security alerts).
- We do not sell or share your SMS opt-in data or personal information with third parties for marketing purposes. Our text-message provider (Twilio) sends texts for us as a service provider (§5).
- Message frequency varies. Msg & data rates may apply. Reply STOP to opt out at any time, HELP for help.
6. Your rights
You can ask us to access, correct, delete or get a copy of your personal data, and to opt out of any sale or targeted advertising (we don't do either). Email support@vividtokenz.io. You can also ask to delete your account in the phone app (Account → Delete account) or on the website (Account → Profile → Delete account); this page explains how, including without the app, and what we keep. We respond within 45 days, and may extend once by 45 days if we tell you why. If we decline a request, we'll explain why and how to appeal; you can appeal by replying to our decision. If your appeal is denied, you can contact the Texas Attorney General.
Requests are free up to twice a year.
7. Security
We use reasonable safeguards for the data we hold. They include:
- Encryption in transit (HTTPS) and at rest on our hosting provider (Cloudflare).
- Sign-in codes that expire in 10 minutes, with limits on how many can be requested and tried each day.
- Device confirmation. A sign-in code alone doesn't open private records, team, billing or banking on a new device. The device must also get your signing key: you approve it from a device where you're signed in, use your passkey, or it waits 24 hours. You're notified when a new device asks and when it gets in, and you can stop it, or sign out other devices, from Security in your account.
- Your signing key is kept on your device, locked to that browser or phone. The copy we hold is locked with a key only our servers have, and is handed only to a device you approved or that waited 24 hours. A small number of VTS administrators with access to both could technically use it; we limit that access the same way as private records, below.
- Private records and files are split into channels and served only to the people each one is for. VTS records-desk accounts can open only VTS's own channel in Lintelz. Private records aren't end-to-end encrypted: they're stored on our hosting provider, and a small number of VTS administrators with direct database access could technically see them. We limit that access to running and repairing the service and to legal requests.
- Uploaded files are checked to be real photos or PDFs and are never served as web pages.
No system is perfectly secure. If a breach affects your personal data we'll tell you as the law requires.
8. Retention
We keep account details while your account is open and for 12 months after, unless you ask us to delete them sooner or the law requires longer (for example, tax records). Public records are permanent (§4).
9. Changes
We'll post changes here and notify users of material changes at least 30 days before they take effect.
10. Contact
Vivid Tokenz Studios, LLC · 5473 Blair Road, Ste 100 #178864, Dallas, TX 75231 · support@vividtokenz.io