Effective October 21, 2026. This policy covers bigchange.ai, newsletter registration and correspondence with BIG CHANGE. The publisher and controller of the personal information described here is Powerhub Inc., a company incorporated in Delaware, United States. “We”, “us” and “our” refer to Powerhub Inc.
For privacy questions or requests, email hello@bigchange.ai. You can read the publication without an account, a newsletter subscription or optional analytics. Our Cookie Policy explains browser storage in more detail; our Terms of Use cover use of the publication.
Information we collect and use
When you visit the publication
Our hosting and security provider, Cloudflare, receives the information needed to deliver your request, including your IP address, requested URL, request time, browser information and connection details. This supports page delivery, error diagnosis and protection against abusive traffic. Information in security and diagnostic records may also help us investigate an incident. This processing occurs when you connect to the site, including when you decline optional analytics.
We remember your privacy choice in your browser. The editorial administration system separately uses authentication information for authorised staff; reading our stories does not create an editorial account.
We display an aggregate view count beside published stories. Since October 7, 2026, it counts successful full-article requests and opened “The big change” previews immediately, without a reading-time or scroll requirement. Full requests include people and bots, with or without JavaScript. Language versions share one article total. Browser-cache restores are counted separately without repeating the original server event. This first-party counter stores no IP address, browser identifier or cookie and does not itself send events to Google Analytics. It does not measure unique people or prove someone read the text. Previously recorded reads since September 30, 2026 are retained; earlier unrecorded visits cannot be reconstructed. Preview and cached-open requests are protected by daily rotating IP-derived rate-limit values, removed during daily cleanup. If you allow Google Analytics, opening a preview also sends an article-view event to Google.
We host the publication’s typefaces with our site assets on Cloudflare. Reading our pages does not request fonts from Google Fonts.
Private operational reports also use daily aggregate open counts by source article, content language and surface, with separate explicit-test, identified-bot and unclassified totals. These counters store no IP address, user agent, email, full address, browser identifier or person-level event log. Daily buckets follow a 90-day retention window and are removed during routine cleanup. They do not identify people or prove reading. Unknown automation can remain in unclassified totals. Public lifetime totals remain separate and include bots.
Audience analytics and regional choices
When analytics is allowed, we measure qualified article engagement separately from an article open: at least 30 seconds of active, visible body exposure and 50% progress through the body. Optional tab-session storage prevents repeat outcomes for the same source article. It contains article IDs only and is removed when analytics is turned off. This is an attention estimate, not proof of comprehension, unique people or Google’s engaged-session metric.
Google Analytics receives information about your page visits and selected interactions, such as opening an article, scrolling through a story, clicking a contact link or following an external link. It also processes browser and device information, approximate geographic location, referring websites, campaign identifiers and cookie identifiers. We use these reports to understand our readership, improve the publication and assess interest in our services.
The Google tag starts automatically for connections detected in the United States, Australia or New Zealand unless you have opted out. For all other locations, or if location detection fails, it waits for your acceptance. We use Cloudflare’s connection-country information, not device-location permission, to choose this default. An automatic start is not stored as your acceptance. Saved refusals and Global Privacy Control or Do Not Track browser signals keep Analytics off. Our Cookie Policy explains these rules and preference durations. Google Signals and advertising personalisation are disabled. Our event configuration does not intentionally send your email address, correspondence, free-text searches or newsletter form contents to Google. We remove arbitrary query parameters from reported page addresses and restrict campaign parameters. A contact-click event tells us that someone clicked a link; it does not reveal the email they wrote or establish that a sale occurred.
Select Privacy settings at the bottom of any page to change your choice. Turning analytics off stops future collection through our tag and removes the Google Analytics cookies set for this site. It does not automatically erase records already received by Google. You can contact us about a separate deletion request. Read Google’s explanation of information it receives from partner sites.
When you send feedback
The feedback form sends your message, category, optional topic, page path, selected language and mobile or desktop context to our team through Resend. Your name and email are optional. We use this information to investigate issues, consider suggestions and respond if you request a reply. It is kept in our editorial email correspondence, not added to our newsletter list. Cloudflare Turnstile checks submissions for spam. Our server also uses a daily rotating protected value derived from your connection IP address to limit abusive requests; the raw IP address is not included in the feedback email.
If you request the newsletter
We also store your chosen newsletter language and send that preference to Resend to select the matching edition. It starts with your website language, but you can choose a different newsletter language without changing the website. A language change takes effect after email confirmation.
We collect the email address you enter, the time of your request, the version of the consent statement you accepted and your subscription status. We also record your selected frequency, confirmation time and subsequent preference changes. Resend holds delivery and unsubscribe records. Access to subscriber records is restricted to authorised administrators.
We send an address-confirmation email through Resend. Your daily, weekly or monthly subscription becomes active only after you confirm. Changing frequency through our website also requires email confirmation. Every edition includes an unsubscribe link. The newsletter may include clearly labelled sponsorships, as stated beside the signup checkbox. Newsletter consent is separate from analytics consent, and we do not give sponsors our subscriber list.
To limit automated submissions, the signup service temporarily records a protected, derived value of the connecting IP address and email address, and request counters. The subscriber record does not store your raw IP address. This protection is for abuse prevention, not advertising or a browsing profile.
Separately, when analytics is allowed, restricted first-touch and last eligible paid-touch campaign context and signup placement may be retained for seven days. A random browser receipt, valid for 24 hours, can connect that context to a first confirmation in the same browser. Refusing analytics removes browser context; it does not prevent subscribing. We do not place campaign context in the confirmation link or give confirmation receipts to Google. Permitted first-confirmation events may include cadence, newsletter language, source article, content language and restricted campaign keys, without your email address or secret confirmation token. A confirmation on another device without a matching receipt remains unattributed.
We retain the first confirmed subscription time, frequency and newsletter language as business records without replacing them when preferences change. Older subscriptions are not given invented acquisition histories. Optional server campaign detail is removed after 90 days, and pending campaign context expires after 24 hours through routine cleanup. Business consent and suppression records follow the subscription retention rules below.
If you turn on notifications
With your permission, BIG CHANGE stores a device-specific push subscription endpoint and encryption keys in Cloudflare’s database, along with the times you enabled and last refreshed it. We use these only to send alerts for newly published stories and major follow-ups. A major follow-up requires an editor’s documented importance and urgency assessment; it may be sent after that assessment reaches our system. The push provider used by your browser or device receives an encrypted message and delivery metadata. The alert title can appear on your lock screen or desktop. This choice is separate from analytics and newsletter consent; no email address is needed.
Use Notifications to stop alerts on each device. Turning them off removes that device’s server subscription and asks the browser to unsubscribe. We also remove subscriptions when a push provider says they have expired or been revoked. Delivery records are kept to prevent duplicate alerts and are removed when the associated subscription or article is deleted.
If you like or share a story
When you click Like, we save your choice using a random browser cookie and a separate derived identifier for that article in our Cloudflare database. We store the article, derived identifier and time of the like, without a name or email address. Click again to remove your like. The browser cookie expires after 180 days; the saved reaction remains until removed or the article is deleted. Clearing cookies or using another device may prevent us from recognising a previous like. Public totals are reactions, not verified unique people.
To limit abuse, we use a daily rotating, protected value derived from your connecting IP address for request counters, removed during daily cleanup. Sharing controls open your chosen service only when you use them; we do not embed social-network tracking widgets. That service handles the information you choose to share under its own terms. Suggested reading uses story topics and publication dates, not a personal browsing profile. If you allow analytics, we also measure like actions, sharing-control use and suggested-reading clicks.
If you rate a guide or explanation
On published guides and explanations, you may choose “Yes” or “Not yet” to tell us whether the article helped. If you respond, we save that choice, article and time with a random browser identifier and a separate derived value in our Cloudflare database. We do not ask for a name, email address or free-text explanation. The identifier lets us count one current response per browser and article and lets you change it. The browser cookie lasts up to 180 days; the response remains until the article is deleted. Feedback is optional, is not sent to Google Analytics and is not required to read an article. We use aggregated responses to improve guides and, when at least five responses exist, as a modest newsletter-selection signal. Responses are self-selected and do not represent all readers. The API receives the connection details needed to deliver and protect your request; a rotating protected IP-derived value limits abuse.
If you contact us
We receive your email address, any name or other details you provide, message contents and attachments. We use them to answer the inquiry, investigate a correction or privacy request, and manage any resulting business relationship. Email correspondence is handled through our Google Workspace account. Please send only the information needed for your request and avoid including passwords, payment-card details or unnecessary sensitive information.
Information in our reporting
Stories may refer to people in their professional or public roles and use information from published research, company announcements, public statements, interviews or material sent to the editorial team. Publication makes that information available to readers and search services. If a story contains inaccurate information about you, contact editorial@bigchange.ai with the article address and the issue. We assess requests in light of accuracy, public interest and applicable rights.
Our reasons for processing information
Where European or UK data protection law applies, we rely on consent for optional analytics and newsletter marketing. You may withdraw that consent at any time. Withdrawal does not change the lawfulness of processing carried out before it.
For delivering and securing the site, handling ordinary inquiries and maintaining relevant business records, our legitimate interests are running a reliable publication, preventing abuse and responding to people who contact us. If you request a paid service, processing needed to prepare or perform our agreement may instead be based on that contract. We may also retain or disclose information to meet a legal obligation. Editorial processing is subject to the applicable rules protecting journalism and freedom of expression.
You are not required to provide an email address to read the site. An address is needed to register for the newsletter or receive an email reply.
Who receives information
Cloudflare provides hosting, network security and storage, including the database containing newsletter requests and push subscriptions. Google provides our optional Analytics service and Workspace email. Resend processes subscriber email addresses, chosen newsletter frequencies and delivery events to send confirmations and newsletters, manage unsubscribes and suppress undeliverable addresses. Email open pixels and individual click tracking are disabled; newsletter links may carry campaign tags for our optional site analytics. If you enable notifications, your browser’s push provider, such as Apple, Google or Mozilla, handles encrypted delivery to your device. These providers process information needed to perform their respective services, under their applicable service, privacy and data-processing terms.
We may provide information to professional advisers where needed to resolve a legal or business matter, or to authorities where a valid legal obligation requires it. If the publication changes ownership, relevant records may form part of that transaction, subject to applicable privacy requirements and notice of material changes.
We do not sell subscriber lists or provide reader information to sponsors for their own marketing. We do not currently use advertising pixels, cross-site advertising profiles or automated decisions about readers that produce legal or similarly significant effects. Links to other websites take you to services with their own privacy practices.
Where information is processed
Powerhub Inc. is a US company. Cloudflare, Google and Resend operate international infrastructure, so information may be processed in the United States and other countries outside your country of residence. Local privacy protections can differ. Their published data-processing terms describe the transfer arrangements they offer, including contractual safeguards where applicable. Contact us to request information about the arrangements relevant to your information.
Provider information is available in the Cloudflare Data Processing Addendum, Google Workspace data-processing terms Google advertising and measurement data-processing terms and Resend’s data-processing terms.
How long we keep information
- Privacy preference: valid for 180 days in the browser where you made the choice. Clearing browser storage removes it earlier.
- Pending newsletter requests: expire after 30 days and are removed by scheduled daily cleanup or an earlier signup cleanup. You can ask us to remove a pending request sooner.
- Confirmed subscriptions: kept while subscribed. Confirmation links expire after 24 hours; expired token records are removed during routine cleanup. After an unsubscribe, limited consent and suppression records may be retained to respect your choice and document past consent.
- Signup abuse prevention: derived IP and email values rotate daily. Expired request counters and derived values are removed during routine daily or signup cleanup.
- Correspondence and business records: kept while needed to address the matter, manage an ongoing relationship, resolve a dispute or meet applicable recordkeeping obligations. The nature of the inquiry and any legal obligations determine the period.
- Security records and analytics: retention depends on the type of record and the applicable service settings. We use these records for operational investigation and readership reporting; aggregated reports may remain after individual event records expire.
Deleting an active record may not immediately remove copies from backups or records that must be retained for a legal obligation. Any such copies remain subject to appropriate access restrictions and their applicable retention cycle. Cookie lifetimes are listed separately in our Cookie Policy; a cookie lifetime is not the same as server-side retention.
Your choices and rights
You can keep analytics off, change your browser preference at any time and ask us to remove a newsletter request. Every newsletter edition includes an unsubscribe option. Change your frequency at /newsletter and confirm the requested change by email. You can also contact us directly to stop marketing.
Depending on the law that applies to you, you may have rights to access and receive a copy of your information, correct it, request deletion, restrict processing, receive portable data or appeal a decision about your request. These rights can have exceptions, including for legal obligations and protected editorial activity.
You may object to processing based on legitimate interests, and you may object to direct marketing at any time. Send requests to hello@bigchange.ai. Describe the request and the address or interaction it concerns. We may ask for proportionate information to confirm your identity; do not send identity documents unless we explain why they are needed. We will respond within the period required by applicable law and explain any lawful limitation or refusal.
You may complain to your relevant privacy regulator. UK residents can contact the Information Commissioner’s Office; people in the European Economic Area can find their authority through the European Data Protection Board. Contacting us first is welcome but is not a condition of exercising that right.
Children and security
BIG CHANGE is a general-interest publication and does not direct newsletter registration to children under 16. We do not knowingly collect newsletter registrations from them. If you believe a child has submitted personal information, contact us so that we can investigate and remove it where appropriate.
We use access controls and service protections appropriate to the systems we operate. No internet service can guarantee absolute security. Please report a suspected exposure involving this site to hello@bigchange.ai.
Changes to this policy
We will update this page when our practices change and revise its effective date. Material changes will receive an appropriate notice. If a new purpose requires consent, we will request it before using information for that purpose.