Privacy Policy

Nashville Apex Solar is a lead matching service and it installs nothing. The arrangement it is built for is that you describe a roof, one solar contractor prices the job, and that contractor pays us instead of you. No contractor is attached to this site yet, so nothing sent here has gone anywhere. That arrangement is still the only reason anything you type would ever leave this site, which is why it belongs at the top of a privacy policy rather than somewhere in the middle of one. The longer account of it is on the about page.

The second record has nothing to do with the form and starts without you. Every page here is counted, this one included, including the visit where somebody reads the policy and leaves. That count is set out further down. It is kept apart from the form on purpose, and the two are never matched against each other.

The form works without any. If you do attach some, four is the limit and ten megabytes each is the size the upload accepts. They go into private storage: there is no public web address for them, so nobody arrives at one by guessing and no search engine has anything to index.

Two things ride along with a roof photograph and both are worth a moment before you send one. The first is whatever else was in the frame, which is usually a neighbour's house and sometimes a parked car. The second is the metadata your camera wrote into the file, which on a phone normally includes the exact position the shot was taken from. Nothing here strips either of them out, so the file that arrives is the file you took.

Nobody, today. No solar contractor is attached to this site, so a request sent this week reaches us and stops. The rest of this section is written in the future tense deliberately: you should be able to read what would happen before deciding whether to send anything.

The chain would be three links long and no longer. Your request reaches us. We hand it to one solar contractor working in Middle Tennessee, who prices the job. We keep our own copy so that we can tell whether it landed and chase it when it did not.

In between, it sits with the two firms that run the hosting for this site and the database behind it. They keep it because we asked them to, and they put it to no use of their own.

A contractor's copy would be theirs once they had it, governed by their policy rather than by this page, and they would be a different company from this one. That is a question to put to them, on the day there is somebody to put it to.

There is one more stop outside that chain, and it comes before we read anything: a request that gets past the two checks above has its text, your name and phone number included, read by an AI model a third-party provider runs, whose only task is to tell a real solar request from a sales pitch or spam. It can flag a request as a pitch and do nothing else with it, it does not replace our own reading of what you sent, and what the provider does with the words is a matter for its own terms, not ours. If that bothers you, tell us through the form.

• The page you asked for, the path on its own. Anything after a question mark in the address is dropped before it is recorded.
• The site that sent you here, if one did, the host name of that site by itself, never the page on it you were reading.
• The width of your browser window, the one number that separates a phone from a laptop, which is most of what anyone needs to know about how these pages get read.
• Roughly where your internet connection is registered, worked out from the connection rather than from GPS, and never finer than a town. It is often simply wrong: a phone on a cell network, or anybody behind a VPN, can register hundreds of miles from where they are sitting.
• The browser and operating system you are using, the line every browser sends about itself with every request it makes anywhere. It is read, not asked for.
• A one-way code standing in for "the same reader", so that four pages read in one afternoon count as one visit instead of four. It is built out of your connection address, your browser, today's date and a value held only on the server. It does not run backwards, the address it was built from is never written down, and tomorrow's code has no relation to today's, so a reader who comes back next week arrives as a stranger.

Not one of those six carries a name or a telephone number, because not one of them comes from the form. Fill the form in during the same visit and the two records still sit apart: nothing here joins a page view to a request.

And the things that do not come with it:

• No cookie is set for it, and nothing is written into your browser's storage.
• Your connection address is never written down. Only the code made out of it is.
• There is no analytics company in the loop, no advertising tag, and nothing that works across other websites.
• The script doing the counting is served from this domain and talks to this domain.
• Turning that script off does not stop the count, and letting you assume otherwise is exactly the sort of thing this page exists not to do. five of the six are things this site's own server reads for itself as it hands over the page. Only the window width has to come from the browser.

A request stays on file while somebody is dealing with it, and then for a stretch beyond that, so one nobody ever followed up on can still be found. There is no other reason to keep it.

There is also no automatic deletion date, and inventing one for this page would be easier than making it true. What exists instead is a request you can make, and it gets acted on.

Ask through the contact page and say what you want in the message. It arrives in the same place an estimate request does. You can ask what is on file about you, and you can ask for all of it to go, photographs included.

There is no second copy to chase today, because nothing has been passed to anybody. When that changes, a deletion you ask us for will not reach their copy, and that one you would have to ask them for.