BYTESLIP
Legal Documentation // Protocol 01

Privacy Policy • Byteslip Apps & Web Tools

Effective Date: October 30, 2026
ZERO TELEMETRY // OFFLINE PROCESSING
Summary: This Privacy Policy applies to Byteslip's apps and web tools, made by John Truslow ("Byteslip," "we," "us," or "our"), Hawaii, USA. That means the mp4loom mobile application (Package ID: org.byteslip.earfondle, the Android package ID carried over from the app's earlier name), the free browser tools on byteslip.org such as Leafzagonal and Inspectrosite (the "Web Tools"), and the website itself. We believe strongly in user privacy and data sovereignty. mp4loom does not collect, store, transmit, or share any personal or sensitive user data, and Leafzagonal never sends your images to us. Both work on your own device. Like any website, byteslip.org itself does see basic request data when you load a page, as explained in sections [09] and [10].

[01] Information Collection and Use

We do not collect, store, transmit, or share any personal information. mp4loom is a standalone application that operates entirely locally on your device. We do not require you to create an account, sign in, provide an email address, or submit any identifying information to use the App.

[02] Local Media & File Processing

The core functionality of mp4loom involves rendering MP4 video files and synthesizing audio using your local audio files (such as MP3s) and optional background images. All file reading, audio synthesis, and video encoding occur strictly on your device's local hardware. None of your source audio files, background images, or rendered video outputs are ever uploaded to our servers, cloud infrastructure, or third-party services. We have zero access to the media you load or create.

[03] Web Tools (Leafzagonal & Browser Tools)

Leafzagonal is a free browser tool on byteslip.org that resizes images (keeping their aspect ratio) and converts them to WebP. All of that work happens inside your browser, using the browser's built-in file reading and canvas features. Your source images and the WebP files you make are never uploaded to Byteslip, and we have no access to them. Your browser saves the converted file wherever you choose. Animated images are converted using their first frame.

Leafzagonal needs no account or sign-in. The Leafzagonal page has no analytics or tracking scripts and doesn't load third-party scripts, fonts, or services. Everything it uses comes from byteslip.org.

Opening the page is still an ordinary web request to byteslip.org, so our host's standard server access logs record that visit like any other page (see sections [09] and [10]). Those logs show that the page was loaded. They don't contain your images.

You choose which images to open, and you are responsible for having the rights to process and share them (see section [07] and our Terms & Conditions).

[04] App Permissions

mp4loom requests only the following Android permissions. You choose audio and image files through Android's built-in file picker, so the App does not request broad storage access. These permissions are used exclusively on-device for the App's core functionality.

Notifications: lets the App show a notification while a video is rendering and tell you when it's finished.

Exact alarms: lets the App deliver its local notifications at the right moment.

Start at boot: lets the App restore any pending local notifications after your device restarts.

Wake lock: keeps your device's processor awake while a render is running so it isn't interrupted when the screen turns off.

Foreground service (media processing / data sync): lets a render keep running in the background, with a visible notification, while you use other apps.

No internet access: mp4loom does not request the internet permission, so it cannot send anything off your device.

[05] Analytics and Third-Party Tracking

mp4loom does not integrate any third-party analytics trackers, advertising networks, monetization SDKs, or remote crash-reporting tools that harvest usage data, device identifiers, IP addresses, or behavioral telemetry. Your usage habits remain entirely your own business.

[06] Data Retention and Deletion

Because mp4loom does not collect, transmit, or store any personal data on external servers, we hold no user data records to retain or delete. Any project settings, preferences, or exported media files exist strictly on your local device and can be removed at any time by clearing the App's local storage or uninstalling the application.

[07] User Responsibility & Media Rights

mp4loom and our Web Tools, such as Leafzagonal, are local media tools provided "as is" without warranties of any kind. Users are solely responsible for ensuring they hold the necessary rights or permissions for any audio files, images, or media assets they process and distribute using the App or the Web Tools.

[08] Children's Privacy

Because our App and Web Tools do not collect or transmit any personal data whatsoever, they do not knowingly or unknowingly collect personally identifiable information from anyone, including children under the age of 13.

[09] Website Visitors (byteslip.org)

While the mp4loom mobile application operates strictly offline and transmits zero network data, the public website (byteslip.org) relies on a few third-party services that your browser contacts directly when a page loads. The landing page uses a third-party visit counter (countapi.mileshilliard.com), site pages load fonts from Google Fonts (fonts.googleapis.com and fonts.gstatic.com), the videos page loads video thumbnails from YouTube (i.ytimg.com) and, only when you choose to play a video, YouTube's embedded player (www.youtube.com), and the views page loads its chart library from jsDelivr (cdn.jsdelivr.net). The Leafzagonal page is an exception: it loads none of these third-party services. Each of these services receives your IP address and basic request data when the page loads, and handles that data under its own privacy policy. Donations are processed by Stripe on Stripe's own pages, and byteslip.org never sees or stores your payment details.

[10] Site Statistics & Bot Traffic

byteslip.org keeps its own anonymous counts: the number of home page views per day (Hawaii time) and the number of downloads per app, per day and per version. These counts are just numbers. No IP addresses, cookies, or personal data are stored with them, and known bots and automated tools are filtered out of those counts. The daily views are shown publicly on the views page, and download totals appear on the Apps page. Separately, the home page's "visited" number comes from the third-party countapi counter described in section [09].

Like most websites, our web host keeps standard server access logs. Those logs can include the requesting IP address, timestamp, requested URL, HTTP status, referrer, and user-agent string. We use them for security, abuse prevention, and site operations.

Bot and crawler traffic. We intentionally review and collect information about automated visitors (bots, crawlers, scrapers, scanners, and similar tools) from those access logs. That review focuses on bot user-agent strings, the paths they request, response status codes, and related request metadata so we can understand crawler behavior, protect the Site, and improve how pages are discovered. That private reviewer is called botsmeller: an owner-only page that lists automated hits from the access logs (bot name/family, country, status, whether a robots.txt Disallow path was requested, and severity). It is not a public dashboard: access is limited (IP allowlist plus a password), the public decoy path is blocked in robots.txt, and it is not meant for people or bots to browse as content. This bot-facing review is separate from the anonymous human view and download counters above, which continue to exclude known bots and do not store IP addresses with those counts. Rules for automated access—including honoring robots.txt, rate limits, and when written permission is required—are in the Acceptable Use section of our Terms & Conditions. We may block, throttle, or otherwise respond to bots that ignore those rules.

[11] Changes to This Policy

If we update this Privacy Policy in the future, any revisions will be posted directly on this page with an updated Effective Date.

Questions // Inquiries

If you have any questions or concerns regarding this Privacy Policy, you can contact the developer directly at johnny@byteslip.org or reach out via the official Byteslip YouTube channel.

Use of byteslip.org, its apps, and its web tools is also covered by our Terms & Conditions.