Privacy policy

Last updated September 21, 2026

This policy explains what information we collect, why we collect it, how we handle it, and your rights. We do not sell your personal information.

This policy applies to all products built and maintained by Iterator, Inc. (“Iterator”, “we”, “us”, or “our”), including these products and websites.

• Our websites, including itrtr.com, slpwy.com, skipper.dev, screenrecording.ai, and milestracker.app
• Skipper, meaning the service at app.skipper.dev and Skipper for Mac
• Screen Recording for Mac
• Miles and our other iPhone and Mac apps

Most of it applies to all of them. Where a section applies to one product, it says so.

What we collect and why

Our guiding principle is to collect only what we need. The following sections describe what each product needs.

Skipper

Identity and access. You sign in to Skipper with GitHub. GitHub gives us your account’s numeric ID, username, display name, email addresses, and avatar URL. We use these to create your account, show you to your teammates, and contact you about the service. We also store the access token GitHub issues, for as long as the connection lasts, so we can act on your behalf and read the organizations and repositories you grant us. Revoking that token in your GitHub settings ends our access immediately.

Workspace and team information. When you create a workspace, we store its name, its GitHub organization, and its members. When you invite someone, we store the name, email address, and GitHub username you enter so we can send the invitation and show it as pending. If you connect Slack, we store the tokens and workspace identifiers needed to post there for you.

Skipper for Mac. The Mac app runs on your machine against your local checkouts. It does not upload your source code, repositories, terminal output, or agent conversations to our servers through ordinary diagnostic events. It checks for updates against dl.skipper.dev. These checks reach our content delivery provider as ordinary web requests carrying your IP address and your app and macOS versions. With Share diagnostics enabled, the app sends the reports described under “Diagnostics from our apps”, including crash reports that can contain memory fragments.

Cookies. One first-party cookie keeps you signed in to app.skipper.dev.

Screen Recording

No account and no content servers. Screen Recording runs entirely on your Mac. Recording, transcription, and editing happen on your machine, and the results are ordinary files on your disk. There is no account to create, and we run no servers that hold recordings. When you share a recording, it goes to your own iCloud account under your agreement with Apple. We never receive a copy.

Trial and license. The app stores the date your free trial started, on your Mac, so it can tell you when the trial ends. When you buy a license, our payment processor collects your payment details and the email address to send the license to. We keep a record of the purchase, your email address, and the license we issued so we can deliver the license, help you recover it, invoice you, calculate tax, and detect fraud.

Outbound requests. Screen Recording sends update checks and diagnostics. An update check against our release server reaches our content delivery provider as an ordinary web request carrying your IP address and your app and macOS versions. The diagnostics are described below.

Miles

No account and no location servers. Miles runs on your iPhone. It records your drives with the location and motion services of the phone, and it stores them in a database on the phone and in the private database of your own iCloud account, under your agreement with Apple, so your other devices can read them. There is no account to create, and we run no servers that hold drives, routes, places, or expenses. We never receive a copy of your location history.

Apple Maps. To turn coordinates into addresses and to compute the distance of a drive you add by hand, the app sends those coordinates or addresses to Apple Maps under Apple's privacy terms. They do not reach us.

Subscription. You subscribe through the App Store. Apple collects your payment details and handles billing, trials, and cancellation. We receive a receipt that identifies the subscription, not you, so the app can tell whether it is active.

Diagnostics and measurement. Share diagnostics is on by default. Miles sends approved usage events, purchase facts, crash reports, and performance reports to Iterator's service at lookout.itrtr.com/lookout/, hosted on Google Cloud in the United States. Google's load balancer forwards the requests to the service. Reports include app version, device model, operating system, language, connection country, a random Measurement ID, and a session ID. Purchase events include App Store product and transaction identifiers, price, and currency, never payment details. Event properties do not include drives, addresses, routes, notes, receipts, or text you enter. Crash reports contain stack frames and device state. Raw crash memory can include fragments of app data and is kept for 30 days. Events and crash reports are kept for 400 days and performance traces for 180 days. Purchase and conversion records may be retained for reconciliation, refunds, and disputes.

Turning Share diagnostics off stops capture, removes queued reports, and deletes the Measurement ID. A later opt-in creates a new ID. A minimal permission update can still be sent to stop advertising delivery. An in-flight request can complete. To request server-side deletion, email humans@itrtr.com with the Measurement ID shown in Settings, then Privacy. We explain any records retained for a continuing purpose.

Advertising measurement. Separate settings control advertising measurement and personalization. Miles requires your choice and Apple's tracking permission before sending permission-gated requests through alpha.itrtr.com/lookout/. Approved conversions and matching identifiers, including the advertising identifier when authorized, can be shared with configured Google, Meta, LinkedIn, X, or AppLovin destinations to measure and improve Iterator's advertising. Each destination must be configured and support the available identifiers. Miles does not collect your email address or phone number for matching. Refusing advertising permission does not stop first-party diagnostics. Turning a choice off prevents new eligible exports once the service receives the update. It cannot recall data a partner already received. Apple separately provides Apple Ads attribution and privacy-preserving conversion postbacks. Miles updates Apple's conversion values only while Share diagnostics and advertising measurement are both on. Apple controls their timing and may deliver an already submitted signal after sharing is turned off.

Diagnostics from our apps

Our iPhone and Mac apps use Iterator's Lookout service, hosted on Google Cloud in the United States, for optional crash reports, handled application errors, hang reports, performance measurements, and feature outcomes. These reports help us investigate failures and improve reliability.

Share diagnostics is off until you enable it in newly instrumented apps, including Skipper for Mac. Miles retains its existing choices and default. Screen Recording preserves saved choices and defaults to off when no choice has been saved. You can change the choice in the app's settings. Turning it off stops capture, clears queued reports, and deletes the random installation identifier. A later opt-in creates a new identifier. An already transmitted request can complete.

Reports include app, platform, environment, app version and build, operating system, device model, locale, country inferred from the connection, and random installation and session identifiers. Workflow events add a fixed feature name, random operation identifier, attempt number, duration, and success, failure, or cancellation outcome. Ordinary event properties exclude source code, task titles, file paths, recordings, transcripts, note text, and locations. We do not connect these new diagnostic integrations to an advertising identifier or user account.

Crash reports contain stack frames, device state, and memory fragments that can include data the app was handling. Raw crash memory is kept for 30 days. Events and crash reports are kept for 400 days and performance traces for 180 days. The separate Miles advertising and purchase rules are described above.

Billing information

If you sign up for a paid Iterator product, you will be asked to provide your payment information and billing address. Credit card information is submitted directly to our payment processor and doesn’t hit Iterator servers. We store a record of the payment transaction, including the last 4 digits of the credit card number, for purposes of account history, invoicing, and billing support. We store your billing address so we can charge you for service, calculate any sales tax due, send you invoices, and detect fraudulent credit card transactions.

Website and service logs

Our web servers keep standard request logs, including IP address, time, page requested, and browser and operating system versions. We use them to run the service, investigate errors, and detect and prevent abuse. We log Skipper sign-ins by IP address for the same reasons.

No Iterator page loads a third-party analytics script. Our websites do not use tracking cookies. Advertising measurement for Miles is described above.

Voluntary correspondence

When you email Iterator with a question or to ask for help, we keep that correspondence, including your email address, so that we have a history of past correspondence to reference if you reach out in the future.

We also store information you may volunteer, for example, written responses to surveys.

Your code and the coding agents you run

This section applies to Skipper.

Skipper for Mac runs AI coding agents from other companies, such as Claude Code, Codex, or Gemini, with the accounts, subscriptions, and API keys you supply. When you run an agent, it sends your prompts and the parts of your code it needs to that company, under your agreement with them and their privacy policy, not this one.

That traffic does not pass through our servers, and we do not receive a copy. Read the privacy policy of any agent provider you configure. Their policy, not this one, governs what they do with your code.

When we access or disclose your information

To provide products or services you’ve requested. We use some third-party subprocessors to help run our applications and provide the Services to you, including cloud and database hosting, content delivery and network security, source code hosting and identity, error and performance monitoring, and payment processing. They process information only to provide those services to us. We name our current providers if you ask.

We may disclose your information at your direction if you integrate a third-party service into your use of our products. Connecting GitHub to Skipper lets us read the organizations and repositories you grant. Connecting Slack lets us post to the channels you choose. Sharing from Screen Recording sends the recording to your iCloud account. Miles syncs your drives through your iCloud account. You can disconnect or stop sharing at any time.

No Iterator human looks at your content except for limited purposes with your express permission, for example, if an error occurs that stops an automated process from working and requires manual intervention to fix. These are rare cases, and when they happen, we look for root cause solutions as much as possible to avoid them recurring. We may also access your data if required in order to respond to legal process (see "When required under applicable law" below). Screen Recording and Miles keep no content on our servers, so there is nothing of yours for us to look at.

To help you troubleshoot or squash a software bug, with your permission. If at any point we need to access your content to help you with a support case, we will ask for your consent before proceeding.

To investigate, prevent, or take action regarding restricted uses. Accessing a customer’s account when investigating potential abuse is a measure of last resort. We want to protect the privacy and safety of both our customers and the people reporting issues to us, and we do our best to balance those responsibilities throughout the process. If we discover you are using our products for a restricted purpose, we will take action as necessary, including notifying appropriate authorities where warranted.

Aggregated and de-identified data. We may aggregate and/or de-identify information collected through the services. We may use de-identified or aggregated data for any purpose, including marketing or analytics.

When required under applicable law. Iterator is a U.S. company and all data infrastructure are located in the U.S.

• Requests for user data. Our policy is to not respond to government requests for user data unless we are compelled by legal process or in limited circumstances in the event of an emergency request. However, if U.S. law enforcement authorities have the necessary warrant, criminal subpoena, or court order requiring us to disclose data, we must comply. Likewise, we will only respond to requests from government authorities outside the U.S. if compelled by the U.S. government through procedures outlined in a mutual legal assistance treaty or agreement. It is Iterator’s policy to notify affected users before we disclose data unless we are legally prohibited from doing so, and except in some emergency cases.
• Preservation requests. Similarly, Iterator’s policy is to comply with requests to preserve data only if compelled by the U.S. Federal Stored Communications Act, 18 U.S.C. Section 2703(f), or by a properly served U.S. subpoena for civil matters. We do not disclose preserved data unless required by law or compelled by a court order that we choose not to appeal. Furthermore, unless we receive a proper warrant, court order, or subpoena before the required preservation period expires, we will destroy any preserved copies of customer data at the end of the preservation period.
• If we are audited by a tax authority, we may be required to disclose billing-related information. If that happens, we will disclose only the minimum needed, such as billing addresses and tax exemption information.

If Iterator is acquired by or merges with another company, we will notify you well before any of your personal information is transferred or becomes subject to a different privacy policy.

Your rights with respect to your information

At Iterator, we strive to apply the same data rights to all customers, regardless of their location. These rights include the following.

• Right to Know. You have the right to know what personal information is collected, used, shared or sold. We outline both the categories and specific bits of data we collect, as well as how they are used, in this privacy policy.
• Right of Access. This includes your right to access the personal information we gather about you, and your right to obtain information about the sharing, storage, security and processing of that information.
• Right to Correction. You have the right to request correction of your personal information. Most Skipper account data comes from your GitHub profile, so correcting it there corrects it here.
• Right to Erasure / “To Be Forgotten”. This is your right to request, subject to certain limitations under applicable law, that your personal information be erased from our possession and, by extension, from all of our service providers. Fulfillment of some data deletion requests may prevent you from using Iterator services because our applications may then no longer work. In such cases, a data deletion request may result in closing your account.
• Right to Portability. You can ask for a copy of the information you have given us.
• Right to Object. You can object to how we use your information, and we will tell you what we can do about it.

Email humans@itrtr.com to exercise any of these rights. We may need to verify your identity first, usually by confirming control of the email address or GitHub account on record. We may also need to keep some information to meet legal obligations, resolve disputes, or enforce our agreements, and we will say so if that applies.

How we secure your data

All data is encrypted via SSL/TLS when transmitted from our servers to your browser. The database backups are also encrypted. Data at rest is encrypted by our hosting providers, and access to production systems is limited to the people who need it.

Data retention

We keep your information for the time necessary for the purposes for which it is processed. The length of time for which we retain information depends on the purposes for which we collected and use it and your choices, after which time we may delete and/or aggregate it. We may also retain and use this information as necessary to comply with our legal obligations, resolve disputes, and enforce our agreements. When you delete your account, we remove your personal information from our active systems, and copies in routine backups age out on our normal backup cycle.

Location of site and data

Our products and other web properties are operated in the United States. If you are located in the European Union, UK, or elsewhere outside of the United States, please be aware that any information you provide to us will be transferred to and stored in the United States. By using our websites or Services and/or providing us with your personal information, you consent to this transfer.

Changes and questions

We may update this policy as needed to comply with relevant regulations and reflect any new practices. Whenever we make a significant change to our policies, we will refresh the date at the top of this page and take any other appropriate steps to notify users.

Have any questions, comments, or concerns about this privacy policy, your data, or your rights with respect to your information? Please get in touch by emailing us at humans@itrtr.com and we’ll be happy to try to answer them!

Iterator, Inc., 2093 Philadelphia Pike #1522, Claymont, DE 19703. See also our Terms of Service.

This work is a modified adaptation of the 37signals privacy policy, used under CC BY 4.0. Iterator, Inc. has modified the original to fit its products and is solely responsible for these modifications. This adaptation is not endorsed by 37signals.