Privacy Policy
Effective date: 2026-10-15. Last updated: 2026-10-15.
We are not lawyers, and this is not legal advice. This is an operations document, written by the people who configure our systems, so that this page describes what our software actually does. It is deliberately plain and deliberately narrow: it makes no compliance claim — no GDPR, CCPA, HIPAA, SOC 2 or ISO statement — that we do not actually keep, and it promises nothing our systems cannot do.
The short version
We are a small web application development company in Northern Nevada. The only personal information this website collects is what you type into our contact form. We use it to reply to you and to keep a record of the conversation. We do not sell it, we do not share it for advertising, and this site runs no analytics and sets no tracking cookies. If you want your information deleted, email us and we will delete it.
The rest of this page is the detail.
1. Who we are
This site is operated by DNS Computing Solutions (“we”, “us”, “our”), a web application development company based in Northern Nevada.
Email: info@dnscomputingsolutions.com
Mailing address: Reno, Nevada, United States
This policy covers the website dnscomputingsolutions.com and nothing else. It does not cover any application we build for a client; those have their own terms, agreed with that client.
2. What we collect
Information you give us
There is exactly one place on this site where you can give us information: the contact form on our Contact page. It asks for:
| Field | Required? |
|---|---|
| Your name | Required |
| Your email address | Required |
| Your message (“How can we help?”) | Required |
| Company name | Optional |
| Phone number | Optional |
That is the whole list. We do not ask for payment details, a date of birth, a postal address, or anything else, and there are no user accounts on this site to sign up for.
The form also contains a hidden field that a person never sees and never fills in. It is there to catch automated spam. If it is filled in, we discard the submission without storing it and without emailing it.
Information collected automatically
Like every website, ours produces technical records as a by-product of serving pages. Here is exactly what that means on this site.
What our application writes to its own logs. Two kinds of line, and nothing else:
- A contact-form outcome line. When you submit the form we record that a submission happened: the event name, the outcome (stored, notification email failed, rejected as spam by the hidden field, or rejected as invalid), the reference of the stored enquiry — a random identifier our database generates, not derived from anything about you — and, on a failure, a short technical error code.
- A rate-limit line, if someone submits the form far more often than a person would. It records that the request was blocked and a network prefix instead of an address: the first three groups of an IPv4 address (for example 203.0.113.0/24) or the first four groups of an IPv6 address. A prefix like that covers a whole neighbourhood of addresses, which is enough to see an abuse pattern and not enough to point at you.
What our application never writes to its logs: your name, your email address, your message, your company, your phone number, your full IP address, or your browser’s user-agent string. Not truncated, not hashed, not “only briefly” — by the point the log line is written, the code does not have them. The record of your enquiry — the row we keep so that we can reply to you — likewise has no field for an IP address and no field for a user agent. That is a deliberate design decision, not an accident of implementation.
The one place your IP address is held, and for how long. To stop someone submitting the contact form thousands of times, we count recent submissions. That count is stored in our database under a label built from the request method, the page it was sent to, and your IP address — for example contact-post:POST:/contact:203.0.113.7 — alongside a start time and a number. Three things are true of it:
- Only submitting creates one. Reading does not. Browsing this site — the home page, the services page, the blog, this page — creates no counter at all. Nothing is counted until you actually send something.
- It is short-lived. The counting window is ten minutes. The row itself is removed by an automatic cleanup once it is more than an hour old. That cleanup runs when the next request is checked rather than on a fixed timer, so on a quiet day a spent counter can sit a little longer before it is swept away. We would rather tell you that than quote a tidier number we cannot stand behind.
- It is not linked to you, not logged in full, and not shared. The counter holds no name, no email address, no phone number and no part of your message, and nothing joins it to the enquiry you sent. It is never written into our logs in full — a log line about a blocked request carries only the network prefix described above — and it is shared with no one.
What our hosting provider sees. The site runs on Fly.io. Every request to any site on the internet arrives from an IP address, and Fly.io — like any hosting provider — keeps its own short-lived access logs of the requests it routes to us, which can include that address, for security, abuse prevention and fault diagnosis. Those logs belong to Fly.io and are kept under Fly.io’s own policy and retention period, not ours. We do not copy them into anything of ours, and we do not use them to build a record of you.
Error reports. If something breaks, our error-tracking tool (Sentry) records the technical details of the failure, and it is configured to carry no personal information: before a report leaves our server, email addresses, cookies, authorization headers, the contents of form fields and the visitor’s IP address are stripped out. What reaches Sentry is the failure, not the person who ran into it.
We do not build a profile of you, and we do not combine these records with anything else in order to identify you.
3. Why we use it
We use what you send through the contact form to:
- Reply to you. That is the entire point of the form.
- Keep a record of the enquiry, so that if you get in touch again we know what was already discussed, and so that we have a record of what we quoted.
We use the automatic technical records to keep the site working and to keep it secure — for example, to stop someone hammering the contact form with thousands of submissions.
We do not use your information for advertising, we do not add you to a marketing list, and we do not send newsletters or bulk email. If we ever want to do any of those things, we will ask you first.
4. Who else handles it
We use a small number of established service providers to run this site. They process your information on our instructions and for no purpose of their own. We do not sell your information to anyone, and no one on this list is an advertiser or a data broker.
| Provider | What it does for us | What it sees |
|---|---|---|
| Supabase | Hosts the database where contact-form submissions are stored, in the United States | Everything you typed into the form, plus the short-lived rate-limiting counter described in §2, whose label includes your IP address |
| Fly.io | Hosts the website itself, in the United States | The request that carries your form submission, and its own short-lived access logs, which can include the IP address the request came from (see §2) |
| Resend | Sends us the notification email when you submit the form | The contents of that email — that is, what you typed into the form |
| Sentry | Collects technical error reports when something on the site breaks | Technical failure details, with personal information stripped out before the report is sent |
| Microsoft 365 | Hosts the info@ mailbox that receives your enquiry | The notification email and any reply thread |
Beyond that list, we disclose personal information only where we are legally required to — for example, in response to a valid legal process — or where you ask us to.
5. Cookies, analytics and tracking
This site runs no analytics, no advertising pixels and no third-party tracking scripts. We do not use Google Analytics, Google Tag Manager, a Meta pixel, or any equivalent. Nobody is watching you move around this site.
Cookies. Browsing the public pages of this site — the home page, the services page, the blog, the contact page and this page — sets no cookies at all. The site is built on a template that includes sign-in pages for the applications we build for clients; those pages are not linked from this website, nothing here uses them, and account creation is turned off. A session cookie would only ever be set if you went out of your way to sign in there, which nobody can do, because there are no accounts.
6. How long we keep it
Contact-form submissions are kept for 24 months from the date you send them and are then deleted. If your enquiry turns into a project, the records of that project are kept for as long as we work together, and afterwards for the period set out in our agreement with you.
The notification email that your submission generates also sits in our info@ mailbox, and in the delivery logs of Resend, which sends it. Neither copy is on the retention schedule above: the mailbox copy stays until we delete it, and the log copy is kept for the period Resend sets, not a period we control. If you ask us to delete your information, the mailbox copy goes with the record — that is the request in section 7, and we complete it within the 30 days stated there.
Our own application logs — the outcome and rate-limit lines described in section 2, which contain no personal information — are kept only for the short period the hosting platform retains them, a matter of days. Fly.io’s own access logs, which can include an IP address, are kept for Fly.io’s retention period under Fly.io’s policy, not ours.
The rate-limiting counter described in section 2 — a number stored under a label that includes your IP address — counts over a ten-minute window and is deleted automatically once it is more than an hour old.
Error reports are kept by our error-tracking provider for a limited retention window, and contain no personal information by the time they arrive.
You do not have to wait for that period to pass. Ask us and we will delete it sooner — see the next section.
7. Asking us to delete your information, or to tell you what we hold
Email info@dnscomputingsolutions.com and say what you want:
- “Delete my information.” We will delete the contact-form record and the related email from our mailbox.
- “Tell me what you hold about me.” We will tell you what is in the record and send you a copy.
- “Correct my information.” We will fix it.
We will acknowledge your email within one business day and complete the request within 30 days. We may need to ask a question or two to be confident we are acting for the right person — for instance, we will reply to the email address on the record rather than to a different one.
There is no fee, and asking costs you nothing. The only thing we keep after a deletion request is the minimum record showing that you asked and that we complied.
8. Nevada
We are a Nevada business, and this is the law that applies to us.
Nevada law (NRS 603A.340) lets a Nevada consumer tell the operator of a website not to sell their covered information. We do not sell your information, to anyone, for any price — so there is nothing here to opt out of. We are telling you anyway, because the statute says a site should give you a way to ask. That way is info@dnscomputingsolutions.com, which is our designated request address. If you send a verified request, we will respond within the 60 days the statute allows.
If you live somewhere with stronger privacy rights than Nevada’s, write to us at the same address and tell us what you are asking for. We will do our best to honour it, and we would rather do that than pretend a request does not apply to us.
9. How we protect it
We take reasonable measures for a business of our size:
- Contact-form submissions are stored in a database with row-level security turned on, which means the public has no read access at all — not even in principle, from a browser. The records are readable only by us.
- All traffic to this site is encrypted in transit (HTTPS), and the site declines to be served over an unencrypted connection.
- The contact form is rate limited and spam protected, so it cannot be used to flood us or to probe the database.
- Our application’s logs are written so that they do not contain your name, your email address, your message, or your full IP address. The most any line carries is a network prefix, used to spot someone abusing the form. The only place a full IP address is held at all is the short-lived rate-limiting counter described in section 2 — not linked to your enquiry, and deleted automatically.
- The keys that give access to the database are held by the owner and are never stored in our source code.
No system is perfect and we do not claim otherwise. If something goes wrong in a way that affects you, we will tell you.
10. Children
This site is for business. It is not directed at children and we do not knowingly collect information from anyone under 13. If you believe a child has sent us something through the contact form, email us and we will delete it.
11. Links to other sites
This site may link to other websites — for example, to a tool we mention in a blog post. We do not control those sites and this policy does not cover them.
12. Changes to this policy
If we change how this site handles information, we will change this page and update the “Last updated” date at the top. If the change is significant — a new provider, a new kind of information, or a shorter or longer retention period — we will say so plainly on the page rather than quietly editing a sentence.
13. Contact us
Questions about this policy, or about anything on this page:
DNS Computing Solutions
Reno, Nevada, United States
Email: info@dnscomputingsolutions.com