Skip to content

Privacy

What we keep, and what we do not.

This describes the records this site actually creates, named one by one. Goldstone Enterprises LLC is the controller of them, at 7301 N 16th St, Suite 102, Phoenix, AZ 85020. Reach us at build@goldstone.solutions. Last updated November 2026.


The short version

Three things worth knowing first.

  • No tracking product

    This site runs no analytics product, no advertising pixel and no tag manager. There is no cookie that follows you here or anywhere else, and no profile of your browsing.

  • Marketing is opt-in only

    Asking for a systems plan does not subscribe you to anything. Marketing email requires a separate box you tick yourself, and it is unticked until you do.

  • Nothing is being sent

    As of this update, no marketing email is being sent from this system and no prize drawing is open. The capability exists and is switched off.


What is stored

Every record this site creates.

Named individually, because a list of categories is a way of not answering the question.

A contact

Created when you send us something with your email address in it — the intake form, a prize drawing entry, or a reply to one of our emails being recorded by hand. It holds your email address, and your name, company and phone number where you gave them. One record per address, so the same person asking twice is one record rather than two.

Where you first came from

Recorded once, the first time we see you: the source (a link tag, an event, or simply this website), the page you landed on, and the referring site if you arrived from an external one. It is written once and cannot be overwritten, which is deliberate — it is there so we can tell which of our own efforts reached you, not to build a picture of you. Our own pages are never recorded as a referrer.

What you did since

A log of events, one row each, from a short closed list: a form submitted, a report requested, a drawing entered, an email sent to you, an unsubscribe. It records that the thing happened and when. It does not record your browsing, and nothing on this site reports your activity back to us as you read.

Your optional marketing consent

If you tick the box, we store the fact, the date, and which form you ticked it on. If you do not, that field stays empty and our sending rules treat an empty field as a refusal — consent is required rather than assumed from silence.

Addresses that asked us to stop

A suppression list, keyed on the email address itself rather than on a contact record. That is so an unsubscribe keeps working even if we delete everything else about you, and so deleting a record cannot quietly re-permit sending. Removing yourself from the list again is deliberate and has to be asked for.

Event page visits

If you scan a QR code from one of our talks, we count the arrival: which event, whether it was a scan or a typed address, and any link tag it carried. There is no cookie, no device fingerprint and no identifier for you in that record — the question it answers is how many people a card reached, and answering it does not require knowing who they were.

A prize drawing entry

Only if we are running a drawing and only if you enter one. It holds your name and email, which drawing, and whether the entry is eligible. No drawing is open at the time of this update. When one opens it has its own published official rules, and those rules govern it.

What you send us

Your description of your problem, the answers you give, the plan generated from them, and any documents you attach. These go to a private record and a private inbox. They are never published, never indexed, and never used as a case study without asking you first.


Voice and documents

Two specifics worth stating plainly.

  • No audio ever reaches us

    If you describe your problem by speaking, your own browser turns the speech into text on your device. No recording is uploaded and none is stored. What we receive is text you had the chance to edit.

  • Documents are read by a person

    Anything you attach is stored privately and read by a person. It is not fed to the planner, not published, and not shared outside Goldstone.


Why, and for how long

The reasons, and the limits.

Why we hold it. To answer you, to do the work you asked about, to keep a record of an agreement or a payment where one exists, and — only with your consent — to send you occasional notes about systems and operations. We never sell, rent or share a list, and we have no advertising relationship with anyone.

Who else sees it. The services that make this site work, and no others: our hosting and form provider, our database provider, our email sending provider, and the model provider that generates a systems plan from what you describe. Each sees only what its job requires. No advertising network, data broker or analytics company receives anything.

How long. A contact and its attribution are kept while there is a reasonable prospect of working together, and removed on request. A suppression is kept indefinitely on purpose: forgetting that you asked us to stop would mean starting again. Plans, descriptions and documents are kept as a business record.

Cookies. This site sets no tracking or advertising cookies, which is why there is no consent banner on it. The client portal at a separate address sets a session cookie so that signing in works, and nothing else.


Your choices

How to stop, and how to see it.

Stop marketing email. Every marketing message we send carries a link that stops them, and it works in one click without signing in to anything. You can also email us and we will do it.

See it, correct it, or have it removed. Email build@goldstone.solutions and ask. We will tell you what we hold about you, correct it if it is wrong, and delete it where we are not required to keep it. We do not charge for this and we do not require a form.

Children. This is a service for businesses. We do not knowingly collect anything about anyone under 18.

Changes. If what we store changes, this page changes with it, and the date at the top moves. It is written from the data model rather than from a template, so it is the page that has to be updated when the system is.