AscendLab

Updated: October 10, 2026

Privacy Policy

This policy explains how Ascend Lab LLC ("AscendLab", "we", "us") collects, uses, and protects information when you use our public browser tools, contact channels, and related site services.

Information We Collect

  • Contact details such as name and email when you intentionally submit a support, correction, or security request.
  • Public browser tool inputs, which are processed locally in your browser unless a specific tool page clearly states otherwise.
  • After you allow analytics: page visits, tool actions, performance measurements, error categories, coarse browser and device information, country-level location, and random browser and session identifiers. These first-party events do not include tool input or generated output.
  • Cloudflare browser performance measurement may run before you choose, within the existing regional exclusions described below. You can opt out of it with Reject analytics in Privacy settings.
  • Ordinary page delivery and security processing can involve IP addresses, request information, and technical logs at our hosting and CDN providers. These operations are separate from optional product analytics.

How We Use Data

  • To provide customer support, investigate bugs, and process content corrections or security reports.
  • To troubleshoot tool quality and reliability when needed, with access restricted to authorized operational purposes.
  • To detect abuse, maintain security, and comply with legal or regulatory obligations.
  • To understand visits, tool usage, and performance through first-party product events after you allow analytics. Google Analytics is also subject to this choice if enabled; it is currently disabled.
  • To measure browser loading performance through Cloudflare under the regional settings and opt-out described below.

Product Analytics Events

With your permission, AscendLab sends first-party product events to its own analytics endpoint to understand tool discovery, search usage, saved tools, related-link navigation, workflow discovery, errors, and performance. We store individual sanitized events and use them to produce aggregate usage reports. Random identifiers can link events from the same browser or session; these records are pseudonymous, not fully anonymous.

  • Public tool inputs, uploaded file contents, clipboard contents, and generated outputs are not stored in product analytics.
  • Page paths exclude URL query strings and fragments. Search metadata uses query length, token count, result count, and no-result flags instead of raw query text. Referrers are reduced to categories such as direct, search, social, or internal.
  • Events can include tool and action names, timestamps, browser and operating-system families, device class, viewport dimensions, network hints, country-level location, processing duration, file format or size metadata, performance measurements, error codes, and software release identifiers.
  • Random visitor and session IDs are generated by this browser. They are not derived from IP addresses, tool input, or browser fingerprinting. Your analytics choice, its version, and its recorded time accompany first-party events sent after acceptance.
  • Internal QA and release validation events may be stored separately from real user traffic so admin dashboards can distinguish testing from usage.
  • First-party usage and performance events start only after you allow analytics in Privacy settings. This setting also controls Google Analytics if enabled. Reject analytics opts out of both these integrations and Cloudflare browser performance measurement; see the reload boundary below.
  • If this browser cannot save your choice, first-party analytics and Google Analytics stay off.
  • A refusal saved under the previous version of our notice remains effective. A previous acceptance requires a new choice before first-party analytics starts.

Cloudflare Performance Measurement

Cloudflare browser performance measurement may run by default within our existing regional exclusions, before you make an analytics choice. Cloudflare says its probe reads performance information without reading or writing cookies or other browser storage. This does not mean no data is sent: page URLs, referrer information, and technical performance measurements can be sent to Cloudflare.

We retain Cloudflare's existing exclusion for requests connecting to its data centers in the EEA/EU, the United Kingdom, and Switzerland. This is based on the connected data center, which may be in a different region from the visitor. Allowing first-party analytics does not expand this Cloudflare collection scope.

Reject analytics opts out of Cloudflare measurement as well as first-party analytics. Rejecting or withdrawing reloads the page to stop an already initialized probe and apply the opt-out to the new page. If the choice cannot be saved, the page stops further analytics sending and explains any temporary pause of other network requests until storage is restored. Requests already sent or in flight cannot be recalled; browser settings do not erase records already received. Necessary CDN delivery and security processing are separate.

Cloudflare documents seven days of unsampled beacon data, followed by aggregation and sampling for longer-term storage. Its six-month reporting window is not a deletion guarantee. See Cloudflare's RUM data and regional settings and retention and beacon behavior.

Advertising and Cookies

AscendLab may use Adsterra or Google AdSense to show ads on public content pages if the respective integration is enabled. Advertising partners may use cookies, web beacons, IP addresses, device identifiers, browser information, and similar technologies to deliver, measure, limit, and secure ads.

The Adsterra native-banner integration is enabled by default on reviewed English and Chinese home pages and selected English workflow, article and reference pages. Tool input pages, account, billing, login and policy pages do not load its scripts. System enablement is separate from consent. We use a country code supplied by a verified Cloudflare connection to choose the loading policy, without storing the country or inferring it from browser language. Ads may load by default for verified United States traffic; all other or unknown regions, including the EEA, United Kingdom and Switzerland, require your acceptance before vendor requests. This conservative regional allowlist is not a determination that every other country legally requires consent. IP geolocation can be inaccurate, especially with VPNs, and is not proof of residence. The provider has no verified cookieless tag. Default loading does not create an acceptance record. The provider receives your IP, page address and browser information and may use cookies or similar technologies to deliver and measure ads. Accepting analytics does not authorize advertising. A saved refusal, unavailable preference storage, Global Privacy Control or a Do Not Track signal keeps ads off. We store your choice, notice version and date in local storage. Refusals remain effective until changed or site storage is cleared; an acceptance expires after 180 days and then requires a new choice. Previous enable records require acceptance of this notice; previous refusals remain effective. Choose “Reject advertising” in Privacy settings, or “Do not sell or share my personal information” beside a default-loaded ad, to persistently opt out. “Close for this visit” beside an ad hides advertising for the current tab using session storage, including across reloads and page navigation. A fresh tab without an inherited or restored browser session starts with the regional loading policy again; saved refusals and browser privacy signals still apply. Closing for a visit does not change your persistent advertising choice. If session storage cannot preserve the closure, an already active ad page navigates to this ad-free privacy page. An open ad document reloads to stop ongoing vendor execution; it cannot recall requests already sent, delete third-party cookies or erase provider records. Optional first-party ad-slot visibility and script-status measurements require your separate analytics consent and do not establish billed impressions or revenue. See the Adsterra Privacy Policy for provider practices and rights requests.

  • Ads may be personalized or non-personalized depending on your region, consent choices, browser settings, and Google controls.
  • Google and other third-party vendors may use advertising cookies based on your prior visits to this site or other sites. You can manage personalized advertising in the Google Ads Settings.
  • Learn more about how Google processes information from partner sites in How Google uses information from sites or apps that use its services.
  • Our application keeps Google AdSense disabled pending a verified advertising-consent integration. A publisher ID or ads.txt entry is not proof of active advertising or Google approval. Accepting analytics in Privacy settings does not authorize advertising, and a legacy browser preference is not treated as certified advertising consent.
  • Before enabling personalized Google ads for visitors in the European Economic Area, the United Kingdom, or Switzerland, we require a Google-certified consent management platform integrated with the IAB Transparency and Consent Framework. We must obtain consent for cookies or other storage where legally required, and for the collection and use of personal data for ad personalization. Non-personalized advertising is not a blanket exemption from storage-consent requirements.
  • Advertising disclosures must identify the applicable vendors and purposes and provide a way to revisit choices. Privacy settings provides separate analytics and native-advertising choices; it is not a Google-certified advertising CMP. Google Ads Settings manages Google personalization preferences; it does not replace a site-level withdrawal control.
  • We do not use public tool inputs to create advertising audiences, and do not intentionally send email addresses, phone numbers, or account identifiers in advertising requests. Advertising must remain separate from account, billing, private input, error, and processing-only screens.
  • AscendLab does not sell public tool inputs, uploaded file contents, clipboard contents, or generated outputs.
  • Public browser-side tool inputs are not sent to AscendLab servers for advertising profiling.
  • Third-party advertising partners may process limited technical data to deliver, measure, prevent abuse, and secure ads.
  • AscendLab public tools do not request or collect precise device geolocation. Approximate location may be inferred by service providers from network information such as an IP address.
  • You may request access, deletion, correction, or opt-out where applicable under regional privacy laws, subject to legal and operational limits.

Sharing & Processors

We share data only with service providers needed to operate AscendLab, such as cloud hosting, analytics, email, payment processors, and security tooling. We do not sell personal data. Contact us for information about the providers and safeguards relevant to your request.

Retention & Security

  • Inputs for public browser-side tools are not retained by AscendLab servers.
  • A browser visitor ID is reused for up to 180 days from its creation; a session ID is reused until 30 minutes of inactivity. Expired IDs are replaced when another analytics event is generated. Browser storage does not automatically disappear at those deadlines; you can clear it or withdraw analytics to remove our stored analytics IDs.
  • Your analytics preference, version, and choice date stay in this browser until you change them or clear site storage; the preference has no automatic expiry.
  • Server-side product events, tool-job summaries, error records, performance samples, and product feedback have a maintenance deletion task with a default cutoff of 180 days. The cutoff is configurable and is not an enforced automatic deletion deadline; records can remain until maintenance runs. Exports, backups, provider records, and security logs are separate and are not covered by this cutoff.
  • Support and correction messages are retained only as long as needed for follow-up, security, or legal obligations.
  • Public pages use HTTPS, and production access is restricted. Browser controls do not erase provider records, exports, or backups. Contact us about the records relevant to a deletion request.

AI Training

Public browser tool inputs are not uploaded to AscendLab for model training. Support messages are not used to train public AI models.

Your Choices

  • You may request access, correction, or deletion of your personal data, subject to legal limits.
  • Use Privacy settings at the bottom of any page to allow first-party analytics or choose Reject analytics to opt out of both first-party analytics and Cloudflare browser performance measurement. Google Analytics, if enabled, also requires acceptance. Rejecting or withdrawing clears our stored analytics identifiers and accessible Google Analytics cookies, and reloads the page to stop an initialized Cloudflare probe. It cannot recall requests already sent or in flight, or erase events already received. Tools remain available; necessary delivery and security logs are separate. This choice does not authorize advertising.
  • For support-record data access or portability, contact us and we will respond subject to identity and security checks.

International Transfers

Data may be processed in the countries where we or our providers operate. Contact us for information about the locations and safeguards applicable to a particular service or request.

Contact

Email: support [at] ascend-lab.com
Address: 30 N Gould St Ste R, Sheridan, WY 82801, USA