Who we are
No Fluff Advisory is an operator-led advisory platform for AdTech, MarTech, data, SaaS, media, and technology companies entering or scaling in the US.
Website: https://nofluffadvisory.com
Information we collect
We may collect information in a few ways:
1. Information you provide
You may choose to share information when you:
- submit a contact form
- request a call
- complete a scorecard or diagnostic
- email directly
- interact with advisory, consulting, or business development materials
This may include your name, email address, company, role, website, business context, and any information you include in your message.
2. Website usage information
Like most websites, we may collect basic technical and usage information, such as:
- pages viewed
- browser type
- device type
- referring pages
- approximate location
- time spent on site
- interaction with content, scorecards, or forms
This helps improve the website, content, and user experience.
3. Local browser storage
Some features, such as scorecard results, saved content, or preference settings, may use browser-based local storage. This means the information is stored on your device and is not necessarily transmitted to No Fluff Advisory unless a feature explicitly asks you to submit it.
You can clear this information through your browser settings.
How we use information
Information may be used to:
- respond to inquiries
- schedule calls
- provide advisory or consulting information
- improve website content and functionality
- understand which topics are useful to visitors
- maintain website security
- personalize or improve future interactions
- support legitimate business operations
We do not sell personal information.
Scorecards and diagnostics
The website may offer readiness scorecards, assessments, or diagnostic tools. These are designed to provide practical guidance based on your inputs.
Unless otherwise stated, scorecard results may be stored locally in your browser. If you choose to submit your details or request follow-up, the information you provide may be used to respond to you and discuss relevant services.
Scorecards are for informational purposes only and do not create an advisory relationship.
Ask Evgeny and yevgeny.ai
Ask Evgeny is the question-answering service behind the chat box on this site, the site at yevgeny.ai, and the MCP connector that lets an AI client query the same corpus. It answers only from published writing. This section describes what it does with what you type, and is written to match the running system rather than the intent behind it.
What is stored
- Your question, in the words you used. A question that reaches the answering engine is stored so answers can be reviewed for quality and so gaps in the writing can be found and filled. It is kept as text, truncated to the first 500 characters, alongside whether it was answered, whether it arrived from the web or the MCP connector, and the time. On this site and yevgeny.ai, a repeat of a question already in the answer cache is served from that cache and is not stored again. Questions asked through the MCP connector are stored every time.
- Two random identifiers, if you ask on this site or yevgeny.ai. Your browser creates one identifier for each conversation and another that it keeps in local storage. Both are stored with each question, and the browser identifier with any rating or comment, so a multi-turn conversation can be read in order and questions from the same browser can be linked. Neither contains your name or IP address. Clearing a site's data in your browser removes its stored identifier, and the chat creates a new one.
- Feedback you volunteer. If you rate an answer or leave a comment, the rating and comment are stored with it.
- An email address, only if you give one. Requesting an API key stores the address you submit alongside a hashed copy of the key. The key itself is never stored in readable form. Every question you ask through the MCP connector is stored with that address, which shows which key holder asked it.
- Daily usage counts for an API key. For each day a key is used, the number of requests and tool calls it made that day is stored against the hashed key, so usage can be measured over time. The record holds counts only, not what was asked.
- Diagnostic traces. Retrieval traces record timings and internal scores so the system can be debugged and measured. They store a shortened SHA-256 fingerprint of your question and its length rather than the text, which lets identical questions be grouped without keeping what was asked. Treat that as pseudonymised, not anonymous: the fingerprint is unsalted, so a short or predictable question could in principle be matched by guessing it. Traces are deleted after 90 days.
No account is required, and no IP address, name, or location is recorded alongside a question. Answers on this site and yevgeny.ai are cached so repeated questions can be served quickly.
Who else sees your question
Answering a question requires sending it to services that generate and retrieve text. In the ordinary course of answering, your question is sent to Anthropic (to write the answer), Cloudflare Workers AI (to turn it into a vector for search), and MADDB, an advertising-industry database used to add current context where a question calls for it. Each handles the text under its own terms. If you request an API key, the email address you supply is sent to Resend to deliver it. Nothing you type is sold, and it is not used to advertise to you.
How long it is kept
Questions, feedback, unanswered-question records, and daily API-key usage counts are deleted automatically 90 days after they are recorded, by a job that runs once a day whether or not anyone visits. Retrieval traces expire on the same 90-day window. Two things are deliberately outside it: a question featured on yevgeny.ai, which has been published deliberately and stays until unfeatured, and an API key with the email address attached to it, because a key is a live credential and deleting it on a timer would break a working integration without warning. Keys are removed on revocation or on request. Anything covered here is also removed on request, before the window runs out.
Analytics on yevgeny.ai
yevgeny.ai uses Google Analytics 4, loaded only after your first interaction with the page. It measures how the site is used — which answers get copied, shared, or rated, and how long a typed question was. The text of your question is never sent to analytics.
Your choices
Do not type anything into Ask Evgeny that you would not want stored: it is a public question box, not a confidential channel, and it is not a route for personal, financial, or health information. To have a question, a comment, or an API key removed, or to ask what is held, contact us using the details at the end of this policy and say when and roughly what you asked, so it can be found.
Cookies and analytics
This site uses Google Analytics 4 (GA4) to measure
aggregate page views, traffic sources, and engagement. GA4 sets
first-party cookies (such as _ga) to distinguish
visitors and sessions. We use it for aggregate site measurement
only: we do not use Google Signals, advertising features, or
remarketing audiences, and we do not build a cross-site profile
of you.
We never send your form messages, email address, name, or scorecard answers to any analytics provider. Custom events carry only non-identifying context (page path, button label, content type). The readiness scorecard runs in your browser and its results are stored only on your device.
You can block or clear analytics cookies with your browser settings or a content blocker; the site works fully without them. See Google's privacy policy for how Google processes analytics data.
Sharing information
We may share information only when necessary to operate the website or business, such as with:
- website hosting providers
- form or email service providers
- analytics providers
- scheduling tools
- professional advisors
- service providers supporting business operations
We may also disclose information if required by law, regulation, legal process, or to protect the rights, security, or integrity of No Fluff Advisory.
Third-party links
This website may link to third-party websites, publications, platforms, tools, or social profiles. No Fluff Advisory is not responsible for the privacy practices or content of those third-party sites.
You should review their privacy policies before providing personal information.
Data retention
We keep information only as long as reasonably needed for the purposes described in this policy, unless a longer retention period is required or permitted by law.
Business correspondence may be retained for relationship management, legal, accounting, or operational reasons.
Your choices
Depending on your location, you may have rights to:
- request access to personal information
- request correction or deletion
- object to certain processing
- withdraw consent where applicable
- request that certain information not be sold or shared
No Fluff Advisory does not sell personal information.
To make a privacy request, use the contact page: https://nofluffadvisory.com/contact/
Security
We use reasonable technical and organizational measures to protect information. However, no website, system, or transmission method is completely secure.
Please do not submit sensitive personal, financial, medical, or confidential business information through public website forms unless specifically requested.
Children’s privacy
This website is intended for business and professional audiences. It is not directed to children, and we do not knowingly collect personal information from children.
Changes to this policy
This policy may be updated from time to time. The updated version will be posted on this page with a revised “Last updated” date.
Contact
For privacy-related questions or requests, please contact No Fluff Advisory through: https://nofluffadvisory.com/contact/