Editorial publication · New York
Privacy Policy
This policy explains what NetNugget records when you read the site or write to us, why we keep it, and how you can ask us to correct or remove it.
Summary of this policy
No selling of data
Personal data is never sold, rented, or traded to advertisers or list brokers.
Contact form only
The only details you hand us voluntarily are the ones typed into the contact form.
Reading data stays broad
Technical logs describe browser, device, and which pages were opened, not who you are.
Requests answered
Ask for access, correction, or deletion of your details and we will act on the request.
Information we collect
Two streams reach us: what you type, and what the browser reports on its own.
What you send us
When you write through the contact form you give us a name, an email address, and the message itself. If your note is a correction to a trend piece or a suggestion for a designer reference we should cover, that text is part of the message and stays with it. We do not ask for a postal address, a birth date, or payment details, because the site has nothing to bill you for.
What the browser reports
Each visit produces a limited technical record: browser type and version, device type, the pages you opened, the date and time of the visit, and an approximate location worked out from the IP address. The location is a region-level estimate, not a street address, and it is never matched back to your name.
What we do not collect
There is no account to create on NetNugget, so there is no password, no profile, and no saved reading list tied to an identity. We do not buy reader lists from third parties and we do not enrich contact form submissions with data from other sources.
Where the records live
Messages and technical logs sit with the hosting and analytics providers that keep the publication online. Access is limited to the editorial team and the people maintaining those services, and only for the purposes described on this page.
How we use information
Every use below follows from running an editorial site that answers its readers. Nothing on this list is marketing, and no contact form submission is added to a mailing list.
Purpose
Reading and replying
A message you send is read by the editorial team so we can respond, chase a correction, or note a designer and fabric you think belongs in a coming guide. We may keep the thread open until the matter is settled. Replies go to the email address you supplied and nowhere else.
Keeping the site standing
Technical records tell us whether pages load, which trend and silhouette guides get read, and where something breaks. They also help us spot automated traffic and abuse, such as a script hammering the contact form. This is maintenance work, not profiling of individual readers.
Editorial decisions
Aggregate page counts tell us which topics deserve a longer guide — seasonal layering, fabric weight, or a designer reference — without identifying who read what. We look at totals and patterns, not at one reader's path through the site.
Cookies and similar technologies
The site sets cookies and uses comparable storage so pages behave the way you expect, and so we can see which guides are read. Some are needed for the site to work at all; others are optional and can be turned off.
The Cookie Policy lists each category, says what it does, and explains how to change or withdraw your choice from the browser or from the on-page controls. Because no account exists here, cookies are never used to sign you in.
Sharing and disclosure
Personal data is not sold, rented, or handed to advertisers. The two situations below are the only ones in which information leaves the editorial team.
Service providers
Hosting and analytics
Companies that keep the publication online and measure its readership may process data on our behalf, and only to the extent that support requires. They work to our instructions and do not receive permission to use reader data for their own marketing.
Legal requirements
Law and safety
Information may be disclosed where the law requires it, or where it is needed to protect the rights and safety of the site and its readers. If a request arrives, we look at whether it is valid and as narrow as the situation allows before responding.
Retention
We keep messages only as long as the matter needs.
A correction thread usually closes within weeks. If a note leads to a lasting editorial decision, we may hold it longer as a record of why a guide changed.
Contact form
Held while the message is open
Then kept for a reasonable period for record-keeping, after which it is removed.
Technical logs
Set by the provider
Hosting and analytics records follow the retention settings of the relevant service.
Aggregate counts
Totals, not identities
Reading totals may be kept longer because they no longer point to a person.
On request
Deleted on a valid ask
Write to the editorial team and we will remove a submission that is no longer needed.
Your choices and rights
You can ask what we hold, have it corrected, or have it removed. There is no form to fill in for this — a written request is enough.
Access
Ask for a copy of the message data we hold about you.
Write to us
Correction
Point out an address or detail we recorded wrongly and we will fix it.
Write to us
Deletion
Request removal of a submission that no longer needs to be kept.
Write to us
Local rights
Depending on your state of residence, further rights may apply to your data.
On request
Requests are handled by the same editorial team that answers reader mail, so expect a reply rather than an automated confirmation. If a request concerns a message you already sent, quoting the original email address helps us find it faster.
Questions readers ask about this policy
Do you sell anything, and does that change what you collect?
NetNugget is an editorial publication. There are no product listings, no cart, and no checkout, so no payment or shipping details are ever requested or stored. The data described on this page is limited to contact form submissions and technical visit records.
Will writing to you put me on a mailing list?
No. Contact form submissions are used to read and answer your message, and for nothing else. There is no newsletter attached to the form, and your address is not passed to anyone for promotional purposes.
Can I read the site without accepting optional cookies?
Yes. Guides and designer references load without optional storage. Turning optional categories off limits the reading statistics we collect, but it does not hide pages or block any part of the publication.
How will I know if this policy changes?
The revised version is posted on this page, replacing the text you are reading now. If a change affects how contact form data is handled, we will say so in plain language in the updated section rather than leaving readers to compare versions.
Children's privacy
The site is not directed at children, and personal data from children is not knowingly collected.
If you believe a child has sent us personal details through the contact form, write to the editorial team and we will remove the message.
Changes to this policy
This policy may be updated as the publication changes. The revised version is posted on this page and applies from the moment it appears.
Contact the editorial team
Questions about this privacy policy, or a request about data you have sent us, can go to the editorial team using the details below. There is no separate privacy department — the same people read reader mail and handle these requests.
Working hours are Monday to Friday, 9:00 AM to 6:00 PM. If your question is about a correction or a designer reference rather than data, the contact page explains which route fits best.