AurixBack to Aurix

Aurix Privacy Policy

Effective 20 October 2026. Updated for IGDB game lookups, channel memberships, Affiliate and Partner monetization, optional AI recommendations, watch history controls and automatic Adcash playback ads.

1. Who we are

Aurix is a video sharing platform operated in Canada by Reese Thompson (Myla). This policy covers aurix.tv, www.aurix.tv, dashboard.aurix.tv, and the account and media services that support them. In this policy, “Aurix,” “we,” and “us” mean that operator.

Our privacy contact is [email protected]. Use that address for privacy questions, requests or complaints. Please do not send your password, payment card details or identity documents in an ordinary email.

2. Information you provide

Do not put sensitive personal information or another person's private information into a public profile, video or comment unless you have an appropriate reason and permission to do so.

3. Information collected when you use Aurix

Our hosting and security services receive information needed to deliver requests, including IP addresses, browser and device information, requested addresses, timestamps, and diagnostic or security information.

When you play a video, Aurix records playback information such as the video, session time, approximate seconds watched, progress, completion and whether playback came from a watch page or playlist. Private watch history is on by default for new accounts and existing accounts that have not chosen a setting. An existing pause stays paused. You can pause saving, remove individual entries or clear your history in Settings. When saving is on, engaged signed-in playback can update private watch history. Creator analytics are separate from recommendation signals. Pausing or deleting watch history detaches its playback sessions from the account reference, while playback measurements and daily derived identifiers may remain for analytics. For visitors who are not signed in, Aurix derives a daily identifier from the IP address to estimate and deduplicate views. Our analytics records store that derived identifier rather than the raw IP address. Hashing does not make these records anonymous, and our infrastructure still receives the IP address to deliver the service.

Search queries are processed to return matching public videos, playlists and channels. Searching works without an account and with search history off. Search history is on by default for new accounts and existing accounts without a recorded choice; existing pauses stay paused. While saving is on, a visible search results page can save its query to your signed-in account. Typing in the search bar, changing result filters and loading more results for the same search do not create separate saved searches. A request to the public search API does not itself save account history. With saving off, the query is not added to account search history, but hosting and security services still process request information as described above.

Creators receive summary statistics for their own content, such as views, watch time, audience retention and subscriber changes. The creator analytics dashboard does not provide individual viewers' email addresses, IP addresses or private watch histories. Studio video previews are excluded from content playback analytics.

4. Why we use information

We use information to create and secure accounts, keep you signed in, deliver videos, publish your chosen content, support comments and playlists, remember account activity, send verification and password recovery emails, provide creator analytics, administer the creator programme, respond to requests, investigate abuse and technical problems, and meet legal obligations.

Optional search and watch history let you revisit recent activity. History saving is separate from accepting the Terms of Service and from enabling AI personalisation. Searches work and videos play with saving off.

AI personalisation is on by default for new accounts and existing accounts without a recorded choice. A previous choice to turn it off is preserved. You can turn it off or choose sources in Recommendations. Aurix uses recent saved searches while search saving is on, recent watched public videos and progress while watch saving is on, and liked public videos and dislikes. Existing saved signals can contribute unless you reset recommendations. Each source can be disabled. Private, unlisted, unready and restricted videos and restricted channels are excluded from recommendation candidates and video interest signals. We do not infer sensitive personal traits, combine your activity with other accounts or use other sites' browsing data for these recommendations.

Aurix compares AI embeddings of video topics and selected queries, then combines semantic similarity, engagement, public recency and popularity, with channel variety. It does not make legal or similarly significant decisions about you. Each suggestion has a short explanation. Results can be imperfect and may repeat or overlook videos, especially in a small catalogue. General mode uses public recency and popularity without account signals. Watch pages may use the current public video's topics without using history. Missing activity or an unavailable model produces a labelled general feed.

We request consent where it is required for a particular use. A privacy policy describes our practices; reading it or creating an account does not give blanket consent to unrelated uses of your information. If we propose a materially different use that requires your consent, we will explain it and seek that consent before starting it.

5. What other people can see

Your username, display name and chosen channel biography, profile photo, banner and links are public. Comments identify their author and are visible to people who can access the associated video. Creators can pin comments and remove comments on their own videos.

Public videos and public playlists are available to other people. Unlisted content is accessible to anyone who obtains its link, including someone a recipient shares it with. An unlisted link is not an access restriction. Private videos and private playlists require the owner's account to access them. Authorised operators and service providers may process stored content to operate and support Aurix.

Views, subscriber totals and like and dislike counts can appear with content. Your recovery email, password hash, private watch history, private search history and private account settings are not public profile fields. Your own account actions can still create public content or affect public totals.

Search history is available only to its account holder through the Aurix and Studio history interfaces. Creators and operators cannot use those interfaces to inspect another person's search history. Authorised operational access and legal disclosures are described in section 8.

People may copy, download, record or redistribute content they can access. Changing visibility or deleting content from Aurix cannot remove copies held independently by other people or sites.

6. Cookies and browser storage

Aurix uses a sign-in cookie named __Secure-aurix_session. It identifies an account session, expires after seven days, and is shared across trusted aurix.tv subdomains so the viewer site and Studio can recognise the same sign-in. It is sent over HTTPS and is not readable by ordinary page JavaScript. Signing out revokes that session and clears its cookie. Your account records and history are not deleted by signing out.

You can remove or block cookies in your browser. Blocking the sign-in cookie prevents account features and automatic sign-in between Aurix and Studio. It does not by itself stop server request logs or the playback measurements described above.

If you used an earlier version of Aurix, a legacy sign-in value in browser session storage is removed when the current account system attempts to migrate it. Infrastructure providers may also use storage or cookies for security and service delivery, as described in their notices.

Earlier versions stored an aurix_video_ads preference cookie for up to 180 days. The current player does not read or write that cookie. Existing copies can be removed in your browser settings and otherwise expire on their original schedule.

7. Advertising and your choices

Aurix automatically requests in-stream video ads from Adcash through Google's IMA video ad player on eligible watch pages. There is no separate Aurix allow or decline prompt before playback. Ads and content attempt autoplay with sound first. If the browser blocks sound autoplay, the player tries muted autoplay and offers Tap to unmute. If autoplay is blocked entirely, a play button starts playback after a tap. You can use its mute and volume controls. This playback behaviour does not change your account's separate history or AI recommendation settings.

Adcash, the Google player SDK and vendors involved in delivery and measurement may receive IP addresses, device and browser information, public page or video references, advertising identifiers and ad interactions through cookies, local storage, tags or similar technologies. These providers may process information outside Canada. Aurix does not add account emails, account identifiers, private search history or private watch history to the ad tag, and does not manufacture a consent signal from opening a video. Browser privacy controls and provider controls can affect ad delivery. Read their notices for their processing, retention and deletion controls.

The shared Adcash platform tag may be used on eligible public and unlisted videos, including videos on channels enrolled in revenue sharing. Shared-zone ads are not yet attributable to individual creators and do not create verified creator earnings. Separately reportable creator zones and verified net reports are needed for attributable earnings. Private previews and restricted videos do not request ads. An ad request may return no ad, and an unavailable ad service falls back to the video. Skip timing and availability are determined by the ad provider. Watching an ad does not itself create a verified creator balance. Google display and future feed advertising remain separate plans.

Read Adcash's legal and privacy information, How Google uses information from sites or apps that use its services and Google's Privacy Policy. You can also manage Google personalised advertising through Google Ads Settings. Those settings do not stop every form of service measurement.

8. Providers and other disclosures

People authorised to operate or support Aurix may access information for the purposes in this policy. We may also disclose information where required by law, to respond to valid legal process, or where permitted by law to protect people, the service or legal rights. Any proposed business transfer involving personal information must be handled with the notices, safeguards and choices required by applicable law.

Content reports and their reporter identities are available only to authorised operators. Affected account holders receive the relevant rule and a decision explanation, and can submit an appeal. Their notice and appeal interfaces do not include the reporter's identity or private report text. Reporters can see whether their own report is open or resolved, not another person's private account or investigation records. Legal disclosure obligations may still apply. Reports and reporter identities are not sent to the automated models. Aurix combines automated screening of content with human review, as described above.

Links in channels, comments or videos can take you to independent sites. Those sites operate under their own privacy practices.

9. Processing outside Canada

Aurix is operated in Canada, but the providers we use operate internationally. Your information may be stored or processed outside your province or Canada and may be subject to the laws and lawful access requirements of those locations. We remain responsible for personal information under our control and use appropriate contractual and other safeguards for our providers. This policy does not promise that all information stays in Canada.

10. Retention and security

We retain account, published content and interaction records while they support an active account or remain needed for the purposes described here. Except for search and watch history and the expiring records described below, these records do not currently have a fixed automatic expiry. We review requests to delete them and retain information only where a continuing operational, security, dispute, accounting or legal purpose requires it. Engaged playback records and view identifiers are retained for analytics and do not currently have a fixed automatic expiry. Creator programme and verified revenue records may need to be retained separately from public content for accounting and disputes. We do not promise that closing an account removes records we are legally required to retain.

Saved search queries expire 90 days after the query was last searched for, with a maximum of 500 distinct recent queries per account. Repeating a query updates its recency rather than creating another entry. Expired queries are excluded from your history immediately; scheduled cleanup physically removes them in bounded batches. Deleting a search or clearing history removes it from the live history store. Limited infrastructure backups or security records may remain under provider retention and the purposes described in this policy. Preference and consent records remain with the account to honour your choice and document it.

Saved watch history expires 90 days after the video was last watched, with a maximum of 500 recent videos per account. Expired entries stop appearing and contributing immediately, with bounded scheduled physical cleanup. Individual removal and Clear all remove the corresponding live history records and invalidate earlier playback sessions so a delayed event cannot recreate them. Analytics totals are retained separately, with the account reference detached when pausing or deleting history. Recommendation source choices and consent records remain to honour your preferences; there is no persistent personal recommendation vector to retain. Daily recommendation service counters expire after 32 days.

Sign-in sessions expire after seven days. Password recovery links expire after 30 minutes and verification links after 24 hours. For processed videos, Aurix retains the original source for 30 days after encoding succeeds. A terminal processing failure retains its source for seven days after that failure, so the owner can retry. A source whose retention period has ended must be uploaded again to restart processing. Successful playback renditions and subtitle tracks remain until the video or track is deleted. Removing source subtitles also removes translations and stops automatic regeneration until the creator requests it again. Saving source corrections removes cached translations so later requests use the corrected text. Video deletion removes Aurix subtitle records immediately. Caption processing does not store separate audio files. Aurix retains aggregate daily processing counters for up to 32 days to enforce service limits. Deletion immediately removes access through Aurix and queues removal of the original, thumbnail and Stream derivatives, with retries during provider outages. Cloudflare may retain limited backups or security records under its own retention practices.

Scheduled cleanup removes expired authentication and rate-limit records, completed or failed email queue records older than 30 days, abandoned upload drafts older than one day, and playback sessions with under two seconds of watch time that have been inactive for a day. Cleanup runs periodically, so expiry does not mean an immediate physical deletion. Successfully sent or permanently failed account email content is cleared from Aurix's delivery queue; the email provider has its own retention practices.

Policy acceptances, report snapshots, decisions and appeals are retained while needed to document the account agreement, review a concern, handle a dispute, protect people or meet a legal obligation. These records do not currently have an automatic expiry. Deleting a public video or comment does not automatically delete the limited text snapshot or review record. You can request access, correction or deletion through the privacy contact; we assess continuing needs and applicable legal limits before retaining a record beyond its purpose.

Aurix uses HTTPS, salted password hashes, restricted account access and controls intended to protect stored information. No online service can guarantee absolute security. If an incident requires notification to affected people or a regulator, we will provide it as required by applicable law.

11. Your controls and requests

You can update your channel profile and recovery email in Studio, change your password, choose content visibility, edit or delete your own videos and playlists, remove your comments, change reactions, and unsubscribe from channels. You can also pause future creator revenue sharing. Deleting public content does not necessarily remove accounting records or copies held by other people.

You can manage search history from Search history on Aurix or Studio. Turn saving on only if you want this optional feature. Pause to stop future saved searches while keeping existing ones until they expire or you delete them. Delete individual queries or confirm Clear all to remove every saved query. Clearing does not pause saving. These choices apply across both sites for the same account. Watch history has equivalent saving, pause, individual removal and Clear all controls. Saving remains unchanged when clearing. Paused search or watch history does not contribute to recommendations, including entries saved before pausing.

In Recommendations, choose which sources may contribute, turn AI personalisation on or off, or reset it. Reset ignores all signals saved so far while keeping the actual histories and likes. Only signals saved again after the reset contribute; an old like must be removed and added again to contribute. Deleting source history or removing a like immediately excludes that signal and invalidates earlier ranking requests and pagination. Home also offers a General view without account signals. Recommendation choices are shared across Aurix and Studio and do not control playback advertising.

For access to your personal information, corrections that are not available in settings, account deletion, removal of records without a direct deletion control, withdrawal of consent, or a privacy complaint, contact [email protected]. Aurix does not currently have an automatic account deletion or full data export tool. Those requests are handled through the privacy contact.

Describe the request and the account involved. We may need proportionate verification before disclosing or changing personal information. We will explain any lawful limits or reason we cannot fulfil part of a request, and respond within applicable legal time limits. Withdrawing consent may affect features that need the information but does not invalidate earlier lawful processing.

Depending on where you live and the law that applies, you may have additional rights such as portability, restriction or objection to processing. You can raise a concern with the Office of the Privacy Commissioner of Canada or the appropriate provincial or other privacy authority.

12. Children and parents

Aurix accounts are for people aged 13 or older. Aurix is not intended for children under 13. If local law requires an older age or parental permission for a particular use of personal information, those requirements also apply.

Signup requires you to confirm that you are at least 13. Aurix does not collect a date of birth or use an automated age verification system. This confirmation is not proof of age. A parent or guardian who believes a child has provided personal information in circumstances requiring parental consent can contact [email protected]. We will review the concern and take appropriate steps, which may include restricting the account or removing information as required. Children and youth require particular care in deciding what to share publicly and what constitutes meaningful consent.

13. Changes to this policy

We will publish an updated policy with a new effective date when our practices change. We will give additional notice and request fresh consent where required, including before introducing a materially different use of personal information. Live advertising or payout onboarding must be accompanied by updated information about the actual providers, data and choices involved.