Privacy Policy
Last updated: October 9, 2026
1. Who we are and what this covers
Local Directory Builder is operated by MK153 INC, doing business as Client Builder Pro ("we", "us"). This policy explains how we handle personal information in two roles:
- For our customers, the businesses that build directories with the Service. We decide how their account information is used.
- For visitors to directory websites built on the Service. Each directory is run by one of our customers (the "directory operator"). When you submit something on a directory website, we process it on that operator's behalf, as their service provider. Their own practices are their responsibility; contact them first with questions about how they use your information.
Put plainly: for the submissions and leads a directory receives we are a processor, acting for the directory operator, who is the controller. For our own mail log, our email suppression list and the records we keep after a directory is deleted (described in section 7) we are the controller.
2. Information we collect
From customers:
- Account details: name, email address and sign-in information, handled by our identity provider.
- Company and directory details, settings, and the content you add, including listings you import.
- A record of who on your team drafted, approved, published, scheduled or retracted each directory article, and when. We keep it with the directory to run the publishing controls and to answer reports about a post.
- Creating an account and a Free public directory involves no payment. Separate paid memberships go through the Client Builder Pro checkout and are processed by Stripe; we do not receive your full payment card details. Memberships started before our checkout opened are billed through the Skool community platform.
- Messages you send us.
From directory visitors and business owners, only what you choose to submit through a directory website's forms:
- Enquiries: name, email address, phone number and your message.
- Listing claims: name, email address, phone number, role and the evidence you provide.
- Business submissions: your name, email address and the business you are adding.
- Reviews and community posts: your display name, email address and what you write. Email addresses are never published.
- Quote requests from signed-in members: what you need, where it ships, and your contact details, shared with the businesses you ask to quote.
- Member and owner sign-in: your email address, used to send you a sign-in link.
Automatically: your IP address, used to limit how often forms can be submitted and in our hosting provider's security logs, and the cookies described in section 6.
3. How we use information
- To provide the Service: host directories, deliver submissions to the directory operator, send sign-in links, confirmations and notifications, and show your directory to its visitors.
- To keep the Service secure: prevent spam and abuse, and enforce our Terms.
- To support customers and to tell them about changes to the Service.
- To meet legal obligations.
We do not sell personal information, and we do not share it for cross-context behavioural advertising.
4. AI processing
Community posts may be screened by an AI model (provided by Anthropic) before a person reviews them. The model can approve a harmless post or hold it for a human; it cannot reject one. Directory operators can also connect AI providers with their own API keys; content they send to those providers is handled under those providers' terms. We do not use personal information to train AI models.
5. Who we share information with
- The directory operator receives what you submit on their directory website.
- Service providers that run the Service for us, under contracts that limit their use of the data: Supabase (database), Vercel (hosting), Clerk (sign-in), Resend (email delivery), Cloudflare (domains, DNS and the human check on visitor forms), Stripe (payments through our checkout), Skool (billing for memberships started there), Anthropic (post screening), Google (web fonts on directory websites, which receives your IP address when a page loads), Telegram (alerts to our moderators about community posts, which can include the poster's display name and post) and Sentry (error monitoring: when something breaks it receives technical details such as the page or address that failed, the browser and device type and a code trace; form contents, cookies, email addresses and phone numbers are removed before anything is sent. Sentry may see the IP address of the connection that sends a report, but we have configured it not to store IP addresses, and it processes this data in the United States).
- Client Builder CRM, our own customer-relationship tool, when a directory operator has chosen to send their directory's enquiries there.
- Providers a directory operator connects with their own keys, such as Anthropic, OpenAI or Google Maps.
- When required: to comply with law or legal process, to protect rights and safety, or as part of a merger or sale of our business, subject to this policy.
6. Cookies
We use only cookies needed for the Service to work: keeping you signed in to the admin console, keeping a business owner or community member signed in on a directory website, remembering which company and directory the console is showing, and access to preview sites. When an account owner opens a private directory on its subdomain, a short-lived handoff sets an eight-hour, host-bound cookie. The cookie identifies the owner; the directory checks current ownership on every read. We do not use advertising or analytics cookies. Blocking these cookies will stop sign-in from working.
7. Retention
We keep customer account information while the account is active and for a reasonable period afterwards for legal, tax and security reasons. Directory submissions are kept for the directory operator until the operator asks us to delete them, or until the directory is deleted at the end of its archive period (below). To have a submission deleted, ask the directory operator or write to us. Security logs are kept for a limited period by our hosting and error-monitoring providers.
Senior Travel Insider saved trips. Saved trip plans are kept until you delete them or ask us to; you can delete a plan from its page, or everything for your email from any plan page. Deleting everything also removes your Senior Travel Insider newsletter subscriptions and the contact details saved only for a trip follow-up you requested. We keep a hashed form of your address as our record of the deletion request, and if mail to it bounced or was marked as spam, we keep that suppression so we stop emailing it.
Archived directories. A directory is archived when its operator chooses to archive it, or, if it depends on a paid membership, by us 14 days after that membership lapses unless it is paid by then, at once if we end their access outright, or 30 days after a trial ends without an upgrade. An archived directory's public site is offline. We keep its data, including the submissions it received, for 180 days so it can be restored, and then we delete it.
A Free directory's public site goes offline after 14 days without an upgrade. The lifecycle sweep may archive it 30 days later; archived data is retained for 180 days as described above.
Backups. Deleted data can stay in our encrypted backups for up to about 13 months: we keep a daily backup for 30 days and one backup from each month for about 13 months, and our database provider keeps its own shorter-term backups. We use backups only to recover the Service after a failure.
What we keep after a directory is deleted. Only minimal records: that the directory existed (its name, web address and key dates), a log of the actions taken on it, and our email delivery and abuse logs. We remove the personal information in these records, such as names and email addresses, or replace it with a one-way code. We also keep coded records of email addresses that asked not to be contacted or whose mail bounced, so that we do not email them again.
8. Security
Each customer's data is separated at the database level, connections are encrypted, and access is limited to the people and systems that need it. No system is perfectly secure; tell us at info@clientbuilder.pro if you believe your information has been exposed.
9. Your choices and rights
You can ask to access, correct or delete personal information we hold about you by emailing info@clientbuilder.pro. If your request concerns something you submitted on a directory website, we will pass it to that directory's operator, and help them respond, because they decide how it is used. We will verify requests before acting on them and will not discriminate against you for making one.
California residents have the right to know what personal information we collect, use and disclose; to request deletion and correction; and not to be discriminated against for exercising these rights. The categories we collect, their sources, purposes and recipients are described in sections 2 to 5. We do not sell or share personal information as those terms are defined in the California Consumer Privacy Act. You may use an authorized agent to make a request.
10. Children
The Service is not directed to children under 13, and we do not knowingly collect their personal information. If you believe a child has given us information, contact us and we will delete it.
11. Where data is processed
We and our service providers process information in the United States.
12. Changes to this policy
We will post updates here with a new "Last updated" date. For a material change, we will also email our customers at the address on their account at least 14 days before it takes effect, unless the law or the security of the Service requires it sooner.
Contact
MK153 INC (d/b/a Client Builder Pro), operator of Local Directory Builder
7750 Dagget St. #208, San Diego, CA 92111
Email: info@clientbuilder.pro