Privacy Policy
Last updated: November 2026
1. Who I Am and What This Policy Covers
DBJ Technologies LLC is a Texas limited liability company, and you can reach it at joshua@dbjtechnologies.com. In this policy, “I” and “me” mean DBJ Technologies.
This policy covers this website, Pathlight, my business phone line, Canopy (the business system I build and operate) and the DBJ Canopy mobile app. When a client runs its own Canopy workspace, the client controls the information in it, as section 7 explains.
2. Information I Collect
When you use the contact form, I collect what you enter: your name, email address, phone number (optional), company name (optional), project type, budget range and message. If you agree to receive texts, I also record when you agreed and the wording you agreed to.
When you request a Pathlight scan, I collect the website address, your email address, and the business name and city if you give them. When you use the chat assistant on this website, I keep the conversation, the page it started on, your browser details and any email address you write in it.
Canopy, which I run on dbjtechnologies.com, holds my own business records about clients, prospects and the people I correspond with. They include names, companies, email addresses, phone numbers, addresses, notes, deals, quotes, invoices and payment records, files, email mirrored from my own connected mailboxes, calendar events, text messages, call logs and recordings, business-card photos, and the history of my chats with Canopy's assistant. Canopy also keeps audit and security logs and the first-party visitor analytics described in section 12.
This information comes from the people themselves when they contact me, from business cards and events, from referrals, and from public websites and business listings.
Your IP address is handled in a few different ways. The website analytics never store it; they turn it into a one-way hash with a salt that changes every day and discard it at once. Every request passes through my hosting provider, which needs the address to deliver the page. The contact form keeps the address and your browser details with your message, and the chat assistant keeps a hashed form of the address to limit abuse. The bot check on the forms and the rate limiter receive it to stop abuse, and the rate limiter holds it for up to two days. In my own Canopy, the security log keeps the address and browser details for 90 days, and the record of sign-ins keeps them with each sign-in.
3. How I Use Information
I use information to answer you, to provide and support the work I am engaged for, to send the Pathlight reports and follow-ups described in section 4, to run and secure my systems, and to keep the business and tax records the law requires.
I do not sell or rent personal information, I do not share it with anyone for their marketing, and none of it goes to an advertising network.
4. Pathlight Website Scans
Pathlight scans a website and writes a report on it. Anyone can request a scan by entering a website address and an email address. I may also scan a business's public website myself and email the report to a contact I already have at that business.
The report email is followed by up to three follow-up emails. Every one of these emails carries an unsubscribe link that works, and unsubscribing stops the rest.
A scan keeps its results, including a copy of the public pages it read, screenshots and the analysis, and a chat on a report is kept too. Each report opens at its own unlisted address, which search engines are asked not to index, so anyone who has the link can open it.
The scores, estimates and recommendations in a report are information, not professional advice, and section 7 of the Terms of Service covers what they do and do not promise.
5. Calls to My Business Line
Calls to my business line, (682) 325-8324, are answered by an automated screening assistant. Twilio turns the caller's speech into text, and the assistant, which runs on Anthropic's Claude, uses that text to learn who is calling and why, and to route the call.
Calls and voicemails may be recorded and transcribed. The call log keeps the calling number, the time and length of the call, what the caller told the assistant, a short summary, and any recording, voicemail and transcript. Texts to and from the same number are covered in section 9.
6. AI Features
These features run on Claude, the AI model made by Anthropic, through Anthropic's API: the assistant in Canopy and Canopy's other AI features, such as summaries and drafts of records, lead scoring, help importing a spreadsheet and reading business-card photos; the analysis in Pathlight reports and the chat on a report; the chat assistant on this website; the statement reader in one of my free tools, which sends the uploaded statement to Anthropic and keeps no copy; and the live screening of calls to my business line.
Each feature sends Anthropic what its request needs, such as the text of a record, screenshots of a scanned website or a photo of a business card. Anthropic provides its API under commercial terms that do not allow it to train its models on that data, and I do not use client or visitor data to train any model.
In a client's Canopy workspace, every AI switch starts off. The assistant can change records only after someone who manages that workspace turns its actions on, and every action it takes is recorded in the workspace's audit log. Small changes that can be undone, such as adding a task or a note, run without a further click. Deletes and full exports always wait for a person to confirm them. Email and invoices also wait for a person to confirm them, unless a manager of that workspace deliberately turns that confirmation off.
7. Client Canopy Workspaces
Each client that subscribes to Canopy gets its own workspace with its own database. The information in it belongs to the client, the client controls it, and the client's signed agreement with me governs it. I process it only to provide and support the service.
The service providers in section 10 are the ones that can handle that information, each only where the client's workspace uses it. A request about information in a client's workspace goes to that client, since the client decides how it is used.
8. The DBJ Canopy Mobile App
DBJ Canopy is the iOS and Android app for Canopy, the business system I build and operate. This section covers the app.
What the app collects. The email address of the person signing in. It arrives from Google or from Apple when you sign in with them in the app, or from your Canopy install's own sign-in page when you sign in there (with Microsoft or an emailed sign-in link, for example), and it is used to identify you to your own Canopy install and for nothing else. The app never receives or stores your Google, Apple or Microsoft password.
What the app keeps on your device. A sign-in token, a refresh token, the expiry of the first, the email address you signed in with and the address of the Canopy install you signed in to, all held in the operating system's own secure storage (the Keychain on iOS and the Keystore on Android). Since version 2 the app shows your Canopy install's own pages, so it also keeps what a browser would keep for them: that install's sign-in cookie, the pages' own small store of settings, and a short-lived cache, all in the app's private storage; your choice of a light or dark look is kept too. A file you open or export from Canopy, such as an invoice or a spreadsheet, is written to the app's cache so the share sheet can offer it. Version 1 of the app instead kept the latest Today and Pipeline summaries (counts, dollar totals, stage and deal names) in the app's own storage, which the operating system encrypts. Signing out removes all of it.
What your Canopy install keeps about your sign-in. For each device you sign in from, it keeps the sign-in method (Google or Apple in the app, or the install's own sign-in page), the device name, platform and app version the app sends, and when the session was created and last used. Canopy also keeps a security log of account activity, so that questions such as whether a lost phone was used have an answer. It records each sign-in, sign-out, change to notifications and account deletion, with the email address, the device details sent at sign-in, a short fragment of the notification token, and the IP address and user agent of the request. This security log keeps the IP address as it arrives, unlike the website analytics, and section 2 lists every place an IP address is kept. The IP address and user agent are cleared from each entry after 90 days, and entries are deleted after 13 months, except those about invoices, quotes, proposals and subscriptions, which are kept seven years for tax records. Deleting the app account does not remove these entries sooner. Sign-ins and deletions are also noted in Canopy's operations monitoring with the email address, and those entries are removed automatically after 30 days.
Notifications. If you turn notifications on, the app registers a push token that Apple or Google issues for your device, and that token is stored with your account so Canopy can notify you about your own business activity, such as an incoming message or a signed agreement. The token identifies the device to the notification service and nothing else. When you sign out or turn notifications off, the token is switched off and nothing is sent to it again. Deleting your account removes it. Each notification, including its text, passes through Expo's push service, which relays it, and then through Apple's or Google's notification service.
What the app does not do. There is no advertising identifier, no third-party analytics or crash-reporting service, and no attribution or tracking of any kind in this app. Nothing you do in it is shared with an advertiser or a data broker, and nothing is sold. The app does not read your contacts or your calendar, it reads your location only as the paragraph on location below describes, and it never browses your photo library or listens on its own.
Location. Since version 2.2 the app can share where your phone is with your own Canopy install, and only when all of these hold: your company's admin has switched location sharing on for your seat, Canopy is open on your phone, it is within the working hours your company sets, and you have allowed it in the phone's own location prompt. Each time, the app sends the position, how accurate it is and the time it was taken, as often as your company sets (every 1 to 30 minutes). Your company's managers and admins see it in Canopy, and each position is deleted after the number of days your company sets (30 unless it chooses otherwise, never more than 90). You can turn it off at any time in the phone's settings. Location is never used for advertising or tracking, and it goes to no one outside your company's Canopy.
Job files with no signal. Since version 2.2, when you open a job in Canopy the app keeps a short copy of it on the phone so you can still read it where there is no signal: the job's name, number, stage and address, the people on the job with their phone numbers and email addresses, its notes and its recent daily logs, never prices or amounts. It keeps the last 40 jobs for each Canopy install, in the app's private storage, and removes them all when you sign out or delete your account.
Photos, voice notes and files. When you take a photo, choose a photo or a file, or record a voice note in Canopy (a business card, a job photo, a daily log), the app asks the phone for the camera, the photo picker, your files or the microphone for that one action, with your permission, and what you capture goes only to your own Canopy install, exactly as it would from a browser.
Crash reports. When the app hits an error, it sends a short report to your own Canopy install so the fault can be fixed: the error message and where in the app it happened, with email addresses, tokens and long numbers removed first, plus the app version, the update it was running and the phone's operating system. A report never includes your name, your email address or anything from your records, and it goes to no one else. Reports are deleted after 30 days.
Sign in with Apple. If you use Apple's private relay address, that relay address is what I receive and what is stored. I never see the address behind it.
Where the data goes. Requests go to your own Canopy install over an encrypted connection. If your company operates its own Canopy, your records live in your company's own database, under your company's control, and I hold them only insofar as I operate that install for you.
What you write in the app. Everything you write or upload in the app, from notes and call logs to email replies, photos and voice notes, is sent to your own Canopy install and stored there, exactly as if you had done it in Canopy on the web. A reply is sent from your company's own mailbox to the person you are writing to.
Deleting your account. You can delete your account from inside the app, in its settings. Deletion removes the sign-in sessions and the device notification registrations tied to your email address. You can also ask me to do it at joshua@dbjtechnologies.com and I will confirm when it is done. Business records your company owns are your company's to keep or remove, and are governed by the agreement I have with your company rather than by this section. The steps for both routes, and what is kept afterward, are on the account deletion page.
Children. The app is a business tool and is not directed at children.
9. Text Messages
When you text DBJ Technologies at (682) 325-8324, or agree to receive texts about your inquiry or project, your phone number, your messages and the times they were sent are kept in the business's own records so the conversation can be answered and followed up. Texts are carried by Twilio, the messaging provider.
No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Text messaging opt-in data and consent are not shared with any third party.
Reply STOP at any time to stop receiving texts, or HELP for help. The text messaging terms are in section 9 of the Terms of Service.
10. Service Providers
I rely on the service providers below. Each one handles information under its own terms and privacy policy.
Vercel hosts this website and Canopy, stores uploaded files and holds the encrypted nightly backups. Its Speed Insights tool also measures page load times without cookies.
Neon runs the Canopy databases.
Google provides my email and documents through Google Workspace, sign-in with Google, the Gmail, Calendar, Drive and Contacts connections a client makes (section 18), the Places, PageSpeed and Search Console data that Pathlight and my analytics use, and push notifications.
Microsoft provides sign-in with Microsoft and the Microsoft 365 connections, such as a mailbox, that a client makes.
Anthropic provides the Claude AI models described in section 6.
Twilio carries calls and texts, records calls and voicemails, and turns speech into text.
Resend delivers the email that this website, Pathlight and Canopy send.
Inngest runs Canopy's scheduled and background jobs, and the details each job needs pass through it.
Upstash limits how often the forms and chats can be used, counting requests by IP address and email address for up to two days.
Sentry monitors errors. It receives error reports from this website and Canopy, and a small sample of page navigation timing from the browser.
Cloudflare runs DNS for dbjtechnologies.com and the Turnstile check that keeps bots off the forms.
Browserless loads the websites Pathlight scans, the way a browser would.
Intuit QuickBooks and Dropbox exchange accounting records and files with Canopy only where a client connects them.
Expo relays mobile app notifications to Apple's and Google's notification services, and Apple also provides Sign in with Apple.
Calendly handles bookings for calls with me.
DocuSign handles signatures on agreements.
My bank receives client payments.
11. Cookies
This website sets the essential cookies it needs to work and two first-party analytics cookies, a visitor identifier and a session identifier, described in section 12. If you sign in to Canopy here, it also sets a sign-in cookie and a cookie that keeps that browser's visits out of the analytics. That is the complete list. No third-party analytics cookies, no advertising cookies and no cross-site trackers are set, which is why you are not asked to answer a cookie banner when you arrive.
The chat assistant keeps your conversation in your browser's own storage so that reloading the page does not lose it, and clearing this site's data in your browser removes that copy.
12. Analytics
Analytics on this site are entirely in-house and first-party. I measure page views, sessions, traffic sources, approximate geographic region, device type, and Core Web Vitals. Two first-party cookies support this: a visitor identifier (lifespan approximately 13 months) and a session identifier (idle 30-minute window). Both are marked HttpOnly, so no script on the page can read them, and neither is readable by any other site. The analytics never store IP addresses in raw form. They are hashed at the moment of collection using a daily-rotated salt and discarded immediately afterward; only the hash and the country/region/city derived from the request are persisted. Because the salt rotates daily, the hash cannot be used to follow you from one day to the next. Raw page-view rows are retained for 90 days; aggregated session data is retained for 13 months.
This data stays in my own database. It is not sold, not shared with an advertising network, and not sent to a third-party analytics provider. Google Analytics was removed from this site in August 2026, and with it the cookie banner that existed only to ask permission for it. I also use Vercel Speed Insights, which is a separate, cookieless performance measurement tool that records anonymous page load timings without tracking individuals. Sentry, the error monitoring service, receives error reports and a small sample of page navigation timing so that faults can be found and fixed.
If you identify yourself to me, by running a Pathlight scan or submitting the contact form, I connect that inquiry to the visit history of the browser you did it from, so that when we talk I have the context of what you have already seen. That association lives in the same private database, is never shared with anyone, and is deleted on request like everything else.
If you would rather not be counted at all, browsing in a private window or clearing cookies for this site resets both identifiers, and any browser setting or extension that blocks the request to /api/track/view stops the measurement entirely. You can also email me and I will delete what is associated with you.
The Canopy demo. If you explore the Canopy demo in the Canopy app with the demo username and password I gave you, I record which demo pages you open, how long each is on your screen, and what you type into its search boxes, so I can see which parts of Canopy interest you. The demo holds only made-up records, and what I keep is tied to that phone's demo sign-in, never to your name, email address or device name; the place is the approximate city your connection reports. It stays in the demo's own database, is never shared or sold, and is deleted on request.
13. Security and Backups
Every connection to this website and to Canopy is encrypted in transit with HTTPS. The Canopy databases, stored files, and my email and documents are encrypted at rest by the providers that hold them, and sign-in tokens for connected mailboxes are encrypted again inside the database with a separate key.
Every file uploaded to my own Canopy is kept in private storage, and Canopy serves a file only to someone signed in, or to the person it was sent to, such as through the private link of a quote or an invoice. Signing in to my own Canopy as an administrator requires a code from an authenticator app.
Every night, my own Canopy database is written to an archive encrypted with my own key, then read back to confirm it opens intact. The last fourteen archives are kept, so each one rolls off within fourteen days, and the database can also be restored to an earlier point within a short window.
No way of sending or storing information is perfectly secure. If a security incident affects your information, I notify the people and clients affected as the law, including Texas law, and any agreement with them require.
14. How Long I Keep Information
I keep business records while the relationship lasts and afterward as the law requires. A prospect's record is deleted on request.
Pathlight scan results are kept with their reports, and deleting a person's record removes their email address from a scan while the report on the public website stays. Calls, recordings and transcripts are kept while they serve the business purpose they were made for, and are deleted on request.
Website analytics keep raw page views for 90 days and aggregated sessions for 13 months. In my own Canopy, the security log clears the IP address and browser details after 90 days and deletes entries after 13 months, except those about invoices, quotes, proposals and subscriptions, which are kept seven years for tax records. Its operations monitoring entries and app crash reports are deleted after 30 days.
Information deleted from my own Canopy leaves the live database at once. Copies inside the encrypted nightly archives roll off within fourteen days, and the database's short restore history ages out on its own.
15. Your Rights
You may ask to see, correct or delete the information I hold about you at any time, by email to joshua@dbjtechnologies.com or through the form on the Contact page. I respond within 30 days.
You can stop Pathlight emails with the unsubscribe link in any of them, and stop texts by replying STOP. If your information is in a client's Canopy workspace, that client controls it and answers the request.
16. Children
This website and my services are for businesses. They are not directed to children under 13, and I do not knowingly collect information from children under 13.
17. Changes to This Policy
This privacy policy may be updated from time to time. Changes will be posted on this page with an updated revision date.
18. Google User Data
A person can connect a Google account to Canopy. Gmail and Google Calendar are asked for when the account is connected; Google Drive and Google Contacts are asked for only when that person adds them. Canopy uses what Google shares only for the features that person sees in Canopy.
Gmail: messages in the connected mailbox, so they appear on the matching contact, company, deal or job, and so the person can reply, file and archive from Canopy. Canopy sends mail only when the person sends it, or when an automation the business switched on sends it.
Google Calendar: events on the connected calendars, so meetings show on the right records, and the events a person creates in Canopy, with a Google Meet link when asked for.
Google Drive: the folders a person links to a record, and the names, sizes and change history of the files in them, so those files can be found from the record. Files stay in Google Drive. Canopy uploads a file or creates a folder only when the person does so in Canopy, or when the business switches on automatic job folders for won deals.
Google Contacts: saved contacts, read into a list the person reviews. Nothing becomes a Canopy contact until the person adds it.
Access tokens are stored encrypted. Mail, calendar and file details are kept in the Canopy workspace of the business that connected the account, and only the people that business gives access can see them.
Google user data is not sold, not used for advertising, and not shared except as needed to provide the features above, to keep the service secure, or to comply with the law. When an AI feature the business has switched on works with that content, such as a summary, a drafted reply or the assistant, the content involved is sent to Anthropic to produce the result. Google user data is never used to develop, improve or train generalized AI or machine learning models.
No one at DBJ Technologies reads Google user data, except with the account holder's permission, when needed for security or to investigate abuse, when the law requires it, or in aggregated form to run the service.
A person can disconnect a Google account in Canopy's settings at any time, which revokes Canopy's access with Google and deletes the stored tokens, or remove access at myaccount.google.com/permissions. Mail and events already in Canopy stay as the business's records until deleted; section 15 explains how to ask for deletion, and in a client's workspace that client decides.
DBJ Technologies' use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
19. Contact
Questions about this privacy policy can go to joshua@dbjtechnologies.com or through the form on the Contact page.