Privacy Policy

The Website

The public website provides product and support information. It does not require an account and does not include advertising or analytics trackers. The hosting provider receives ordinary request information, such as IP address, browser information, time, and requested page. External links are governed by the destination's privacy terms.

Data Handled on Your Device

On supported YouTube pages, the extension can read a URL or item identifier, title, creator name, visible text, available captions, image text, thumbnail or media references, language, duration, playback position, and whether an item is current or nearby in the feed. It stores settings, consent choices, service status, and recent filtering activity in Chrome. Each of its two activity lists is limited to 300 records. Activity can include an identifier, URL, title, decision, reason, duration, action, and timestamp.

Local filtering is the default. With cloud analysis and usage sharing off, a clean Local install creates no remote installation or session and sends no YouTube content to Orislop. Local mode can make checks with optional software running on your device; those requests stay on your device. Optional usage sharing in version 1.4.13 has its own consent control and sends only the limited counts described below. You can clear recent activity and local settings in the extension. Withdrawing cloud consent returns the extension to Local; clearing browser activity does not itself delete cloud records.

Optional Cloud Analysis

Cloud analysis starts only after you accept its in-extension disclosure. It creates a pseudonymous installation session and can send an eligible video's identifier, temporary media link, limited playback details, language, processing priority, coarse device or network capability information, and session credentials. If a link cannot be analyzed, Orislop may automatically upload a limited video segment, which may include audio. Cloud requests also provide ordinary IP address and request information to hosting and security providers.

The cloud request does not add locally read title, creator name, visible page text, captions, local reasons, or activity history. The video itself can contain personal or sensitive material. Enable cloud analysis only if you are comfortable sending eligible media for processing.

Optional Usage Counts in Version 1.4.13

Usage sharing is off by default and has a consent choice separate from cloud analysis. The Cloud prompt offers an explicit combined choice, a Cloud-only choice, and device-only filtering. Accepting Cloud only or an older Cloud disclosure does not enable usage sharing. When you select Accept cloud & usage counts in the Cloud prompt or enable Share pseudonymous counts in Settings, Orislop sends a randomly generated installation identifier, random event identifiers, extension version, first-open and first-applied-filter events, one useful-activity event per UTC calendar day, and batched counts of completed filtering decisions, items covered or hidden, and technical failures. A genuine fresh install can include its UTC calendar date; an upgrade does not invent an old install date. Activity can include a coarse UTC day so a delayed upload does not change the activity day. Requests are sent to Orislop's HTTPS API and stored in its existing hosted database for the private founder dashboard.

The installation identifier links your opted-in usage across sessions, so this data is pseudonymous, not anonymous. It is separate from website and cloud-account identifiers. These payloads do not include video or audio, video identifiers, titles, creators, URLs, page text, browsing history, messages, account details, IP addresses, or arbitrary error descriptions. Hosting and security providers still receive ordinary network request information such as your IP address; Orislop does not add it to these analytics records. The public website does not join visitors to extension installations.

The counts help Orislop understand useful activity, activation, retention, filtering use and reliability. They do not establish detection accuracy, identify confirmed uninstalls, or reconstruct activity before consent. No advertising, sale of data, fingerprinting, referral rewards, or individual browsing profile is added. Orislop's founder can access the private dashboard for these disclosed product-improvement purposes.

Usage records expire after 90 days and are removed by scheduled application cleanup. Bounded pending counters and event identifiers are stored locally for retry. Turn the usage toggle off to stop collection, cancel pending requests and remove the local analytics identifier and queued counts; clearing activity and settings also turns it off. Already received records expire under the 90-day schedule. The genuine coarse install date and its sent marker can remain locally to prevent duplicated or invented installs. A later opt-in creates a new pseudonymous identifier. Provider logs, snapshots and backups may follow their own schedules. Local filtering remains available when usage sharing is off.

Accounts and Feedback

Version 1.4.12 does not offer new Google sign-in. An older linked account can still show its display name and email, be signed out, or be deleted. If older linked-account state is found, opening the popup may contact Orislop to confirm account status while Local is selected. Incomplete older session information can create a pseudonymous installation session. This status check does not send YouTube content or enable cloud media analysis.

The optional seven-day feedback prompt, its timing, dismissal, and email-link click are stored locally. Clicking the link opens a draft in your email application. Orislop receives your email address and message only if you send it, and your email provider also processes that message.

Why We Use Data

Orislop uses extension data to provide and improve selected filtering features, explain recent filtering activity, operate optional cloud analysis, maintain accounts and deletion controls, prevent abuse, and keep the service reliable. Orislop does not sell extension data, use it for personalized advertising, or use it for credit or lending decisions.

Limited Use and Human Access

Orislop limits use and transfer of extension data to the disclosed filtering feature, service operation, security, legal requirements, and permitted aggregate internal operations. Orislop's use of information received from Chrome and Google APIs follows the Chrome Web Store User Data Policy, including Limited Use. People may access extension data only with your specific consent, when needed for security or abuse investigation, when required by law, or after aggregation and de-identification for internal operations.

Service Providers

Hosting, database, cloud-processing, security, and email providers receive the data needed for their role and process it under their own contracts and policies. YouTube receives requests when media is loaded. The reviewed extension has no advertising or data-broker integrations.

Retention

Local preferences and consent remain in Chrome until removed by you, the extension, or the browser. Recent activity is bounded as described above. The cloud application is configured so access credentials expire after 15 minutes, refresh sessions after 30 days, analysis decisions after 30 days, explicit in-service feedback after 90 days, usage-quota events after two days, and service-reliability events after 30 days. Keyed rate-limit records expire after five minutes. Accounts remain until deletion.

Temporary media-upload staging is scheduled to expire after 10 minutes, and the application is designed to remove its analysis copy after the final attempt. Failures can delay cleanup. Provider logs, security records, snapshots, and backups can follow their own schedules; their deletion has not been independently verified. Support email follows the retention of the support mailbox and email providers and is separate from in-service feedback retention.

Your Choices and Security

You can use Local without cloud analysis, withdraw cloud consent, clear recent activity and local settings, delete pseudonymous cloud data, and delete an older linked account through available extension controls. Deleting cloud data does not delete email you chose to send. Cloud requests use HTTPS. For help with access, correction, or deletion, contact support@orislop.com.

Children, Changes, and Contact

Orislop is not designed as a child-data service and has not implemented a verified parental-consent program. Do not enable cloud processing for a child under 13. Material changes to extension data practices require an updated policy and any required disclosure or consent. Orislop is operated by Aarush Shah. For privacy questions or requests, email support@orislop.com.

Voluntary Uninstall Feedback

When you uninstall version 1.4.12, Chrome opens our uninstall survey. Opening this page does not submit a response or send extension activity. If you choose to submit, Orislop receives your selected reason and any optional written feedback, and records a server-generated submission time. No account, name, email address, or other identifying field is required. Please do not include personal information in your message.

Survey responses are stored separately from account and analysis records and are scheduled for deletion after 90 days. The survey does not attach installation identifiers, browsing or YouTube history, video data, device fingerprints, or IP-derived profiles. A global submission limit helps prevent abuse without storing an IP address with the response. Hosting providers still receive ordinary request information as described above; provider logs and backups can follow their own retention schedules. Voluntary feedback helps us understand problems and improve Orislop. The survey adds no analytics trackers and does not change on-device filtering or cloud-consent choices.

Website Feedback and Support Email

You can also submit a topic and message at our feedback page without an account or email address. Website and uninstall submissions are saved for the support team and automatically queued for an email notification through Resend to the Orislop support team's Gmail inbox. A temporary delivery queue stores the message and a random submission identifier used only to retry that email, not to identify you. These form records and queued copies are scheduled for deletion after 90 days. Copies in the support mailbox and email-provider records follow their own retention schedules; the 90-day application cleanup does not delete those copies. Messages may be read by Orislop support to respond to issues and improve the product. Please do not include personal or sensitive information. The forms do not add analytics tracking or collect extension history.

Limits

Detection is imperfect. A result is a signal, not proof, and uncertain content stays visible.

Back to Orislop