Privacyand cookies.

Unless separately agreed in a written contract, LightningRevenue does not ask you to submit sensitive personal information through public site forms. This includes protected health information, medical records, precise financial account data, social security numbers, government identifiers, credentials, biometric data, children's data, union membership, political opinions, criminal records, or other highly sensitive information. If you choose to submit such information anyway, you do so at your own risk and you instruct LightningRevenue to process it only as reasonably necessary to receive, review, delete, respond to, secure, or document the submission.

The site is designed primarily for business-to-business inquiries. If you contact us on behalf of an organization, you represent that you are authorized to make the inquiry and that the submitted information is relevant to a legitimate commercial, operational, recruitment, vendor, or partnership purpose.

No website, database, network, transmission method, authentication flow, or operational process can be guaranteed to be completely secure. LightningRevenue uses practical safeguards appropriate to the site and the categories of data processed, but we do not warrant that unauthorized access, disclosure, alteration, loss, interruption, or misuse can never occur.

Analytics, attribution, scoring, campaign source detection, referrer capture, and conversion analysis may rely on technical signals that are incomplete or imprecise. LightningRevenue may use such signals for operational and strategic decisions, but does not represent that analytics records are exhaustive, legally determinative, or suitable as the sole evidence of user intent.

We may refuse, limit, delay, or charge for requests that are manifestly unfounded, excessive, repetitive, fraudulent, technically infeasible, legally prohibited, harmful to others, or impossible to verify. We may also retain limited records needed to demonstrate that a request was handled or denied appropriately.

Name, work email, company name, website, and any contact details you provide when using forms, project inquiries, newsletter signup, or the How Can We Help flow.

You are responsible for making sure any contact information you submit is accurate, current, and submitted with authority to represent the relevant company. If you submit information about another person or organization, you confirm that you have a legitimate basis to do so and that the submission does not violate confidentiality, employment, platform, or contractual obligations.

Service interest, budget range, timeline, selected engagement model, selected pain points, selected outcomes, technology stack, campaign needs, CRM context, and free-text messages.

Project information is treated as business context for evaluation, scoping, qualification, prioritization, and response. You should not submit regulated health data, payment card data, government identifiers, passwords, confidential client records, trade secrets, or any information you are not authorized to disclose unless LightningRevenue has separately agreed in writing to receive and process that type of information.

IP address, user agent, browser information, timestamps, request source, and security metadata generated when your browser communicates with our site.

Technical data may be processed automatically as part of ordinary internet communications. We may use this data to detect abuse, troubleshoot outages, prevent fraud, reduce spam, investigate suspicious activity, maintain logs, support auditability, and preserve the integrity of our site and infrastructure.

Visitor ID, session ID, landing page, page views, referrer, UTM parameters, event timestamps, and attribution links between tracked sessions and submitted leads.

Analytics data is used for aggregate business intelligence, campaign performance, conversion quality, product decisions, and operational review. Analytics data should not be interpreted as a perfect or complete behavioral record. Browser settings, consent choices, blockers, network issues, and device changes can affect completeness and accuracy.

Your cookie choices, consent version, consent timestamp, and the categories you approved or rejected.

Consent records help us respect and evidence your choices. If you clear browser storage, use another device, change browser profiles, or block storage mechanisms, the site may ask for consent again because it may not be able to read your previous preference.

Captures name, email, company, selected pain points, selected outcomes, selected services, IP address, user agent, and the submission timestamp.

We may use this record to identify duplicate submissions, route the inquiry internally, evaluate whether the request is commercially viable, prepare follow-up questions, and maintain evidence of what was submitted and when.

Captures Foundation, Momentum, Apex, or Custom Package interest and the fields submitted through that engagement flow.

We may use this record to identify duplicate submissions, route the inquiry internally, evaluate whether the request is commercially viable, prepare follow-up questions, and maintain evidence of what was submitted and when.

Captures service-specific data for PPC, SEO, web development, software development, UI/UX, SMM, sales setup, and lead generation forms.

We may use this record to identify duplicate submissions, route the inquiry internally, evaluate whether the request is commercially viable, prepare follow-up questions, and maintain evidence of what was submitted and when.

Captures your name, email, company, requested service, budget range, timeline, and message.

We may use this record to identify duplicate submissions, route the inquiry internally, evaluate whether the request is commercially viable, prepare follow-up questions, and maintain evidence of what was submitted and when.

Captures the email address submitted to The Insight newsletter and stores it in the newsletter approved database table.

We may use this record to identify duplicate submissions, route the inquiry internally, evaluate whether the request is commercially viable, prepare follow-up questions, and maintain evidence of what was submitted and when.

A tracked session can include session ID, visitor ID, landing page, referrer, UTM source, UTM medium, UTM campaign, UTM content, UTM term, page path, event name, timestamp, IP address, and user agent.

Lead attribution connects a submitted lead to the consented analytics session that preceded it. This helps us understand which pages, campaigns, referrers, and messages generated legitimate inquiries.

If analytics consent is rejected, optional analytics cookies should not be set and first-party analytics events should not be sent by the browser. Necessary cookies may still be used to operate the site.

Some server-side technical logs may still exist for security, debugging, rate limiting, uptime, or abuse prevention. Rejecting analytics cookies does not prevent all technical processing that is necessary for the site to load or for LightningRevenue to protect its systems.

Attribution can be affected by consent changes, private browsing, ad blockers, browser restrictions, cleared cookies, shared devices, VPNs, network changes, redirects, email clients, and UTM mistakes. LightningRevenue may rely on attribution for internal judgment, but does not guarantee that attribution is complete, exact, or legally conclusive.

Required for security, admin login sessions, form behavior, and basic site functionality. These are always active because the site cannot reliably operate without them.

Examples: admin session cookie, consent storage, basic form/session behavior.

LightningRevenue may update the exact cookie names, duration, or implementation details as the site changes, provided the underlying purpose remains consistent with this policy and applicable consent requirements.

Used only if you approve analytics. They help us understand page performance, traffic sources, visitor sessions, and which content leads to project inquiries.

Examples: LightningRevenue_visitor_id, LightningRevenue_session_id, landing page, referrer, and UTM cookies.

LightningRevenue may update the exact cookie names, duration, or implementation details as the site changes, provided the underlying purpose remains consistent with this policy and applicable consent requirements.

Reserved for campaign measurement and future paid acquisition or retargeting use. These are not enabled unless you approve marketing cookies.

Examples: campaign source, campaign medium, campaign name, ad content, and keyword attribution.

LightningRevenue may update the exact cookie names, duration, or implementation details as the site changes, provided the underlying purpose remains consistent with this policy and applicable consent requirements.

Used to remember non-essential interface choices so the site can feel more tailored over time.

Examples: saved consent preference and future interface preferences.

LightningRevenue may update the exact cookie names, duration, or implementation details as the site changes, provided the underlying purpose remains consistent with this policy and applicable consent requirements.

We rely on consent for optional analytics, marketing cookies, preference cookies, and newsletter subscription where applicable.

You may withdraw optional consent without affecting processing that occurred before withdrawal or processing that LightningRevenue must continue for necessary, legal, security, contractual, or legitimate operational reasons.

We may process inquiry, analytics, and security data to operate the site, respond to prospects, prevent abuse, improve conversion quality, and understand business performance.

These interests include protecting infrastructure, reducing spam, preserving business records, measuring service demand, improving funnels, understanding campaign quality, and avoiding repeated or irrelevant outreach.

When you contact us about a project, we process your submitted information to evaluate the request and prepare a response, proposal, or discovery conversation.

This does not mean LightningRevenue has agreed to work with you, reserved capacity, accepted confidentiality obligations, or committed to pricing, delivery, timelines, or scope before a written agreement is signed.

We may process or retain limited information where required for compliance, accounting, dispute handling, or lawful requests.

Where deletion conflicts with legal, tax, audit, fraud prevention, security, dispute, or evidence-preservation obligations, LightningRevenue may retain the minimum information reasonably necessary for that purpose.

Kept for as long as needed to respond, manage pipeline context, maintain business records, and evaluate whether LightningRevenue can support the request.

We may retain declined, inactive, or duplicate inquiries to avoid repeated qualification work, document prior interactions, prevent abuse, and maintain continuity if you contact us again.

Kept until you unsubscribe, request deletion, or we determine the list record is no longer needed.

We may keep limited suppression or unsubscribe records where necessary to avoid sending future communications to an address that opted out.

Kept for business performance review, attribution analysis, security review, and trend analysis, subject to operational cleanup and deletion requests where applicable.

Analytics may be aggregated, transformed, summarized, or separated from direct identifiers over time. Aggregated or de-identified business intelligence may be retained longer because it no longer reasonably identifies a specific person.

Kept for authentication, security, and session management. Expired sessions may be removed through maintenance processes.

Admin records may be retained for audit, security review, unauthorized access investigation, and internal accountability.

Data deleted from active systems may remain for a limited time in backups, logs, caches, archives, or disaster recovery systems until those systems rotate or are overwritten. We may not be able to selectively remove every residual copy immediately if doing so would compromise integrity, security, or continuity.

Where health-related workflows are relevant, our design direction is to minimize unnecessary data collection, restrict access, and avoid casual exposure of sensitive operational records.

HIPAA Aligned does not mean this public website is intended for unrestricted submission of protected health information, nor does it create a Business Associate Agreement. Any HIPAA-governed engagement must be handled through separate written terms where required.

The site supports consent choices, optional analytics controls, data minimization principles, access/deletion requests, and privacy-first first-party tracking behavior.

GDPR Aligned means the site is designed around privacy principles such as transparency, data minimization, purpose limitation, consent controls, and rights handling. It does not waive LightningRevenue's right to rely on legitimate interests, legal obligations, contractual necessity, security needs, or statutory exemptions where available.

Our operating direction follows structured access control, least privilege, security review, incident awareness, and documented handling of business-critical data.

ISO 27001 Aligned describes the direction of our internal security posture and control thinking. It is not a representation that every LightningRevenue system, vendor, workflow, or engagement is certified unless a current certification is separately published or contractually provided.