Privacy Policy

Effective date: October 27, 2026

This policy describes what information is handled when you read bigsignmessage.com, a blog about Times Square, New York events and wedding proposals. The operator is the person or organisation running the blog, and the words we and us refer to the operator.

Visit logs

The servers that deliver our pages keep ordinary logs. An entry can show your IP address, the time of your visit, the article you opened, your browser and device type, and the page that sent you here. We use logs to keep the blog online, to investigate errors and abuse, and to see in broad terms whether readers prefer Times Square guides, event roundups or proposal ideas.

Cookies and similar technology

The blog may use cookies or similar storage. Some help pages load properly. Others, where enabled, count audiences, remember a setting, support advertising, or record that a reader arrived at a ticket seller, hotel or proposal-related service through a link here so that affiliate attribution works. A cookie dropped by an ad network or an embedded video is under that provider’s control, not ours, so its notice is the place to look for details.

Browser controls and opt-out signals

You can block or clear cookies in your browser, browse privately or use tools that limit tracking. If your browser sends a do-not-track or global privacy signal, we will honour it as an opt-out where the tools we use are able to. Blocking some cookies may change how certain features appear.

Emails and forms

If you write to [email protected], we receive your address and whatever you include. A reader planning a proposal may share personal details about a partner or a date; please share only what you are comfortable with. Your message is used to answer you, to fix a page that got something wrong and to remember what was already discussed. We do not sell messages and will not publish them without asking you first.

Newsletters

If a newsletter or sign-up form is offered, the details you enter are used to send what you requested, such as event updates. Each message explains how to unsubscribe, and you may also ask us by email.

Outside services

Running a blog involves other providers, which may include hosting and delivery networks, analytics tools, advertising and affiliate networks, and embedded maps, videos or social posts about New York locations. They may receive technical information about your visit so their service works, and they act under their own privacy notices.

How long information is kept

Raw visit records are held only for a short working window, after which they are erased or boiled down to totals that cannot point to a single reader. Emails stay while they help us answer you, fix an article or meet a legal duty, and are deleted once that need ends.

Your rights

Depending on where you live, you may be able to ask what personal information we hold about you, have it corrected or deleted, object to certain uses, or withdraw consent you gave earlier. To make a request, email [email protected] and say what you would like. Before acting on a request we may ask you to prove the message really comes from you, and we will answer within whatever period applies where you live.

Children

Bigsignmessage is written for a general adult audience, including couples planning engagements, and is not aimed at children under 13. Nothing on the blog is designed to gather details from young children. If you believe a child has sent us something, tell us and we will delete it.

Security

Pages are served over encrypted connections, and only the operator can open the inbox that receives your emails. Even so, no system on the internet is perfectly secure, so we cannot guarantee absolute protection.

International transfers

Many readers visit from outside the United States, and our providers may process data in several countries. Those countries may have privacy laws that differ from yours, and by using the blog you accept that your information may travel in this way.

Changes to this policy

This policy will be updated if the way the blog handles information changes, for example when a new analytics or advertising tool is added. The effective date above shows when the current version began, and continuing to read the blog after a change means you accept the updated policy.