1. Responsibility & scope
Bidemi Ologunde, operating as IntelEdge360 in Tampa, Florida, is responsible for deciding how information submitted to this website is used. This policy covers inteledge360.com and its hosted website, inquiry forms, publication-download forms, and associated site operations. Contact us through the Contact page or at +1 (702) 983-0499. No unconfirmed email inbox is listed as a privacy contact.
Client consulting records may be governed by a separate engagement and data-processing agreement. A client may be the controller and IntelEdge360 its processor, or each may have independent responsibilities depending on the assignment. This policy does not authorize a client to disclose someone else’s information unlawfully. Applicable laws depend on location, processing, and statutory thresholds; this notice is not a claim that every global law applies or that compliance has been certified.
2. Information collected & where it comes from
Inquiries: the name, email address, organization if supplied, selected service area, project description, and whether you request a consultation call. These are provided directly by you and stored as an inquiry record with its creation time.
Publication downloads: full name, work email address and its domain, organization, optional job title, requested publication, optional publication-update preference, and the request’s creation time. Personal and disposable email providers are blocked. A server-side domain check sends only the email domain, not the full address or form contents, to Cloudflare’s DNS resolver to check whether the domain receives mail.
The forms include a hidden anti-spam field. Network requests to hosting, file storage, and other providers necessarily expose connection information such as an IP address, request metadata, and browser details to those providers. Operational logs and error reports may contain request or diagnostic information; avoid sensitive details in forms. The site does not intentionally collect payment-card information, government identifiers, health records, biometric templates, or precise location through these forms.
3. Uses, purposes & lawful bases
Inquiry information is used to assess your request, respond, arrange a requested call, and discuss a possible engagement. Download information is used to enforce the work-email requirement, record the request, provide the chosen publication, and administer or protect the service. Submission does not enroll you in unrelated marketing.
Where GDPR or UK GDPR applies, processing necessary to take steps at your request toward a contract may rely on Article 6(1)(b). Ordinary professional correspondence, publication administration, abuse prevention, and appropriate record keeping may rely on Article 6(1)(f) only where a legitimate interest, necessity, and balancing of your rights support it. Specific legal obligations may require processing under Article 6(1)(c). Optional publication updates rely on your affirmative choice and, where required, consent under Article 6(1)(a); you can withdraw without affecting an earlier lawful use or the download.
The publication-update checkbox is optional and initially unchecked. The current site records that choice; it does not automatically send a newsletter or email every inquiry to an inbox. If updates are sent, they must follow your recorded preference and applicable email rules, including CAN-SPAM, Canada’s CASL, and relevant European or UK electronic-marketing requirements. An inquiry is permission to respond to that inquiry, not consent for an unrelated campaign.
The site has no AI chat or form-analysis feature and does not use these forms for automated decisions with legal or similarly significant effects. The work-email eligibility check is a limited access rule, not a credit, employment, or risk assessment. Contact us if it incorrectly blocks your organization. No use of submitted website information to train an AI model is part of the stated purposes.
4. Visitor analytics & click recording
Lovable visitor analytics and click tracking are enabled on the published site. There is currently no consent banner passing a choice to Google Consent Mode. Clicks on links and buttons are therefore recorded for visitors without a banner choice, subject to Lovable’s built-in handling of browser privacy signals. Page visits, time on page, page speed, and errors are recorded for every visitor, without cookies and without identifying anyone. The editor preview is not counted.
Lovable’s analytics records pages visited, where visitors came from, country, browser, operating system, device type, time on the site, page-load performance, errors, and clicks. The site reports caught page errors but sends no separate custom business events. The analytics uses no cookies, stores nothing on the visitor’s device, does not keep IP addresses, and does not identify visitors or recognize a returning person. Detailed data is kept for 90 days and daily summaries for one year.
Lovable collects this data for us. Lovable’s privacy policy explains how it handles it. Cookie-free analytics does not mean the whole site stores nothing: form records, browser-saved download details, and providers’ operational processing are separate and described below. Privacy and consent requirements differ by country and should be assessed for the places our visitors are located.
5. Browser storage, fonts & external websites
After a successful publication request, the site saves your full name, work email, organization, and job title in your browser’s local storage under ‘pub-download-profile’ to prefill later download forms. It is not a cookie and currently has no automatic expiry. It remains until you clear this site’s stored data or the browser removes it; clearing it does not delete the separate request record. Consider this before downloading on a shared device.
The public inquiry and download journeys do not require a visitor account. If a managed authentication session is used, its session information may be stored in browser storage for sign-in; it is separate from visitor analytics. Authentication email support does not automatically subscribe a visitor to marketing.
The site loads Cormorant Garamond and Karla fonts from Google Fonts. Your browser sends Google connection information, including an IP address and request headers, when it loads them. Site images are delivered through hosting/CDN services with similar necessary connection information. The site does not embed podcast players or social feeds and has no advertising pixel or separate advertising analytics configured in its public pages.
Links to LinkedIn, Substack, podcast services, CyberBay, legal sources, and other outside sites take you to services governed by their own notices and storage practices. They receive the connection information your browser sends when you follow a link. Their policies, not this one, govern activity on those sites.
6. Recipients, disclosures & security
Bidemi Ologunde accesses inquiry and download records to administer the practice. Lovable Cloud and its infrastructure providers process and store form records and private publication files to operate the site; hosting/CDN providers deliver pages and media. Lovable processes visitor analytics. Cloudflare receives the email-domain DNS query. Google receives font requests. Providers process information subject to their own terms and applicable contractual restrictions.
Information may also be disclosed to professional advisers or authorities when necessary for a legal obligation, lawful request, claim, security issue, or protection of rights. Any transfer arising from a reorganization or sale of the practice must remain subject to applicable privacy requirements and appropriate notice. We do not sell submitted inquiry or download records, rent contact lists, or share them for cross-context behavioral advertising.
Lead records are not publicly readable through the site. Publication files are private and accessed through short-lived signed links, issued after a request is recorded; links last ten minutes and should not be forwarded. These access controls reduce exposure but no internet service can guarantee absolute security. Applicable incident-notification duties must be assessed if a personal-data breach occurs, including GDPR Articles 33–34 and Florida’s Information Protection Act where relevant.
7. Retention & deletion
Our retention policy is to keep inquiry and publication-download records for 36 months after our last contact with you, then delete or anonymize them unless a legal obligation or a documented need relating to a claim requires longer retention. If there is no further correspondence, the request date is the starting point. Valid deletion requests may require earlier removal. The current site does not automatically track later correspondence or delete expired records: implementing this policy requires manual review and deletion. You may request deletion through the Contact page or by phone, subject to applicable legal exceptions and proportionate identity checks.
The ten-minute download-link expiry does not delete your request record. Browser-saved profiles and analytics have the separate retention periods explained above. Backup and provider-log retention can differ from active records; deletion may require backup expiry rather than immediate removal from every copy. We do not represent that an automated erasure system or a uniform provider-wide retention period is already configured.
8. International processing
IntelEdge360 operates in the United States and uses providers whose processing may occur in the United States and other countries. Legal protections may differ from those in your country. This notice does not verify a single storage region for all infrastructure or claim that every provider is covered by an adequacy decision.
Where a restricted international transfer is subject to GDPR or UK GDPR, the applicable route must be established, such as a valid adequacy decision or appropriate contractual safeguards and any required transfer assessment or supplementary measures. GDPR Chapter V, EU Standard Contractual Clauses, and the UK IDTA or Addendum are relevant frameworks; this policy alone is not a transfer safeguard. Ask about the processing arrangements before submitting information subject to special location or transfer restrictions.
9. Your rights & how to exercise them
Depending on the applicable law, you may have rights to notice and access, correction, deletion, restriction, portability, objection to legitimate-interest processing, withdrawal of consent, and opt-out of sale, sharing, targeted advertising, or certain profiling. Sensitive-data restrictions, authorized-agent requests, and an appeal of a denied request may also apply. We do not discriminate against you for exercising an applicable privacy right.
Use the Contact page with ‘Privacy request’ in the project description, or call +1 (702) 983-0499. Identify the email you used and the requested action without submitting identity documents or sensitive records initially. Verification will be limited to what is reasonably necessary. We will explain any legal exception or denial and applicable appeal route. An inquiry form submission is not automated fulfillment of a rights request.
Where GDPR or UK GDPR applies, requests generally require a response within one month, with a permitted extension of up to two additional months for complexity or volume and notice within the first month. Where the CCPA applies, verifiable access, correction, and deletion requests generally require a response within 45 days, subject to permitted extensions. Other laws have different deadlines. You may complain to your competent regulator, including an EU/EEA supervisory authority, the UK ICO, or the relevant state or national privacy authority.
Global Privacy Control is relevant to legally required opt-outs of sale or sharing. This site does not sell or share submitted records for cross-context advertising, and Lovable’s analytics has built-in handling of GPC for interactions. A GPC signal does not submit a deletion request or erase your browser-saved profile. We do not claim that cookie-free basic page counting stops when such a signal is present.
10. Global laws & local differences
Relevant frameworks, where their territorial and other conditions are met, include EU GDPR (Regulation 2016/679), UK GDPR and the Data Protection Act 2018, the ePrivacy Directive and UK PECR for storage and electronic marketing, California’s CCPA as amended by CPRA and CalOPPA, other U.S. state privacy laws, and Florida’s Information Protection Act. The Florida Digital Bill of Rights has specific coverage thresholds; being based in Florida does not by itself establish that the practice is a covered controller.
Outside those jurisdictions, Canada’s PIPEDA and applicable provincial laws (including Quebec’s private-sector law as modernized by Law 25), Brazil’s LGPD, South Africa’s POPIA, Australia’s Privacy Act 1988, New Zealand’s Privacy Act 2020, Singapore’s PDPA, Japan’s APPI, and China’s PIPL may impose additional duties where applicable. These laws differ in scope, legal bases, sensitive-data treatment, transfer rules, rights, and exemptions. This illustrative list does not replace an applicability assessment or waive a local mandatory protection.
Business email addresses and professional details can still be personal information. Public-source information is not automatically exempt. We do not intentionally solicit information from children under 18. A parent or guardian who believes a child supplied information should contact us; COPPA and other child-privacy requirements must be assessed where applicable. Do not submit sensitive information about children or third parties through these forms.
- UK Data Protection Act 2018 ↗
- EU ePrivacy Directive ↗
- Florida Digital Bill of Rights — definitions ↗
- Canada — PIPEDA ↗
- Quebec — Commission d’accès à l’information ↗
- Brazil — LGPD ↗
- South Africa — Information Regulator ↗
- Australia — Privacy Act ↗
- New Zealand — Privacy Act 2020 ↗
- Singapore — PDPA ↗
- Japan — Personal Information Protection Commission ↗
- China — Personal Information Protection Law ↗
- FTC — Children’s Online Privacy Protection Rule ↗
11. Recent rulings, trends & policy changes
Schrems v. Meta (C-446/21, October 4, 2024) reinforces that personal-data aggregation must respect minimization, and public disclosure of sensitive information is not general permission for unrelated processing. KNLTB (C-621/22, October 4, 2024) confirms that a commercial interest may be legitimate, but necessity and balancing remain essential; legitimate interest is not automatic permission for marketing.
The EDPB’s October 2024 work on legitimate interests and processor oversight highlights the need to understand provider chains and justify processing. U.S. state privacy laws continued expanding through 2025–2026, including laws taking effect in Indiana, Kentucky, and Rhode Island in January 2026; sensitive health information, biometrics, and AI-related processing receive growing attention. These developments support purpose limits, minimization, and a jurisdiction-specific review rather than a blanket worldwide assurance.
We may revise this policy when collection, providers, purposes, or applicable requirements change. The displayed date identifies the version. Material changes require appropriate notice and, where required, a new choice before new processing. Browsing this page does not provide blanket consent to future uses.
