Legal
Privacy Notice
- Document
- legal/privacy-notice.md
- Version
- 1.7
- Approved
- 2026-10-28
- Status
- In effect since 2026-10-28
Version: 1.7 · Drafted: 2026-10-28 · Effective date: 2026-10-28Replaces: Privacy Notice v1.6, effective 2026-10-22.
This notice explains what personal information New Age Consulting, LLC collects, why, who helps us handle it, how long we keep it and what you can ask us to do. "NAC", "we" and "us" mean New Age Consulting, LLC.
The short version
- We collect what you give us, what our systems need to run, and business contact details that businesses publish on their own websites.
- We don't sell personal information, and we don't share it for advertising. There are no ad pixels or tracking cookies on our sites, and no tracking pixels in our emails. We count visits to our public web pages without cookies (§7).
- We use AI tools to do our work. Noah Hicks, NAC's owner, approves commercial commitments and material releases; routine work and communications may be automated under approved permissions.
- Signed records, signing evidence and financial records are kept for years. Opt-outs are kept permanently so they keep working. Most other data is kept for shorter, stated periods.
- You can ask to see, copy, correct or delete your information by emailing help@consultnewage.com. We aim to answer within 30 days.
1. Who we are
New Age Consulting, LLC is a Missouri limited liability company. It builds websites, software, automations and AI systems for businesses and individuals in the United States.
- Postal address: 30501 Utica Dr, Richland, MO 65556
- Email: help@consultnewage.com
- Website: consultnewage.com
2. What this notice covers
It covers:
- our public website;
- our intake form and its optional AI helper;
- the client portal;
- our signing service at sign.consultnewage.com;
- email between you and us;
- the business contact information we use for outreach.
It doesn't cover information we handle inside a client's own systems on that client's behalf, such as the client's customer list. There, we follow the client's instructions and our contract with the client, and the client's own privacy notice applies. Questions about that information should go to the client first. We will help the client answer them.
This notice is information. It is not a contract, and it doesn't change a signed agreement. We still stand behind every statement in it, and we keep it accurate.
3. What we collect, by source
3.1 When you visit the website
Our hosting provider records technical information for each request: IP address, browser and device type, the page requested, the time, and any errors. We use it to keep the site running and secure. We don't use it to build a profile of you.
3.2 When you use the intake form or its AI helper
- Before you submit, NAC does not create an inquiry record from your answers. The form and AI helper keep an unsent draft in your browser tab's session storage, so a reload can restore it. This storage is normally limited to the tab, but browser session-restoration features can retain it after closing. Clear the draft or browser site data if you do not want it kept on your device. The form clears its draft after a successful submission, and the helper clears its stored conversation after its request is successfully submitted. If the AI helper is switched on, your messages and relevant conversation history go to our model provider to generate a reply before you submit (see §5 and the Intake Assistant Terms). Hosting and provider security/abuse processing are separate from an inquiry record and may involve retention. To limit abuse, our helper counts requests against a one-way hash of your network address, held briefly in memory rather than written to the inquiry database.
- When you tick the consent box and press submit, we store:
- your name, email, business name (if any), and town and state;
- what you need, and whether the work is for a business or for personal use;
- how you found us, if you tell us;
- the summary you reviewed and confirmed. We don't store the chat itself.
- a consent record: the time and the versions of this notice and the applicable Website Terms and Intake Assistant Terms presented with your submission.
3.3 When you become a client or talk with us about a project
- Contacts: names, roles, email addresses, and phone numbers you choose to give us.
- Project material: messages, files you upload, requirements, decisions, tickets, feedback, and the deliverables we build.
- Meeting recordings and transcripts, made only when everyone in the meeting has been told and has agreed. We announce the recording on it, and each person's yes is captured.
- Meetings and bookings: when you book a call on one of our Google Calendar booking pages, Google adds it to our calendar, and our platform copies the time, the kind of call, and each guest's name and email address onto your inquiry or client record. It doesn't copy the event's description or any notes you add there. If we don't know you yet, the booking starts an inquiry record, which we keep and delete as §8 describes for inquiries, unless your address is on our do-not-contact list. When we arrange a meeting with you, it becomes an event on our calendar with a Google Meet link, and Google sends you the invitation.
- Portal account records: your name, email, how you sign in (a one-time code we email you), sign-in times and access history. For each sign-in session we also record the IP address and browser details it came from, so you and we can recognize a session that isn't yours.
3.4 When you sign a document with us
We keep:
- your name and email;
- a record that your one-time email code was checked (stored as a one-way hash, never the code itself);
- your consent to electronic records, and the version of the disclosure you saw;
- the time of each step;
- a digital fingerprint (a hash) of each document you opened and signed;
- the signed documents themselves.
This is the proof that you signed and what you signed. The signing record itself doesn't include your IP address or browser details. Our hosting provider's request logs do, as §3.1 describes.
3.5 When you pay us
We keep your billing contact, invoices, amounts, payment status and payment references. Your bank or card details go to our banking and payment providers (Mercury and, if you choose card, Stripe). We don't receive or store full card numbers or bank login details.
3.6 When we contact a business about our services
We research local businesses from their own public web pages, and find them through public business directories such as chamber of commerce, city and visitor-bureau listings and the Better Business Bureau. For a business we may write to, we record:
- the business's name, website and town;
- the business email address it publishes on its own website or, if it has no website, on its own listing in one of those directories, and the name and role of the person it names with that address;
- the URL of the page where the address appears, and the time we read it;
- short excerpts (up to 300 characters each) from the business's own pages that explain why we're writing, each with its source URL, the time we read it and a hash of the excerpt;
- a log of what we sent and when, and any reply or opt-out.
We never collect phone numbers, home addresses, photos, review text, social media profiles, or anything about a person's private life. We never buy lists, and we never guess or build email addresses. If a site or directory asks not to be contacted, or says its addresses mustn't be used for marketing, we don't write, and we add the business to our do-not-contact list. Every outreach email says where we found the address.
3.7 When someone introduces you to us, or you introduce someone
- If someone introduces you to us, we record who introduced you, when, and how: an email introduction, their referral link, or your telling us. If they copy you on an introduction or give us your contact details, we keep your name, email, business and any note they share, so we can reply to the introduction. We don't start contact from a name alone. We reply where you're already part of the conversation, or after you contact us.
- If you introduce someone to us, we record your name, email and business (if any), and each introduction you make, with its status.
- If you become a referral partner, we also keep your signed agreement, your referral code, your sign-in records (as in §3.3), the rewards we owe and pay you, and the date we received your tax form. Your tax form, taxpayer ID and bank details aren't stored in our platform. They stay with our bank and our tax records.
3.8 Information you shouldn't send us
Please don't send us any of these:
- passwords, API keys or recovery codes;
- full card or bank account numbers;
- Social Security numbers, or government ID numbers or images;
- health, medical, health-insurance or biometric information;
- information about children.
Our forms screen for common patterns, but they cannot detect every sensitive item. If it reaches us unexpectedly, we restrict access and arrange appropriate return or secure deletion where practicable, subject to incident evidence, legal duties and backup limits. Exposed credentials should be revoked or changed.
Ordinary project integrations can use named accounts or narrowly scoped credentials through a private access method approved for that project; never send them through intake, AI chat or ordinary email. Sensitive or regulated processing needs a specific agreed scope, suitable safeguards and any legally required agreement before it begins. Approval of ordinary services does not approve those exceptional uses.
4. Why we use it
- To answer your inquiry and decide together whether we're a fit.
- To prepare quotes, agreements and statements of work.
- To do the work you hired us for, and support it afterward.
- To run the client portal and keep it secure.
- To obtain and prove signatures.
- To bill, collect and keep accounting records.
- To credit the person who introduced you, and to calculate, pay and account for referral rewards.
- To contact businesses about services that match something on their own website, and to honor opt-outs.
- To prevent abuse and fraud, investigate problems, and keep required records.
- To meet our legal duties and protect our legal rights.
What we don't do:
- We don't sell personal information.
- We don't share it for cross-context behavioral advertising, which means ads targeted using your activity across other sites.
- We don't publish a client's name, logo, results or testimonial without separate written permission.
- NAC does not use your personal information or confidential project material to train AI models. Before sending it to a model provider, we require suitable business/API terms or account controls that exclude model training for that use, and we do not opt it into training through feedback or data-sharing programs. This does not mean the provider keeps no logs or retains nothing.
- We will never start any new kind of use, such as AI training, by quietly changing this notice. If we ever want to, we will tell you first, prominently, and ask for your consent.
5. Who we share it with
We share information with service providers as reasonably needed for the purposes below and the agreed project, subject to confidentiality, suitable provider terms and applicable law. The table describes our principal tools, not a promise to use an unchanging set forever. Other project tools may be named in the scope or access plan. We assess a new provider before giving it personal or confidential information and update this notice or give further notice when required; a change does not silently authorize a new purpose for old information.
| Provider | What it does for us | What it handles |
|---|---|---|
| Vercel | Hosts our websites, the portal and the signing service; stores files; counts visits and measures page speed on our public pages | Everything those services hold, plus request logs and the visit measurements in §7 |
| Neon | Runs our databases | Records for the portal, signing, projects and outreach |
| Resend | Sends system email: sign-in and signing codes, signing invitations, completed documents, request receipts, notices. Tells us when a message bounces or is marked as spam. | Your name, email address, the message, and its delivery reports |
| Google Workspace | NAC's email, calendar and documents. The platform's Gmail integration reads and organizes approved mailbox threads and sends permitted replies. Its Calendar connection reads our calendar's busy times and the bookings made on our booking pages, and creates the meetings we arrange, with Google Meet links. | Emails, calendar events and invitations (with guests' names and email addresses), bookings and working documents |
| Mercury | Business banking and invoicing (ACH and wire) | Billing contact, invoices, payments |
| Stripe (optional) | Card payments, only when card payment is offered and you choose it | Payment details you enter with Stripe, amounts, status |
| OpenAI (the intake assistant's model provider; only if the helper is switched on) | Generates the helper's replies | Your messages and relevant history, sent with the application's storage option off (store:false) under the business API terms. That setting is not a promise of zero provider retention: security/abuse logs and applicable exceptions may remain. |
| OpenAI, Anthropic and Grok (SpaceXAI) (model providers used by NAC's agents and build tools) | Research, drafting, building and testing | The project and business information needed for the task, under the no-training policy in §4. Product terms, account controls, feedback options and retention can differ; we check the actual service used rather than assuming all accounts have the same policy. |
| Pushover | Sends notifications to Noah's phone | A brief, redacted title, status/action summary and, where useful, a link. No credentials, documents or sensitive client detail |
Our signing service is NAC's own. It runs on the providers above, not on a third-party signing company. A project may also use tools named in its statement of work, such as the code host for the project's source code.
We may also share information:
- with people in your own organization who are authorized for the project;
- at your direction;
- with the person who introduced you to us: whether you became a client, and the reward we owe them. We don't share your project details with them. A referral partner also gets a statement of the introductions they made, each one's status, and the amounts we received that their reward is based on, under a confidentiality agreement;
- with our lawyers, accountants or insurers, who have duties of confidentiality;
- when the law requires it, such as a valid subpoena or court order;
- to investigate or prevent fraud, security incidents or abuse, or to protect our legal rights;
- in a sale or reorganization of NAC's business, where the buyer must keep honoring this notice for information collected under it.
Google sign-in supplies account identity; connecting NAC's owner-approved Gmail accounts and NAC's Google Calendar are separate features. Mailroom uses message text, sender and recipient details, subjects, dates, thread identifiers and authentication results to organize mail and prepare and send permitted replies. The Calendar connection uses event titles, times and guests' names and email addresses to record bookings and schedule meetings, and reads only busy times from the other calendars it checks; it never reads event descriptions. Meeting records are stored in Neon. Message records are stored in Neon and provider mappings in Vercel Blob. Authorized AI services described in §5 may process only the content needed for the approved mail task under our no-training controls. NAC's use and transfer of Google API data follows the Google API Services User Data Policy, including its Limited Use requirements. We do not use Google Workspace API data to develop, improve or train non-personalized AI or machine-learning models. Google API data is not sold or used for advertising, creditworthiness or lending. Sharing and human access stay within Google's permitted authorizations and exceptions; a business-asset transfer requires the user's prior explicit consent. These limits control broader wording elsewhere in this notice. Sections 8 and 9 cover retention and requests for access, correction or deletion, including NAC's stored Gmail and Calendar records.
6. How we use AI
NAC does much of its work with AI agents under Noah's direction. They research, draft, build, test and prepare documents. People and agents act within approved permissions. Noah approves contracts, commercial terms, refunds, access grants and material releases; signers make their own consent and signature decisions. Routine project work and communications may be automated under the approved scope and policies, without a separate human approval for every technical step.
AI output can be wrong. Noah reviews material deliverables before release. The public intake helper has no authority to make a commitment or give professional advice. A formal quote, invoice, approved project instruction or contractual notice issued under NAC's approved workflow may have the effect stated in the signed agreement; automation does not erase that effect.
7. Cookies and browser storage
We use only cookies and browser storage that are strictly necessary for a service you ask for:
- keeping you signed in to the portal or the signing service;
- protecting forms and sessions from misuse;
- keeping your unsent intake draft in your browser tab;
- remembering a display setting you chose, such as light or dark mode.
We use no advertising cookies, no third-party tracking, and no analytics cookies. If you block these cookies, sign-in and signing won't work.
Our public web pages count visits and measure how fast pages load, using Vercel Web Analytics and Vercel Speed Insights from our host, Vercel. The client portal, our workspace, sign-in, unsubscribe pages and the signing service don't use them. They set no cookies and store nothing in your browser. Each visit records the page address with anything after a "?" removed, the site that sent you, your country, your device type, operating system and browser, and how long the page took to load. Vercel tells visits apart within a single day using a code made from the request that resets every day, so no one can follow a visitor from one day to the next or from one site to another. We see totals, not individuals.
We don't sell or share personal information for advertising. If your browser sends a Global Privacy Control signal, our public pages record no visit or page-speed measurement for you, and we honor the signal as an opt-out anyway.
8. How long we keep it
Deletion is a reviewed step, not a silent timer. The system lists what is due, and Noah approves each deletion. That is why some periods below say "about".
| What | How long |
|---|---|
| Intake draft and helper conversation before you submit | No NAC inquiry record before submission. The unsent draft/conversation is kept in browser session storage; browser restoration can retain it. Successful submission or clearing the draft removes the application's saved draft. Provider/security processing has separate retention. |
| Inquiries that don't lead to work | Reviewed for deletion 24 months after our last contact with you, together with the consent record that came with the inquiry. |
| Project working data: uploads, messages and working files | Where the SOW, Order or written promise specifies a shorter period, reviewed for deletion about 90 days after final acceptance. Otherwise retained while reasonably needed to deliver/support the work, then reviewed for deletion; requests and legal holds can change the result. Core proof of the work is kept separately below. |
| Meeting recordings and full transcripts | Normally reviewed for deletion about 90 days after acceptance, or earlier on a valid request, unless an agreed purpose, applicable law or legal hold requires more. Keep only the necessary consent record, approved decisions or other core evidence on the longer record schedule. |
| Deliverables and the versions we handed over | Kept as our record of the work, for the same period as signed records. |
| Signed agreements, SOWs, Orders, change orders, signature/electronic-consent evidence, acceptance and core payment proof | Our normal risk-management baseline is at least 10 years after the later of project closeout or final obligation, subject to applicable deletion rights and exceptions. A dispute, law or legal hold can require longer. This is our schedule, not a claim that every record legally requires ten years. |
| Other invoices, payments, refunds and accounting records | Normally at least 7 years, with core contract/payment proof on the 10-year schedule above and longer retention where tax law, a dispute or a legal hold requires it. |
| Referral records: who introduced whom, and rewards owed, paid or credited | With our accounting records: normally at least 7 years after the last reward. An introduction that never led to work is reviewed for deletion with its inquiry, 24 months after our last contact. A partner's signed agreement follows the signed-records schedule above. |
| Company formation, ownership and tax filings | Permanently. |
| Outreach research on a business we didn't end up working with | The research (the excerpts, the brief, the page we found the address on, and the name and address of the person we wrote to) is deleted 12 months after the lead closes, or after our emails end with no reply. We keep the business name and town, a one-way hash of its domain, the close reason and dates, so we don't re-contact too soon. |
| Outreach send log | 3 years. Each entry carries a one-way hash of the recipient. The record of what Noah approved to send, which shows the address it went to, is kept with it. |
| Opt-outs and do-not-contact entries | Permanently, stored as one-way hashes of the address or domain, so an opt-out keeps working. We never share or sell this list. |
| Security and provider processing logs | According to the applicable service, account plan and security/legal purpose. An application's storage-off setting does not remove all provider logs. |
| Recovery backups and historical archives | Encrypted provider, local and removable/offline copies follow the applicable recovery/archive schedule and legal holds. Deleting a live record may not immediately remove it from an existing recovery point or a retained historical archive. Such copies are restricted to recovery, integrity and justified recordkeeping; approved deletion/suppression decisions are reapplied before restored data returns to ordinary use. |
| A written finding after a security incident that notice wasn't required | 5 years. |
9. Your choices and requests
What you can ask for. Anyone can ask us to:
- tell you what personal information we hold about you;
- send you a copy;
- correct it;
- delete it;
- stop contacting you.
We give these rights to everyone, whatever state you live in.
How to ask. Email help@consultnewage.com, or write to 30501 Utica Dr, Richland, MO 65556. Tell us what you want and which email address we would know you by.
How we check it's you. Normally we confirm through the address on file. If you cannot access it, contact support from a new address: Noah can use proportionate alternative checks appropriate to the records and the request, and records how authority was established before releasing or changing anything. We do not ask you to send ID images through intake, chat or ordinary email. If someone asks on your behalf, we need your written permission and confirmation of their authority. A request does not itself grant access to someone else's records.
When we answer. Our target is 30 days. If we need longer, we aim to tell you why and when within that period. Any applicable statutory response/extension deadline controls.
What may need to be kept. Applicable exceptions may require or permit retaining signed agreements, signing evidence, issued quotes, financial records, necessary request records, or dispute/legal-hold evidence. We assess the request, retain only what is justified, limit its use to that reason, and explain what we kept and why. A minimal opt-out entry remains so deletion does not restart outreach. Existing encrypted backups/archives have the restrictions in §8. When we delete at your request, we also add your address to our do-not-contact list.
Organization data. When information belongs to a client organization, such as project files, we may need that organization's agreement before we release or delete it. One person's request doesn't entitle them to an organization's whole record.
If you disagree with our answer, reply and ask Noah to reconsider. Our target is 30 days, subject to any shorter applicable appeal deadline. You can also contact your state attorney general.
We won't treat you differently for making a request.
10. Emails from us
- Outreach emails to businesses say they are advertisements, show our postal address, and say where we found the address. Every one has a one-page, no-login unsubscribe link, and you can also just reply "stop". We record the opt-out at once, and the law's outer limit is 10 business days. If you ask for your business to be left alone, we suppress the business, not just your address, and that includes in-person visits.
- Service emails keep coming while you use our services, because the service needs them: sign-in and signing codes, signing invitations, a receipt when you send us a request, completed documents, invoices and project notices. They never carry advertising.
- If an email to you bounces permanently, or you mark one of ours as spam, our email provider tells us. We then stop emailing that address and note why on your record. To start again, write to help@consultnewage.com from that address.
11. Children
Our websites and ordinary services are for adults (18 or older). They are not directed to children, and we do not knowingly accept children through our intake. If we learn that a child submitted information, we restrict it and arrange deletion as appropriate, subject to any applicable legal duty or incident-evidence requirement.
12. How we protect it
We use safeguards that fit a small firm and the information involved:
- named accounts and task-appropriate access restrictions, with passkeys or multifactor sign-in where supported; privileged exceptions require owner approval and review;
- each client's information kept separate from every other client's;
- encrypted connections, and storage with providers that encrypt data at rest;
- secrets kept out of code, messages and documents;
- a signed, tamper-evident record for every signature;
- owner approval for commercial commitments, access grants, money movement, material publication and deletion of retained records; routine work may run under previously approved permissions.
No system is completely secure. If you think something is wrong, email help@consultnewage.com right away. Don't include passwords or sensitive documents in that first message.
13. If there is a security incident
If personal information we hold may have been accessed without authorization, we will:
- contain the problem and preserve the evidence;
- investigate what happened, what information was involved and whose it is;
- if we hold the information for a client, tell that client immediately after we discover it, as Missouri law requires of anyone holding data for someone else, and help it meet its own duties;
- notify affected people without unreasonable delay where the law requires it. The notice says what happened, what information was involved, how to reach us, and what you can do to protect yourself, including how to contact the credit bureaus where that's relevant;
- notify the Missouri Attorney General and the national credit bureaus when the law requires it, as it does when more than 1,000 Missouri residents are notified at once;
- follow the law of the state where each affected person lives.
We send a notice by email only to people who have agreed to receive records from us electronically. Everyone else gets it by mail.
14. State privacy laws
Privacy duties vary by residence, the information involved and how a service uses it. Some requirements or sensitive-data rules can apply even to small businesses. We assess the applicable rules for the project instead of assuming a size exemption, honor the choices described here and avoid unnecessary sensitive information. We never sell sensitive information.
15. Changes to this notice
We post each version with its effective date and keep the change log. For a material change, we give website notice and notice to affected active clients when required or reasonably appropriate before the changed practice starts. Equivalent service-provider changes, corrections and security/legal updates need not wait a universal 30-day period; urgent updates may take effect when necessary, with notice as required. We do not use an update to retroactively weaken a prior privacy commitment or authorize an incompatible new purpose, such as model training, without the notice and consent required for that change. A notice update never changes a signed agreement.
16. Contact
New Age Consulting, LLC · 30501 Utica Dr, Richland, MO 65556 · help@consultnewage.com
Change log
| Version | Date | Changes |
|---|---|---|
| 1.0 | Undated draft | First working draft. Never published or dated. |
| 1.1 | 2026-09-28 draft | Restructured by source; added provider, signing, request and retention information. Not approved by this revision. |
| 1.2 | 2026-10-09 | Clarifies browser drafts versus inquiry records, AI training versus provider retention, approved project access and routine automation, practical provider/change notices, authenticated support verification, encrypted backups/archives, deletion exceptions and the proposed ten-year core-evidence baseline. |
| 1.3 | 2026-10-16 | Adds Google API Limited Use and Google-data handling commitments; clarifies the platform's Gmail transport. |
| 1.4 | 2026-10-19 | Adds the Google Calendar connection (bookings, busy times and meetings with Meet links), request receipts, and how bounce and spam reports stop email to an address. |
| 1.5 | 2026-10-22 | Outreach research also finds businesses through public business directories (chamber of commerce, city and visitor-bureau listings, the Better Business Bureau), and may use the address a business published on its own directory listing when it has no website. |
| 1.6 | 2026-10-22 | Names the cookieless visit counting and page-speed measurement on our public web pages (Vercel Web Analytics and Speed Insights), what each visit records, and that Global Privacy Control turns it off. |
| 1.7 | 2026-10-28 | Adds referrals: what we record when someone introduces you or you introduce someone (§3.7), why (§4), what we tell the person who introduced you (§5), and how long we keep it (§8). Corrects §3.3 on how clients sign in. |
Questions about this document: help@consultnewage.com · New Age Consulting, LLC, 30501 Utica Dr, Richland, MO 65556