AscendLab

Updated: May 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, preview pages, account-based workflows, APIs, and related services.

Information We Collect

  • Account details such as name and email for admin or account-based workflow access.
  • Public browser tool inputs, which are processed locally in your browser unless a specific tool page clearly states otherwise.
  • Uploaded media (images, videos, and documents) submitted intentionally for account-based workflows after access and scope are confirmed. These workflows are separate from public browser tools.
  • API or workflow usage metadata including endpoints called, timestamps, and volume if account-based processing is enabled.
  • Payment and invoicing identifiers may be processed through payment partners only if future paid workflows are enabled; AscendLab does not store full card data.
  • Device, analytics, and log data such as browser type, approximate location, IP, page visits, referrers, and error logs to maintain service reliability, security, and product quality.

How We Use Data

  • To provide requested workflow results, API responses, and customer support.
  • To generate invoices, track usage against confirmed limits, and enforce rate limits if paid or account-based workflows are enabled.
  • To troubleshoot workflow 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 aggregate site usage through analytics tools such as Google Analytics and Ahrefs Analytics.

Product Analytics Events

AscendLab may collect first-party, privacy-conscious product events to understand tool discovery, search usage, saved tools, related-link navigation, workflow discovery, errors, and aggregate usage patterns. Product events are sanitized before storage and are designed to avoid storing public tool inputs.

  • Public tool inputs, uploaded file contents, clipboard contents, and generated outputs are not stored in product analytics.
  • Search metadata uses query length, token count, result count, and no-result flags by default instead of raw query text.
  • Internal QA and release validation events may be stored separately from real user traffic so admin dashboards can distinguish testing from usage.
  • You can limit analytics with browser privacy controls where applicable.

Advertising and Cookies

AscendLab may use Google AdSense or other advertising partners to show ads on public content pages if advertising 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.

  • Ads may be personalized or non-personalized depending on your region, consent choices, browser settings, and Google controls.
  • You can manage ad personalization through Google ad settings, browser privacy controls, and consent tools when available.
  • 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.
  • 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. These providers are bound by confidentiality and data-protection terms. We do not sell personal data.

Retention & Security

  • Inputs for public browser-side tools are not retained by AscendLab servers.
  • Media uploads for account-based AI workflows are retained only as long as needed to provide the workflow result, support the account, or meet legal and accounting obligations.
  • API logs and future payment records are kept only as needed for operations, audit, and financial compliance purposes.
  • Access to production systems is restricted and monitored; data is encrypted in transit and at rest.

AI Training

Uploaded customer content for account-based workflows is not used to train public AI models unless you explicitly agree in writing. Public browser tool inputs are not uploaded to AscendLab for model training.

Your Choices

  • You may request access, correction, or deletion of your personal data, subject to legal limits.
  • You can limit analytics through browser settings, consent tools when available, or by using browser privacy controls.
  • For account or API data portability, contact us and we will prepare an export aligned with our security policies.

International Transfers

Data may be processed in the countries where we or our providers operate. We use contractual safeguards when data crosses borders.

Contact

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