LocalGuild Privacy Policy
Effective date: September 27, 2026
LocalGuild is operated by DE Digital LLC, a Florida limited liability company ("LocalGuild", "we", "us"). This policy explains what information we collect, why, who we share it with, how long we keep it, and the choices you have. It covers our website at localguild.app, our web app, and the LocalGuild Chrome extension.
LocalGuild is a service for local home-service businesses. A group of trusted local businesses (a "guild") works together. When someone in a local Facebook group asks for a recommendation, we let guild members know so they can respond and recommend each other.
Who this policy is about
Members: people who have a LocalGuild account. This includes business owners and admins, their employees, and "advocates" (friends, family or past customers who choose to recommend a business).
People who post in local groups: people who write posts in Facebook groups that our members belong to. They don't have a relationship with us, but we describe how we handle their posts below.
Information we collect
From members
Account details: your name, email address and mobile phone number. We use them to sign you in, with a one-time code or a sign-in link, and to send you the alerts you ask for.
Your business: your company's name, trade (for example, HVAC or plumbing), website address and public Facebook Page address.
Your business profile: when you set up your company and give us permission, we read your company's public website and public Facebook Page once. From them we build a business profile: services, service area, and the kinds of requests that fit you. You can review and edit it. We keep the profile and a record of your permission. We don't keep copies of the pages themselves.
Your role and team: which guild and company you belong to, and your role (admin, employee or advocate).
Alert preferences: whether you want alerts by email or text, and any pause you set.
Consent records: when you agree to receive texts, we record the exact wording you saw, when you agreed, and the IP address and browser you agreed from. We record opt-outs the same way. Text-message rules require these records.
Terms of Service acceptance: which version of our Terms of Service you accepted, and when.
Your activity: for example, which alerts were sent to you, whether they were delivered, when you tapped "I endorsed this", and any "this wasn't a real request" reports.
Security and audit records: sign-in sessions (including IP address and browser type), and a log of important account actions (for example, invitations and removals) with the IP address they came from.
From the LocalGuild Chrome extension (if you install it)
The extension helps your guild notice recommendation requests in Facebook groups you're already a member of. Before it does anything, it shows a disclosure and asks for your permission. We record your answer, the version you saw, and the IP address and browser it came from. You can pause it or disconnect it at any time.
When the extension finds a post in one of your guild's watched groups that matches a trade keyword, it sends us:
The post's text, so an AI service can check whether it's a genuine request for a recommendation. See "How we handle post text" below.
The post's ID and the group's ID and name, so we can link to the post and avoid alerting twice.
When the post was made.
The extension also sends us technical information:
Device and extension information: a name you give the browser, the extension version, and the Chrome version.
Scanner health counts: for example, how many posts were read, how many checks ran, and whether Facebook showed a security check. These are counts only, with no post content.
The extension never sends us the names, profile links or photos of the people who post, and we never store them.
The extension works with your own Facebook session in your browser. It keeps your Facebook session information on your computer. We never receive your Facebook password, cookies or session tokens.
How we handle post text
Post text is used only to check whether a post is a real request for a recommendation, and to write a short neutral summary in our own words (for example, "Needs AC repair, Conroe area").
We do not store post text.
If the check can't finish right away, we hold the text encrypted for at most one hour to retry, then delete it.
What we keep about a post: a link to it, the group, the matched trade, the AI's assessment, and our short summary. This summary never includes the poster's name.
Email delivery information
When we send you email, our email provider tells us whether it was delivered, bounced, or marked as spam. We use this to stop sending to addresses that bounce or complain.
How we use information
We use information to:
run LocalGuild: sign you in, manage your guild and team, find recommendation requests, and send alerts;
check posts with an AI service and summarize them;
honor your preferences and your consent choices, including text-message opt-outs;
keep LocalGuild secure, prevent abuse, and troubleshoot problems;
improve how accurately we recognize real requests. To do this, our staff may write made-up, name-free examples based on posts that were reported as mistakes. We never keep the original post text.
comply with the law.
We do not sell your information. We do not use it for advertising, and we don't use advertising or analytics trackers.
AI processing
We use an AI service provider to:
check whether a post is a real recommendation request;
write a short neutral summary;
build your business profile from your public website and Facebook Page.
We send the provider only what it needs for each task. We ask it not to keep what we send and not to use it to train its models.
Who we share information with
Your guild. Other members of your guild see your name, company and role. When an alert goes out, the people it's sent to see the lead summary and your company's name.
Service providers who help us run LocalGuild, under contracts that limit how they can use the information:
website and app hosting;
database hosting;
email delivery;
AI processing;
text-message delivery (only once texting is turned on).
Legal and safety: when the law requires it, or to protect the rights, safety or security of our users, the public or LocalGuild.
Business transfers: if LocalGuild is involved in a merger, acquisition or sale of assets, subject to this policy.
Mobile information will not be shared with third parties or affiliates for marketing or promotional purposes. The information-sharing described above excludes text-messaging originator opt-in data and consent; this information will not be shared with any third parties.
Text messages (SMS)
We send texts only if you agree to receive them. Agreeing is not a condition of any purchase.
We send lead alerts and account messages, such as sign-in codes and invitations. How often varies. Message and data rates may apply.
Reply STOP to stop texts, or HELP for help. You can also turn texts off in your alert preferences.
We keep a record of your consent and any opt-out for as long as the law requires (at least four years).
See our SMS Terms for details.
How long we keep information
| Information | How long |
|---|---|
| Post text | Not stored. If a retry is needed, it is held encrypted for at most 1 hour, then deleted. |
| Sign-in codes | 5 minutes |
| Email sign-in links | 10 minutes |
| Extension pairing codes | 10 minutes, or until used |
| Invitations | 7 days, or until accepted |
| Alert links | Work for 72 hours. The alert record is kept until its lead is deleted. |
| Sign-in sessions | Up to 30 days of inactivity |
| Records that a post was seen by a particular scanner | 30 days after last seen |
| Email delivery event records | 30 days |
| Consent and opt-out records (the email address or phone number and its opt-in and opt-out history) | At least 4 years, even after account deletion, kept unlinked from you so opt-outs keep being honoured |
| Lead records (link, group, trade, AI assessment, summary) and related activity (alerts, endorsements, "not a real request" reports) | 12 months from when the lead was created |
| Post references (the post and group IDs we use to avoid duplicates) and the AI's assessment records | 12 months, once no lead refers to them |
| Alert delivery records (which alert was sent to whom, by which channel, and whether it was delivered) | 90 days from when the alert was created |
| Your business profile, every version of it | While your company is in the guild, then deleted 30 days after your company leaves |
| Your company's name, website address and Facebook Page address | Kept in your guild's history after your company leaves |
| Extension scanner health counts (counts only, no post content) | 90 days |
| Records that you agreed to the extension's disclosure (version, what you allowed, times, IP address and browser information) | 1 year after that browser is disconnected. The IP address and browser information are removed straight away if you delete your account. |
| Account, team and preference records | While your account exists. When you ask, we remove your name, email and phone number and delete your preferences (see "Your choices"). |
| Security and audit logs | 1 year |
| Terms acceptance records (which version you accepted and when) | Until your account is deleted |
Backups. Deleted data can remain in our database's restore history for up to 6 hours before it is permanently gone. Encrypted post text held for a retry therefore exists for at most about 7 hours in total: up to 1 hour in use, plus up to 6 hours in restore history. It is also protected by keys that we destroy within about 25 hours, and our key store keeps no history.
How we protect information
All connections use HTTPS encryption.
Sign-in uses one-time codes or sign-in links, with no passwords, and sessions are protected against theft.
Sign-in codes are only sent to people who already have an account or an invitation.
Links in alerts are unguessable, work only for the person they were sent to, and expire.
Each browser the extension is connected to has its own key. You or your company admin can revoke it at any time.
Access is limited so that one guild can never see another guild's information.
Our logs are designed not to contain post text, sign-in codes, or full phone numbers or email addresses.
No system is perfectly secure, but we work to protect your information and will notify you as required by law if a breach affects you.
Your choices
Alert preferences: change email or text alerts, or pause them, in your account settings.
Email: every alert email has an unsubscribe link.
Texts: reply STOP, or turn them off in your preferences.
Extension: pause scanning, turn off background checks, or disconnect the browser from your account at any time. You can also uninstall it.
Access or correction: email privacy@localguild.app.
Deleting your account: email privacy@localguild.app from the address on your account, or tell us the phone number on it. We'll confirm the request comes from you, and complete it within 30 days. We will:
replace your name with "Deleted user" and remove your email address and phone number from your account;
sign you out everywhere, delete your sign-in records and codes, and revoke all your access, including connected extension browsers (their names are cleared too);
end your guild memberships and clear your job title or relationship;
delete your alert preferences, cancel any alerts still waiting to be sent to you, and remove your address from the records of alerts we already sent;
cancel any pending invitations sent to or from you, and remove the names and addresses on them.
What we keep, and why:
Guild history. Past activity, such as endorsements and alerts, stays in your guild's records. It is attached to an anonymous "Deleted user" entry that no longer has your name, email or phone.
Security logs. Existing entries are not rewritten. They refer to an internal ID that no longer connects to any of your personal details. They are deleted after one year, like all our audit logs.
Text and email opt-in and opt-out records. For at least four years, because the law requires it, we keep each record of an opt-in or opt-out. Each record holds:
your phone number or email address;
what you agreed to or declined, and the wording you saw;
when it happened;
the IP address and browser information it came from.
These records are no longer linked to you or to any account. They also let us keep honouring an opt-out, so a number that said STOP is never texted again.
If your company leaves LocalGuild, your access through it ends, but your account itself isn't deleted. Ask us if you want it deleted.
If you are the only admin of a business that is still active, we'll ask you to name a new admin first, or close the business's account. We'll confirm by email when we're done.
Depending on where you live, you may have additional rights under your state's law. Contact us at privacy@localguild.app to exercise them.
People who post in local groups
If you posted in a Facebook group and a LocalGuild member saw it, here is what happened:
The member's extension may have sent us your post's text so we could check whether you were asking for a recommendation.
We did not store your post text or your name.
We kept only a link to your post and a short summary in our own words.
If you'd like us to remove the link and summary about your post, email privacy@localguild.app with the post's link.
Children
LocalGuild is for businesses and adults. It is not intended for anyone under 18, and we don't knowingly collect information from children. If you believe a child has given us information, contact us and we'll delete it.
United States only
LocalGuild is offered in the United States, and our systems are hosted in the United States.
Changes to this policy
We may update this policy. If we make significant changes, we'll notify members by email or in the app before they take effect. The effective date at the top always shows the current version.
Contact us
DE Digital LLC
1680 Fruitville Rd, #530, Sarasota, FL 34236
Email: privacy@localguild.app