Privacy Policy
This Privacy Policy explains how GridLogic Analytics, LLC processes information through its website and point-in-time residential electric-utility analysis service. GridLogic is designed to minimize the personal information needed to perform an analysis.
Effective and last updated: September 5, 2026
Privacy at a glance
- Your browser reads and parses selected electricity-data files locally. Numerical interval values needed for the analysis are transmitted over HTTPS to GridLogic’s protected server-side calculation service.
- Do not include names, utility account numbers, passwords, payment-card information, or other unnecessary personal information in uploaded files or column headings.
- A property address may be processed temporarily for geocoding, electric-utility service-territory screening and, for solar analyses, roof and solar-production estimation.
- GridLogic does not intentionally retain submitted interval electricity data as a reusable raw dataset. For paid analyses, GridLogic retains a private copy of the completed PDF report and limited retrieval information for a 30-day customer-access period as described below. If the property address appears in the PDF, it remains inside that stored PDF during the access period even though the address is not intended to be retained as a separate report-vault database field.
- GridLogic uses the email address returned in the successful Stripe Checkout session to send the initial secure report link and to match replacement-link requests during the 30-day report-access period. GridLogic does not independently verify ownership of the email address entered during checkout.
- Payment-card information is processed by Stripe rather than GridLogic.
- GridLogic does not sell customer personal information or use submitted electricity data, property addresses, or geographic coordinates for behavioral or targeted advertising.
Categories of information and purposes
Depending on the analysis and features you use, GridLogic may process: interval electricity-usage values; solar-production or export values; timestamps and file headings; property address and geographic coordinates; customer-selected utility, rate, solar, battery, interconnection, and modeling inputs; calculated results; transaction and checkout records; technical request metadata; and information you voluntarily provide in correspondence.
GridLogic processes these categories only as reasonably needed to provide and secure the residential analysis, identify or screen utility service territory, model solar production and utility bills, process payments, provide customer support, prevent misuse or fraud, maintain transaction and legal records, and comply with applicable law.
Hourly electricity, solar-production, and export data
Your selected CSV files are read and parsed locally in your browser. GridLogic does not upload the original CSV file itself as part of the standard calculation. After parsing, the numerical interval values needed for the selected analysis—such as electricity usage, solar production, exports, and associated timestamps when available—are transmitted over HTTPS to a protected GridLogic server-side calculation function hosted by Netlify.
The protected function applies GridLogic’s utility-rate, billing-determinant, solar, battery, modeled annual bill, and modeled annual bill-difference calculations and returns calculated results to your browser. The proprietary calculation-engine source code is not sent to your browser.
GridLogic does not intentionally write the submitted interval values to a GridLogic customer database, Netlify Forms, Netlify Blobs, or application logs, and the calculation function is designed to process them for the request and then release them when the request completes. The values necessarily exist transiently in computer memory while the calculation is being performed. Netlify may maintain ordinary infrastructure, security, and traffic metadata under its own practices.
If you choose AI-assisted column detection, file column headings may be transmitted separately to identify likely date, time, usage, production, or export columns. The interval data rows are not included in that AI-assisted header-detection request.
Address, geolocation, and utility-territory processing
The address entered for a residential analysis may be processed temporarily through GridLogic’s server-side services. Depending on the utility and location, the address may be sent to a geocoding provider to obtain geographic coordinates. Those coordinates may then be compared with applicable electric-utility service-territory GIS information to identify or screen the likely electric utility.
Utility-territory screening is not a certified determination of electric service. GridLogic asks the customer to confirm the electric utility shown on the property’s current electric bill.
For a solar analysis, geographic coordinates may also be provided to Google Solar Building Insights or similar services to estimate roof characteristics and to PVWatts to model solar production.
GridLogic does not intentionally use the submitted property address or resulting coordinates for marketing or targeted advertising. The automated workflow is designed not to write the submitted address to a GridLogic customer database, Netlify Forms, Netlify Blobs, or application logs. Service providers may maintain technical or security metadata under their own practices.
Where applicable law treats precise geolocation as sensitive data, GridLogic processes geographic coordinates only for the analysis and service functions described in this Policy and does not use them for targeted advertising or sale.
If the customer chooses to include the address in a report, the address may appear in the resulting PDF. For a paid analysis, GridLogic stores a private copy of that completed PDF for a 30-day customer-access period so the customer can receive a secure email link and request replacement access links. The underlying property address is not intended to be retained as a separate report-vault database field after processing; however, any address printed in the PDF remains inside that privately stored PDF until the report is removed.
Payment processing
GridLogic uses Stripe to process payments. Payment-card information entered during checkout is provided directly to Stripe and is not directly received or stored by GridLogic as complete card information.
GridLogic may receive or retain limited transaction information from Stripe, such as payment status, amount, date and time, transaction or payment identifier, analysis type, the legal-policy version associated with the purchase, and information supplied during checkout as applicable. For paid report delivery, GridLogic uses the email address returned in the successful Stripe Checkout session to send the initial secure report link and to match replacement-link requests. GridLogic does not independently verify ownership of that email address. This information may be used for transaction completion, report delivery and retrieval, customer support, refunds, chargebacks, fraud prevention, accounting, recordkeeping, dispute resolution, and legal compliance.
Records of agreement and purchases
For a paid transaction, GridLogic may retain limited records showing that the purchase terms were accepted, including the transaction identifier, purchase date and amount, analysis type or route, and the version or effective date of the Terms of Use and Privacy Policy associated with the purchase.
These transaction records do not require GridLogic to retain the customer’s submitted interval electricity data or property address.
Optional AI-assisted features
If you use AI-assisted column detection, GridLogic may transmit only the limited file-heading information described above. If an optional AI summary feature is offered and you request it after completing a calculation, GridLogic may transmit a compact set of calculated results and modeling assumptions to OpenAI to generate a plain-language explanation. Hourly files and the property address are not intended to be included in that summary request.
The deterministic utility-bill calculation does not depend on an AI-generated summary.
Reports and information you choose to provide
The protected calculation service returns calculated report data to your browser, where the detailed PDF is generated. After a successful paid analysis, GridLogic stores a private copy of that completed PDF for a 30-day customer-access period and associates it with limited retrieval metadata such as the checkout email address, report code, payment identifier, analysis case or utility identifier, creation/expiration dates, status, and hashed access-token information needed to deliver or re-deliver secure links. The initial secure link currently expires after about one hour. If it expires, the customer may request a replacement link during the 30-day access period using the checkout email address and report code. Issuing a replacement link invalidates the previously issued access token. Raw access tokens are not intentionally stored.
Customer access ends at the 30-day expiration time. A scheduled daily cleanup process then removes the expired PDF and associated application-level report-retrieval record, so physical deletion may occur shortly after access has ended rather than at the exact instant of expiration. GridLogic does not use this feature to retain the original hourly CSV file. If the property address appears in the completed PDF, the address remains inside the stored PDF until that report is removed. Customers should download and save any report they want to keep and remain responsible for protecting copies saved to their own devices.
Customer-facing reports and charts show point-in-time modeled annual bills, modeled annual bill differences, billing determinants, and generalized load, solar, and utility-delivery profiles. GridLogic does not use the analysis to forecast future utility prices or long-term savings. Detailed internal optimization thresholds, optimizer formulations, and other development diagnostics may be omitted from the standard customer report.
If you contact GridLogic by email, through a website contact form, or regarding a purchase or analysis, GridLogic may retain the information you voluntarily provide for customer service, correspondence, recordkeeping, dispute resolution, security, and legal purposes. Do not send utility account credentials, passwords, Social Security numbers, payment-card information, or other sensitive personal information by email.
Service providers and categories of third parties
GridLogic uses service providers only as needed to host and secure the website, perform requested calculations, process payments, provide geographic or solar-modeling inputs, and support optional features. Depending on the analysis, providers may include:
- Netlify — website hosting and server-side functions.
- Cloudflare Turnstile — bot and abuse prevention on selected high-value actions such as running an analysis and requesting a replacement report link.
- Google — geocoding and, where applicable, solar roof information.
- National Laboratory of the Rockies / PVWatts — solar-production modeling.
- Stripe — payment processing and transaction records.
- Supabase — private storage of paid PDF reports and limited report-retrieval metadata during the 30-day customer-access period and scheduled cleanup after expiration.
- Resend — transactional email delivery of initial and replacement secure report links.
- OpenAI — optional AI-assisted features when used.
- Governmental, utility, municipal, or third-party geographic-data services used to screen service territory or obtain public rate and tariff information.
These providers may maintain technical records of requests under their respective policies. GridLogic does not control third-party retention practices.
Sale, targeted advertising, and cross-site tracking
GridLogic does not sell customer personal information and does not use submitted utility data, property addresses, or geographic coordinates for targeted or behavioral advertising. GridLogic does not intentionally use those submitted analysis inputs to track individuals across unaffiliated websites.
Third-party service providers may receive technical information such as IP address, browser information, request time, or similar metadata as part of operating their services and may process that information according to their own policies.
Security and retention
GridLogic uses HTTPS, server-side API credentials, protected server-side calculation functions, request-size limits, rate limits, and Cloudflare Turnstile verification on selected high-value actions as technical measures intended to reduce unauthorized access or abuse. No internet transmission, computation, or storage method can be guaranteed completely secure.
GridLogic does not intentionally retain submitted interval electricity values as a reusable raw customer dataset through the standard automated calculator workflow. Request data exists transiently in system memory while a calculation or verification request is processed. For a paid analysis, the completed PDF report and limited retrieval metadata are retained in private report storage for a 30-day customer-access period. Access expires at the end of that period, and a scheduled daily cleanup process removes the expired PDF and associated application-level retrieval record shortly thereafter. A property address is not intended to be retained as a separate report-vault database field, but it may remain inside the stored PDF if the customer included it in the report. Operational, security, backup, and traffic metadata maintained by service providers is subject to their respective practices.
Payment and agreement records, correspondence, security records, and information submitted outside the automated calculator may be retained for as long as reasonably necessary for transaction support, accounting, recordkeeping, dispute resolution, fraud prevention, security, legal obligations, or other purposes described in this Policy.
State privacy rights and requests
Depending on your state of residence, whether a particular privacy law applies to GridLogic, statutory thresholds and exemptions, and the information GridLogic actually retains about you, you may have rights to request access to, correction of, deletion of, or a portable copy of certain personal information, and to opt out of certain sales, targeted advertising, or profiling.
For example, where applicable, Colorado law may provide qualifying consumers rights to access, correct, delete, and obtain a portable copy of personal data and to opt out of sale, targeted advertising, and certain profiling. Where applicable, Utah law may provide qualifying consumers rights to access, correct, delete, and obtain a portable copy of personal data and to opt out of sale and targeted advertising. GridLogic does not sell personal information or use submitted analysis data for targeted advertising.
Residents of North Carolina, South Carolina, Colorado, Utah, California, Florida, Nevada, Arizona, and other states may submit privacy requests to info@gridlogicanalytics.com. GridLogic will honor rights required by applicable law and may take reasonable steps to verify a request. Listing a state here does not mean that a particular state privacy law applies to GridLogic or that a GridLogic analyzer is currently offered in that state.
Because the standard automated analyzer is designed not to persistently retain submitted interval electricity data or property addresses as separate raw customer records, GridLogic may no longer possess those items when a request is received. A property address or derived analysis results may nevertheless remain inside a privately stored paid PDF during its 30-day customer-access period.
Your choices
- Remove unnecessary personal information from files before selecting them for analysis.
- Use manual column selection instead of AI-assisted column detection when that option is available.
- Skip optional AI-generated explanations when that feature is offered.
- Confirm the utility shown on the current electric bill rather than relying solely on GIS screening.
- Contact GridLogic to exercise any privacy right that applies under your state’s law.
Children, changes, and contact
The paid GridLogic residential service is intended for adults age 18 or older and is not directed to children. GridLogic does not knowingly request children to submit residential utility data or purchase analyses.
GridLogic may update this Policy as its services, supported utilities, providers, or legal obligations change. The effective date above identifies the current version. Material changes will be reflected by updating that date and, where required by law, by providing additional notice.
Questions or privacy requests may be sent to info@gridlogicanalytics.com.