Rollit app icon
Rollit Privacy Policy

Your media stays yours.

Keep every transfer direct, local, and under your control. Rollit never uploads your photos or videos to the internet or sends them through our servers.

Direct local transfers

Your media moves device to device without passing through the internet or a remote server.

Temporary connection details

Rollit briefly stores a six-digit verification code, local connection addresses, and short-lived pairing details to connect your browser or Rollit Backup to your iPhone or iPad. Active connection details expire shortly after activity ends.

No accounts or ad tracking

Rollit does not require an account and does not use advertising trackers or behavioral analytics.

Private computer backups

Rollit Backup writes media to your chosen computer folder without uploading it to Bytely or another cloud service.

1. Scope

This Privacy Policy applies to the Rollit app, the Rollit Web Page at rollit.bytely.app, Rollit Backup for Chrome, the Rollit Backup Mac app and Safari extension, and related local transfer services operated by Bytely. It explains how information is handled when you add media to Photos, back up media to your computer, or use hosted pairing.

2. Information on your iPhone or iPad

  • Photos and videos: Media added from your computer stays in the Rollit folder on your iPhone or iPad until you move it to Photos or delete it. When you start a backup, the items you choose are read from Photos and streamed directly to your computer.
  • Photos permission: Rollit requests access only when needed to save media into Photos or let you browse and back up items you select.
  • Camera permission: The camera is used only when you choose to scan a QR code to pair a browser.
  • Local network permission: This is used to run the local transfer server and connect your computer directly to your iPhone or iPad.

3. Hosted browser and backup pairing

When you choose Rollit Web Page or use a Rollit Backup session that relies on hosted pairing, Rollit temporarily sends connection details to Bytely's pairing service so your browser or Mac can find your iPhone or iPad. These details include:

  • A six-digit verification code and pairing identifier.
  • Random browser and session identifiers, temporary access tokens, and short-lived claim tokens used to resolve a backup connection.
  • Your local network address, hostname, and port.
  • The app name, connection status, and expiration time.

Rollit does not send a separate device display name. However, a local network hostname may include a name assigned to your iPhone or iPad.

Your media is never sent to the pairing service. Photos, videos, filenames, and file contents transfer directly between your browser or Rollit Backup on your Mac and your iPhone or iPad over your local network.

Bytely processes these connection details only to provide pairing and keep it secure. Active transfer records are kept while a connection is active and are scheduled to expire within up to ten minutes after the final activity. Browser pairing records are separately scheduled to expire within up to five minutes after their final activity. Closing a session requests earlier deletion. Cloudflare recovery systems may keep deleted records technically recoverable for up to 30 days.

4. Rollit Backup on your computer

Rollit Backup is available as a Chrome extension and as a Mac app containing a Safari extension. Both versions save the photos and videos you select directly from your paired iPhone or iPad to a folder you choose on your computer.

Information handled during a backup

  • The local Rollit connection address and temporary session identifiers and access tokens. When hosted pairing is used, this also includes the pairing identifier and temporary claim token.
  • The destination folder permission you select.
  • Photo and video metadata needed to name, transfer, and verify files.
  • The photo and video file bytes being saved.
  • Local progress, errors, and completed-file checkpoints used to continue or resume a backup.

Local storage and transfer

For Chrome, temporary pairing and backup-job details are stored locally in extension storage and IndexedDB. Pairing details expire after 30 minutes of inactivity. Job details may remain for up to seven days within the same browser session so an interrupted backup can report its status.

Your selected folder permission and completed-file checkpoints remain in local extension storage until you clear the extension's data or remove the extension. Rollit uses them to confirm the destination and skip files already completed when you resume. Choosing another folder replaces the saved folder permission but does not remove older checkpoints.

For the Mac app and Safari extension, the Mac app stores a security-scoped bookmark for the folder you choose. The app and extension exchange temporary pairing, job, progress, and cancellation records through their private shared App Group container. Prepared connections expire after 30 minutes of inactivity, and completed-job status is removed after no more than seven days. Changing the active destination replaces the active bookmark; to reveal completed backups in Finder, the app can retain up to 24 additional per-job folder bookmarks. These records remain on your Mac and are not sent to Bytely.

Rollit Backup also creates a small hidden .rollit-backup-state folder inside the generated Rollit Backup folder. For Mac backups, it can contain incomplete transfer files and a local checkpoint journal with resource identifiers, output names, file sizes, dates, status, and error details needed to resume a backup. This information stays in the folder you choose and is not sent to Bytely.

Your backup does not pass through Bytely. Media moves directly from your paired iPhone or iPad to the folder you choose over your local network.

Extension permissions

  • Chrome: uses offscreen processing and extension storage to keep a backup running after destination confirmation and to retain local progress and resume information.
  • Safari: can access Rollit's local HTTP backup pages to support Device Name and Numeric IP Address connections. It activates only on supported private or local hosts and verified Rollit backup pages, relays only explicit backup messages, and does not collect unrelated page content or browsing history.
  • Mac app: uses the folder access you choose and a private Safari App Group so the extension can communicate with its containing app without exposing folder bookmarks to the web page.

Rollit Backup does not sell or transfer user data, use it for advertising or profiling, or use it for any purpose unrelated to its local backup function. Where the Chrome extension is distributed, its use of information complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

5. Service providers and disclosures

Cloudflare hosts and protects the online pairing service and may process standard request data, including IP address and browser information. Apple provides the App Store, Photos, and optional iCloud services. Our email provider processes support messages, which are kept only as needed to respond.

We do not sell personal information, share it with data brokers, or use it for targeted advertising. Information may be disclosed when legally required or necessary to protect users and the service.

Cloudflare operates globally, so technical information may be processed outside your country under applicable safeguards.

6. Your choices and rights

You can avoid online pairing by choosing Device Name or Numeric IP Address. You can manage Rollit permissions in Settings, close an active transfer session, and delete files stored in Rollit.

You choose the computer folder used by Rollit Backup and can change it from the extension. Removing the extension clears its extension-owned local storage. Files already written to your chosen folder, including the small backup-state folder, remain under your control and can be deleted with your computer's normal file tools.

Where privacy law applies, you may contact us to exercise your rights over the limited connection or support information handled by Bytely. You may also complain to your local data protection authority.

Because Rollit has no accounts and pairing details expire quickly, we may be unable to identify an expired session.

7. Security

Hosted pairing uses HTTPS, short-lived access tokens, verification codes, rate limits, and automatic expiration.

Browser media transfers over your local network currently use local HTTP with a random session token and are not protected by local TLS. Use Rollit on a trusted network and close the transfer screen when finished.

8. Children's privacy

Rollit is not directed to children under 13 or the minimum age required in their country. Contact us if you believe a child has provided personal information.

9. Changes to this policy

We may update this policy when Rollit, its providers, or legal requirements change.

10. Contact

For privacy questions or requests concerning Rollit, contact Bytely at [email protected].

Contact Support