legal bench

Cookie Policy

Effective date: September 30, 2026

Last updated: September 30, 2026

This Cookie Policy explains how BarnTrucking LLC, doing business as Alpeya (“Alpeya”, “we”, “us”, or “our”) uses cookies and similar browser technologies on our websites and web applications.

Our current website is: https://alpeya.com

Privacy contact: [email protected]

This Cookie Policy should be read together with our Privacy Policy and Terms of Service.

Cookie settings

Analytics
Privacy-friendly, cookieless page-view and tool-usage counts. Off until you accept.

1. What Are Cookies?

Cookies are small pieces of information that a website may store in your browser.

Websites can also use technologies that perform similar functions, including:

  • localStorage
  • sessionStorage
  • IndexedDB
  • the browser Cache API
  • pixels and web beacons
  • scripts that access information stored in a browser
  • similar technologies used by advertising or analytics services

For purposes of this Cookie Policy, we refer to cookies and similar technologies collectively as “cookies and similar technologies” where appropriate.

Some cookies are necessary for a website to function. Others are used for analytics, advertising, personalization, or other purposes.

2. Our Privacy-First Approach

Alpeya is designed to minimize the use of tracking technologies.

  • our media-processing tools process supported files locally in your browser;
  • we do not need a cookie to process your image, audio, video, or document;
  • our self-hosted Umami analytics installation is cookieless;
  • Umami is not loaded for analytics until the user gives the applicable analytics consent through our consent banner;
  • our first-party language preference is stored separately from analytics and advertising;
  • Google AdSense may use advertising cookies and similar technologies when advertising is enabled and applicable consent/settings permit it.

Because Alpeya deliberately gates Umami behind the consent mechanism, declining analytics consent prevents our Umami analytics script from being activated for that visitor.

3. Categories of Cookies and Similar Technologies

We classify the technologies used by Alpeya into the following categories:

Category Purpose Consent
Strictly necessary / essential Security, administration, and basic site functionality Generally not optional where strictly necessary
Functional Remembering preferences such as language and consent choices May be used where necessary for the requested functionality; otherwise controlled by consent
Analytics Understanding aggregate website and tool usage through Umami Consent required by our implementation
Advertising Google AdSense and related advertising technologies Consent where required by applicable law and Google policy

The exact technologies active on a particular page can depend on the features used, your location, your consent choices, and the services currently enabled on the website.

4. First-Party Technologies Used by Alpeya

4.1 Language preference

When you select a language, Alpeya stores your selected language in a first-party cookie.

Purpose

The cookie allows the website to remember your language preference when you return.

Type

Functional / preference.

Typical retention

Up to 1 year.

Information stored

A language/locale value, rather than the contents of your media or a user profile.

The cookie is configured by our application as:

  • HttpOnly
  • Secure when operating over HTTPS
  • SameSite=Lax

This cookie is not used for advertising or behavioral analytics.

4.2 Consent preference storage

Our consent interface stores your cookie/consent choices in browser-local storage.

The current implementation uses values including:

  • cookie_consent
  • cookie_preferences

These values are used to remember whether and how you have responded to the consent interface.

Purpose

  • remember your privacy choices;
  • prevent the consent interface from repeatedly asking the same question;
  • determine which optional services may be activated.

Storage mechanism

Browser localStorage.

Type

Consent-management / preference storage.

Does it track you?

No.

This storage is used to remember your privacy decision. It is not used to create an advertising profile or to measure your behavior.

In addition to the localStorage values above, the consent interface sets a first-party analytics_consent cookie (accepted or declined, 1 year) that mirrors your choice. Your browser sends this cookie to our servers with each request so the server can enforce your decision - visit recording and the analytics script stay off until the cookie says accepted. See the inventory in Section 19.

If you clear your browser’s local storage, change browsers, or use a private browsing session, the consent interface may ask for your preferences again.

4.3 Administrative session

Alpeya has protected administrative functionality that is not available to ordinary visitors.

An administrative session cookie may be used when an authorized administrator accesses the administrative interface.

Purpose

  • authentication;
  • maintaining an administrative session;
  • security.

Type

Strictly necessary for the administrative interface.

Advertising / analytics

This cookie is not used for advertising or general visitor analytics.

5. Umami Analytics

5.1 What Umami does

Alpeya uses a self-hosted Umami Analytics installation to understand aggregate use of the website and improve our tools and content.

Our Umami instance is hosted in the United States and is operated for Alpeya.

Umami is designed to operate without analytics cookies. Examples of information that analytics may provide include:

  • pages visited;
  • tool usage;
  • referring pages;
  • campaign/referral information;
  • browser and operating-system information;
  • device type;
  • approximate geographic information such as country;
  • timestamps;
  • aggregate events and interactions configured by Alpeya.

The precise information available depends on our Umami configuration.

5.2 Umami is consent-gated on Alpeya

Although Umami itself does not require an analytics cookie, Alpeya intentionally treats Umami analytics as an optional analytics technology.

The Umami script is loaded/activated only after the visitor gives the applicable analytics consent through our consent banner.

If you accept analytics

The Alpeya website may activate the self-hosted Umami analytics script and send analytics events to our Umami server.

If you reject analytics

Alpeya does not intentionally activate our Umami analytics script for your session.

If you do not make a choice

Optional analytics should remain disabled according to our consent implementation.

This means that our Umami analytics does not depend on an assumption that “cookieless means no consent is needed.” We have chosen to gate analytics behind the consent mechanism as an additional privacy measure.

5.3 Umami cookies

Our self-hosted Umami implementation is configured as cookieless.

Accordingly, we do not expect our Umami analytics installation to set a conventional analytics cookie.

The consent mechanism itself may store your consent decision locally in your browser, as described above.

6. Google AdSense and Advertising Technologies

Alpeya plans to use Google AdSense to support the Service through advertising. No advertising cookies are set today.

Google AdSense may use:

  • cookies;
  • local storage or similar browser technologies;
  • web beacons/pixels;
  • IP addresses;
  • advertising identifiers;
  • other technologies used for advertising, measurement, fraud prevention, and related purposes.

Advertising technologies can be used for purposes such as:

  • serving advertisements;
  • measuring advertising performance;
  • limiting repeated advertisements;
  • detecting invalid traffic and fraud;
  • personalized advertising where permitted;
  • non-personalized or limited advertising where applicable.

The exact cookies and technologies used by Google can vary depending on:

  • your location;
  • the type of advertising being served;
  • your consent choices;
  • Google’s advertising configuration;
  • Google’s advertising partners;
  • browser and platform behavior.

For that reason, we do not attempt to provide a permanently exhaustive list of every Google advertising cookie name in this policy.

7. Consent for Google Advertising

Where applicable law requires consent for advertising cookies, local storage, or related processing, Alpeya will seek the required consent before enabling the relevant advertising functionality.

For users in the European Economic Area (EEA), United Kingdom, and Switzerland, Google currently requires publishers serving personalized advertising to use a Google-certified Consent Management Platform (CMP) integrated with the IAB Transparency and Consent Framework (TCF).

Google also requires publishers to disclose relevant advertising technology providers and obtain consent where legally required for cookies/local storage and the collection, sharing, and use of personal data for personalized advertising.

Therefore, the production consent implementation used with AdSense must be kept aligned with Google’s then-current publisher requirements.

Important implementation requirement

A custom Alpeya consent banner should not be treated as automatically satisfying Google’s EEA/UK/Swiss personalized-advertising requirements merely because it displays “Accept” and “Reject” buttons.

If Alpeya serves personalized AdSense advertising to users in the EEA, UK, or Switzerland, the production CMP configuration must meet the applicable Google certification/TCF requirements.

Google maintains the current list of certified CMPs and updates it over time.

8. Analytics Consent and Advertising Consent Are Separate

Alpeya treats analytics and advertising as separate purposes.

For example, a visitor may:

  • accept analytics but reject advertising;
  • reject analytics but accept advertising where the applicable consent framework permits it;
  • reject both;
  • make another choice through the available consent controls.

Our consent implementation should therefore avoid treating a general “I accept cookies” state as permission for every optional processing purpose unless the applicable consent mechanism actually communicates the required purposes and choices.

Where Google AdSense or another advertising technology requires its own consent signal or standardized consent framework, the advertising implementation must honor that signal.

9. Browser-Local Storage Used by Alpeya Tools

Some Alpeya tools use browser storage for functionality rather than tracking.

These technologies may include:

  • localStorage
  • IndexedDB
  • the Cache API

Theme preference

The website may store your selected light/dark theme locally in your browser.

Typical key: alpeya-theme

Purpose: remember visual preferences.

This information is not sent to Alpeya merely because it exists in local storage.

Processing-engine version information

Some tools may store locally cached version information for browser-side processing engines (for example WebAssembly engine or FFmpeg versions) to determine whether a local processing resource needs to be updated, improve performance, and avoid repeatedly downloading the same resources.

Cached processing resources

Alpeya may use the browser Cache API to cache WebAssembly and other resources required for local processing (for example a processing engine), so the browser does not need to download the same resource repeatedly. These cached resources are not advertising cookies.

IndexedDB processing models

Some tools may store machine-learning models in IndexedDB for browser-side processing (for example a vocal-removal tool may cache its model locally). The model is used by the browser to perform processing locally. This browser storage is not used by Alpeya as an analytics profile.

10. Third-Party Resources

Some Alpeya tools request libraries, models, fonts, or other resources directly from third-party infrastructure.

Depending on the tool, requests may be made to domains including:

  • cdn.jsdelivr.net
  • storage.googleapis.com
  • huggingface.co
  • cdn-lfs.hf.co
  • other Hugging Face CDN domains
  • tesseract.projectnaptha.com
  • fonts.googleapis.com
  • fonts.gstatic.com

These requests are not necessarily cookies set by Alpeya.

However, when your browser connects to a third-party server, that third party may receive ordinary network information associated with the request, such as:

  • IP address;
  • user-agent;
  • requested resource;
  • referring page where provided;
  • request time.

The third party’s own privacy policy controls its processing.

11. Cloudflare

Alpeya uses Cloudflare for infrastructure and security functions including:

  • DNS;
  • CDN;
  • TLS/HTTPS;
  • DDoS protection;
  • traffic filtering;
  • security;
  • performance and reliability.

Cloudflare may process network information when your browser communicates with our website through its infrastructure.

Cloudflare’s processing is separate from Alpeya’s optional analytics consent.

A Cloudflare security or infrastructure function may continue to operate even if you reject optional analytics or advertising, because disabling essential security infrastructure would prevent us from providing the website safely. For more information, see Cloudflare’s privacy documentation.

12. Strictly Necessary Technologies

Strictly necessary technologies are those required to provide a service that you have requested or to operate, secure, and maintain the website.

Examples in Alpeya’s architecture include:

  • administrative authentication sessions;
  • security mechanisms;
  • language preference functionality where necessary to provide the requested language experience;
  • consent-preference storage used to remember your privacy choices;
  • technical browser storage required for a requested tool function.

Where a technology is genuinely strictly necessary under applicable law, consent may not be required.

We do not classify advertising technologies as strictly necessary.

13. Optional Technologies and Consent

For technologies that are not strictly necessary, Alpeya’s consent mechanism is designed to provide users with meaningful choices.

In jurisdictions where consent is required, optional technologies should not be activated before the relevant consent is obtained.

In particular:

  • analytics should remain disabled until the applicable analytics choice is made;
  • advertising technologies requiring consent should remain disabled until the applicable advertising choice is made;
  • declining optional technologies should not prevent access to the core Service solely because the user declined those technologies.

European ePrivacy rules require consent for storing or accessing information on a user’s terminal equipment where the relevant exception does not apply, and EU case law requires consent to be a genuine affirmative choice rather than something inferred from a pre-selected option. UK PECR similarly regulates cookies and similar technologies, with an exception for technologies that are strictly necessary: non-essential advertising cookies require a clear positive consent action and cannot rely on continued website use.

14. Withdrawing or Changing Your Choices

You can change your optional cookie and analytics choices through the consent controls provided by Alpeya (for example the analytics toggle at the top of this page or the cookie banner).

You can also clear cookies and browser storage through your browser settings.

Clearing browser storage may cause:

  • the consent banner to appear again;
  • your language preference to be reset;
  • local application preferences to be reset;
  • locally cached processing resources to be removed.

Browser-level deletion does not necessarily remove information that has already been processed by a third party before your choice was changed.

15. Effect of Rejecting Optional Technologies

If you reject optional analytics:

  • Alpeya’s Umami analytics should not be activated for your session;
  • core media-processing functionality remains available;
  • essential website functionality remains available.

If you reject optional advertising technologies:

  • personalized advertising may not be available where consent is required;
  • Google or other advertising systems may instead provide non-personalized, limited, or no advertising depending on the applicable configuration and legal requirements;
  • core website functionality should remain available.

16. International Users

Alpeya is operated by BarnTrucking LLC, a Pennsylvania, United States company, and serves users worldwide.

Cookie and similar-technology rules differ by jurisdiction.

For example:

  • the EU/EEA has ePrivacy and GDPR requirements;
  • the UK has PECR and UK GDPR requirements;
  • Switzerland has its own privacy and electronic-communications requirements;
  • U.S. states may provide privacy and opt-out rights that apply depending on the circumstances.

Accordingly, the consent experience and technologies enabled may vary based on your location and the applicable legal requirements.

17. California and U.S. Privacy Choices

Where applicable U.S. privacy law gives a visitor a right to opt out of the sale or sharing of personal information, targeted advertising, or similar processing, Alpeya will provide the legally required mechanism.

California privacy law can treat certain advertising-related disclosures differently from a conventional sale of data for money.

Where applicable, Alpeya may therefore provide controls for:

  • opting out of targeted advertising;
  • opting out of sale or sharing where legally applicable.

Alpeya recognizes the Global Privacy Control (GPC) opt-out signal: when your browser sends Sec-GPC: 1 (or navigator.globalPrivacyControl is set) and you have not made an explicit choice on this site, optional Umami analytics stay off and the analytics script is not loaded. Your explicit accept or decline choice in our banner or toggle takes precedence over the GPC default. When advertising is enabled, a GPC signal will likewise be treated as a request for non-personalized advertising where the advertising platform supports it.

You can verify this yourself: with GPC enabled and no explicit accept, no visit record is stored and no request is sent to our analytics endpoint.

18. Children’s Privacy

Alpeya’s Service is not directed to children below the age at which parental consent is required under applicable law.

We do not knowingly use advertising cookies or optional analytics to circumvent children’s privacy protections.

Where applicable law imposes additional restrictions concerning children, those restrictions take precedence over the general descriptions in this Cookie Policy.

19. Cookie and Technology Inventory

The following is our current high-level inventory.

Technology Provider Category Purpose Storage Typical duration / retention Consent
lang Alpeya Functional Remember selected language Cookie Up to 1 year Depends on applicable law; used for requested preference
cookie_consent Alpeya Consent management Remember consent state localStorage Until cleared/updated by the user or implementation Necessary to remember the choice
cookie_preferences Alpeya Consent management Remember category choices localStorage Until cleared/updated by the user or implementation Necessary to remember the choice
analytics_consent Alpeya Consent management Mirror of your analytics choice (accepted or declined) so the server can enforce it; visits are recorded only when it says accepted. With no explicit choice, analytics stay off (including under a GPC signal) Cookie (sent to our servers with each request) Up to 1 year Necessary to remember and enforce the choice
alpeya-theme Alpeya Functional Remember theme localStorage Until cleared/updated Depends on applicable law
WASM/FFmpeg version values Alpeya Functional / technical Manage local processing resources localStorage Until cleared/updated Technical
wasm-engine caches and similar caches Alpeya Functional / technical Cache local processing resources Cache API Browser-controlled Technical
Demucs / processing model data Alpeya Functional / technical Local browser processing IndexedDB Browser-controlled Technical
Admin session Alpeya Strictly necessary Administrative authentication Cookie Session/configuration dependent Not optional for admin
Umami analytics Alpeya Analytics Aggregate usage measurement No analytics cookie Server retention according to Umami configuration Only activated after analytics consent
Google AdSense technologies Google Advertising Advertising, measurement, fraud prevention, personalization where applicable Cookies and/or similar technologies Varies Consent where legally required
Third-party libraries/models Various Technical Deliver client-side processing resources Browser cache and network Varies Technical
Google Fonts resources Google Technical / content delivery Deliver fonts Browser cache and network Varies Depends on applicable implementation/law

This inventory is intentionally written at the category level for third-party advertising and resource-delivery systems because third-party cookie names, lifetimes, and vendors can change without requiring an update to Alpeya’s application code.

20. Third-Party Privacy Policies

Third-party services used by the website have their own privacy policies and may update their cookies or similar technologies.

Relevant providers include:

  • Google / Google AdSense;
  • Cloudflare;
  • Umami (our self-hosted analytics software);
  • jsDelivr;
  • Google Cloud / Google Fonts;
  • Hugging Face;
  • Tesseract OCR infrastructure.

Users should review the applicable third party’s current privacy documentation for information about its independent processing.

21. Changes to This Cookie Policy

We may update this Cookie Policy when:

  • we add or remove cookies;
  • we introduce new analytics or advertising providers;
  • the website architecture changes;
  • we change our consent mechanism;
  • applicable law changes;
  • third-party services change their technologies;

When we make material changes, we will update the Last updated date at the top of this document and provide additional notice where required by law.

22. Contact

If you have questions about this Cookie Policy or our use of cookies and similar technologies, contact:

BarnTrucking LLC d/b/a Alpeya
7901 Dungan RD, Philadelphia, PA 19111, United States
Privacy contact: [email protected]

23. Short Summary

Alpeya’s cookie approach can be summarized as follows:

  • Media processing does not require cookies.
  • Your media files are processed locally in your browser.
  • Alpeya’s Umami analytics is self-hosted in the United States.
  • Umami itself is cookieless.
  • Alpeya nevertheless gates Umami behind the analytics choice in the consent banner.
  • Rejecting analytics prevents our Umami script from being activated under the intended implementation.
  • The consent banner stores your consent choice locally in the browser.
  • The language preference is stored in a first-party cookie for up to one year.
  • Administrative sessions use a separate authentication cookie.
  • Some tools use localStorage, IndexedDB, and Cache API for browser-side functionality and cached processing resources.
  • Cloudflare may process ordinary network/security information as part of providing the website.
  • Google AdSense may use advertising cookies and similar technologies.
  • Advertising consent is separate from Alpeya’s optional analytics consent.
  • Where required, advertising and analytics are not activated before the applicable consent is obtained.
  • Users can change their optional privacy choices through the site’s consent controls.