Privacy Policy

Who this covers

Relic Web Solutions LLC (“Relic”, “we”, “us”) is a web development and marketing company based in Ohio, United States. This policy covers:

• This website — relicwebsolutions.com, including our contact form.
• Beacon — our job-proof and local-SEO product: the technician app, the client dashboard, and the public project pages and embeddable widget it publishes.
• Client websites we build and host, to the extent they run our code. Those businesses may also have their own privacy policies covering their own use of your data.

The two roles we play

This distinction matters, because it decides who you should ask about your data.

• Our own data — we decide. Visitors to this website, and the business owners and technicians who hold Beacon accounts. This policy governs it.
• Our clients' data — they decide, we process. When a trades business uses Beacon, the check-ins, photos, notes and any customer records they bring in belong to them. We hold and process it on their instruction. If you are a homeowner asking about a job at your property, the business that did the work is the right first contact — but you can still reach us at info@relicwebsolutions.com and we will help.

This website

Browsing relicwebsolutions.com, we collect:

• Contact form submissions — your first and last name, email, optional phone, the service you selected, and your message. The form posts to Formspree, which delivers it to us by email.
• Analytics — we use Google Analytics 4, which sets cookies and records pages viewed, approximate location derived from your IP address, and general device and browser information. You can opt out with Google's browser add-on or by blocking cookies.
• Fonts — pages load typefaces from Google Fonts, so your IP address and the page you are on are visible to Google when they load.
• Server logs — our host, Vercel, keeps standard request logs.
• A theme preference — stored in your browser only (light or dark). It never reaches us.

Beacon accounts

Beacon accounts are created by invitation — a business owner invites their team by email; there is no public sign-up. For each account we store your email address, your name, an optional profile photo, your role (owner, approver, or technician), and which business you belong to. Authentication and password storage are handled by Supabase; we never see your password.

Other members of your business can see your name and email address in the team list. Relic staff can also access accounts and data across businesses in order to operate and support the product.

Check-ins: photos, location, and notes

When a technician completes a check-in on a job, the app records:

• Photos — up to five per check-in.
• The device's location at the time of capture — latitude, longitude, and an accuracy reading — taken from your browser's location service, with your permission.
• A street and neighbourhood label for that location. To produce it, the app sends the coordinates from the technician's device to OpenStreetMap's Nominatim service. Map tiles shown in the app are also requested from OpenStreetMap.
• A note describing the work, plus the services performed, the time, and which technician submitted it. If you dictate the note instead of typing it, your browser's own speech recognition handles the audio — in Chrome, that means the audio goes to Google. If that matters to you, type the note.

Some businesses run Beacon in a mode that records no location and no photo geodata at all — only the city and state of the job.

What becomes public — and what never does

Beacon's purpose is to publish proof of completed work, so a check-in that a business publishes is deliberately public: it appears on their project pages and widget, and is intended to be found by search engines. Unpublished check-ins stay private to the business.

Published check-ins show: the photos, the note, the services performed, the neighbourhood and the city/state, the date, and the business's own branding and contact details.

Published check-ins never show:

• The exact location. Before publishing, we replace the precise coordinates with a deliberately fuzzed point — offset by a random distance of roughly 80–200 metres in a random direction. The map pin is an approximation on purpose, because a check-in is usually at someone's home. The precise coordinates stay private to the business, and the offset is generated once and never recalculated.
• The street address.
• The technician's name or any account details.
• Any customer name, address, phone number, or job record.

Photos attached to a published check-in are served from public storage, which means anyone with the direct link can open the image file, whether or not they came via the page.

Customer records from job-management systems

A business can connect a job-management system (for example Jobber) so their scheduled jobs appear in Beacon. When they do, we import the job records — which can include the customer's name, service address, coordinates, and schedule, along with the raw record as the provider sends it.

This data exists so a technician can pick the right job. It is never published, never used to train anything, and never shared with the social platforms. It belongs to the business that connected the account, and it is deleted when they disconnect and ask us to remove it. Access credentials for these connections are stored where only our servers can read them — never in the app on your phone or in your browser.

Connecting Facebook and Google Business Profile

A business can connect their Facebook Page or Google Business Profile so that published check-ins can be posted to it. This is optional, and it is the only reason we touch those platforms.

• We never see or store your Facebook or Google password. You authorise the connection on the platform's own screens.
• We do not hold the access tokens. The connection is brokered by our publishing provider, Zernio, who holds them. Beacon stores only what it needs to address the right account: an account identifier, the account's display name, the platform, a workspace identifier, and when it was connected.
• We use the connection for one thing: publishing. We list the accounts you can choose from, and we post the content you approve to the account you picked. We do not read your messages, your friends or followers, your ads, or your reviews.
• Posts are made from your own real jobs — the caption and photo come from a check-in your business published.

To disconnect, or to have this data removed, see Data Deletion.

How we use AI

Beacon uses AI to clean up a technician's rough note into a readable paragraph, and to draft social captions. We send text only — the note, the services, the city or neighbourhood, and the business name — to Anthropic's Claude API.

Who else touches your data

We do not sell your data, and we do not share it for advertising. We use these providers to run the product, and they only receive what their job requires:

Supabase

Database, sign-in, file storage, and server functions — the core of Beacon.

Vercel

Hosting and request logs for our websites and dashboards.

Anthropic

Note clean-up and caption drafting. Text only — never photos.

Zernio

Publishing to Facebook and Google Business Profile. Receives the caption and a public link to the image, and holds the platform access tokens.

OpenStreetMap

Turning coordinates into a street label, and map tiles. Receives the device's coordinates.

Resend

Delivering invitation and account emails.

Formspree

Delivering this website's contact form.

Google

Analytics and fonts on this website. Speech recognition, if you dictate a note in Chrome.

Job-management systems

Only those a business connects themselves, and only to import their own jobs.

We may also disclose data if the law requires it, or to protect our rights or someone's safety. If our business is ever sold or merged, data may transfer with it; we would tell you first.

Security

Every request is checked against the business it belongs to at the database level, so one business's data cannot be read by another. Captured photos live in private storage and are served through short-lived links. Integration credentials are readable only by our servers, never by the apps on your phone or in your browser. Traffic is encrypted in transit.

No system is perfect, and we will not pretend otherwise. If you believe you have found a vulnerability, email info@relicwebsolutions.com and we will take it seriously.

How long we keep things

Being straight with you about this:

• We do not run an automatic deletion schedule. We keep your data for as long as your business has an active account with us, and delete it on request.
• Published check-ins are intentionally durable. The whole point is a public, permanent record of completed work, and our software deliberately blocks accidental deletion of published pages. Removing them is a deliberate act — we will do it when asked.
• Website analytics are retained under Google Analytics' own settings.

If that is not what you want for your data, the next section is the one you need.

Deleting your data, and your choices

You can ask us to show you what we hold about you, correct it, export it, or delete it. We honour these requests regardless of where you live, rather than only where a law compels us to. Full instructions, including what disconnecting a social account does and does not remove, are on the Data Deletion page.

You can also turn things off at the source: deny the location permission (check-ins still work, without a pin), type notes instead of dictating, block analytics cookies on this site, or disconnect a social account at any time.

Children

Beacon is a tool for businesses and their staff. It is not directed at children, and we do not knowingly collect data from anyone under 16. If a child's data has reached us, tell us and we will remove it.

Where your data lives

We are a United States company and our providers process data in the United States. If you use our products from elsewhere, your data is transferred to and stored in the US.

Changes to this policy

If we change how we handle data, we will update this page and the date at the top. For changes that meaningfully affect you, we will contact account holders directly rather than quietly editing the page.

Contact us

Questions, requests, or complaints — a real person reads these:

• Email: info@relicwebsolutions.com
• Phone: (937) 658-1670
• Relic Web Solutions LLC, Ohio, United States