Privacy policy
Last updated October 7, 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, milestracker.app, and plusone.dev
- Skipper, meaning the service at app.skipper.dev and Skipper for Mac
- Screen Recording for Mac
- Lightbox, Riff, and our other Mac apps
- Plus One, the account for our apps and the plans and credit packs it sells, at www.plusone.dev and account.plusone.dev
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. Unless you turn off Share diagnostics, 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 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. We run no servers that hold recordings. When you share a recording, the app saves it as an MP4 file on your Mac and hands it to the sharing service you choose in macOS, such as Mail, Messages, or AirDrop. We never receive a copy.
Plus One. Screen Recording is free and needs no account. If you sign in to it with your Plus One account, the account works as described under Plus One. Nothing about your recordings reaches the account. Buying a Plus One plan or credit pack in Screen Recording opens our web checkout in your browser, as described under Web purchases.
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.
Plus One
Your account. Plus One is one account at plusone.dev that our apps can sign in with. It holds your email address, your name if you give it or Sign in with Apple shares it, the sign-in methods you add, and the devices and browsers signed in to it. For Sign in with Apple we keep the identifier Apple gives us for you and the token that lets us revoke the sign-in when you delete the account. For a passkey we keep its public key and credential ID, and its private key never leaves your devices and their password manager. For an emailed code we send a code to your address. We email you only sign-in codes and messages about your account, never marketing. For each signed-in device or browser we keep what kind it is (iPhone, iPad, Mac, or web browser), when it signed in, and when it was last used, so the account can list it and you can sign it out. The record of a device that signs out is deleted 90 days later. The account ID is a random identifier that never changes and carries no meaning.
Signing in on your other devices. When one of our apps signs in on a Mac, it also saves a sign-in credential, a random value, in your iCloud Keychain. Apple syncs it, end-to-end encrypted, to your devices signed in to the same Apple Account, and our apps there use it to sign in to your Plus One account without asking. We keep only a hash of it and when it was last used, and a credential nobody uses for 400 days expires. Signing out on one device stops our apps on that device from using it until you sign in there again. Sign out everywhere, on your account page at account.plusone.dev or in any of our apps, signs out every device and browser and revokes every such credential, and deleting your account does the same.
The apps you use. When one of our apps signed in to your account reads your plan, we record which app it is and when you first and last used it, at most once an hour. The Plus One app and your account page use this record to list the apps you use, most recent first. We keep it until you delete your account, and deleting the account deletes it.
Free credits. A new account gets free credits once, after it signs in to one of our apps on an iPhone, iPad, or Mac. To keep one person from collecting them again and again with new accounts, the app sends us a DeviceCheck token from Apple when your account claims them. We pass the token to Apple's DeviceCheck service, which confirms that it comes from a genuine Apple device running our app, tells us whether that device already gave free credits to an account, and then records that it has, in two bits Apple keeps for each device for our developer team. Apple keeps those bits, not us, and they name no account and no person. We store no identifier of your device, only that your account claimed its free credits. We use the token and the bits only to prevent fraud with free credits, never for advertising or to track you across apps or websites.
Sign in with Apple and private relay. When you sign in with Apple, you can hide your email address. Apple then gives us a private relay address, and mail we send to it reaches you through Apple without our learning your own address. If you turn off forwarding for that address in your Apple Account, our emails, sign-in codes included, no longer reach you, and you can still sign in with Apple or with a passkey.
Plans, purchases, and credits. The account records your plan, where you bought it, its status and renewal date, the credit packs you buy, and your credit history, meaning each grant, each use with the app and feature that used it, and each refund. We use them to make your credits available in every app you sign in to, show your balance and history, answer billing questions, and detect fraud.
App Store purchases. When you buy Plus One with In-App Purchase in Plus One on iPhone or iPad, Apple collects your payment details and handles billing under its privacy policy. The purchase carries your account ID so we can attach it to your account, and Apple sends us the transaction, never your payment details. If you ask Apple for a refund, Apple can ask us about your use of the purchase. With the consent you give in our Terms of Service, we tell Apple that the purchase was delivered, that our apps can be used for free, what share of a credit pack’s credits you spent, and whether we would prefer Apple to refund it in full, in part, or not at all, which for a credit pack follows that share. We send nothing else about you. You can withdraw that consent under Refund requests on your account page at account.plusone.dev, and we then stop answering.
Web purchases. On the web, Plus One is sold through Link, the merchant of record service of our payment processor Stripe. When you subscribe or buy credits at account.plusone.dev, including from Screen Recording, which opens it in your browser already signed in, Link collects your payment details, name, email address, and billing address on its checkout page, under Link’s privacy policy, and can offer you a Link account to manage the order. Card numbers go to Link and never reach our servers. We give Stripe your email address and account ID to set up the checkout, and we receive the plan or pack you bought and its status, linked to your account ID.
Purchase records. Lookout, a service we run ourselves, keeps the record of each Plus One purchase, renewal, cancellation, refund, and dispute from Apple and Stripe, including the amount, the plan, and, for a web charge, the billing details on the invoice, linked to your account ID. While you are signed in to one of our apps with Share diagnostics on, the app also tells Lookout your account ID, so Lookout can connect a purchase to the app it was made in, as described under “Diagnostics from our apps”.
Deleting your account. You can delete your account in the account screen of any of our apps or at account.plusone.dev. We then sign out every device, revoke your Sign in with Apple authorization with Apple, cancel a plan bought on the web at once, revoke every sign-in credential saved in iCloud Keychain, and delete your email address, name, Sign in with Apple identifier, passkeys, the record of the apps you used, and the link to your payment account at Stripe. Apple keeps a device's DeviceCheck bits, so a device that gave free credits to your account cannot give them to another account. The records of your signed-out devices are deleted 90 days later. We keep the records of your purchases, refunds, and credits, including the history of what used your credits, linked to the account ID and without your email address or name, for seven years after you delete the account, as tax and dispute rules require. Lookout keeps its purchase records, linked to the account ID, for reconciliation, refunds, and disputes. To ask us to delete the diagnostics or other records Lookout holds for your account, email humans@itrtr.com with your account’s email address before you delete it. A plan bought in the App Store keeps renewing until you cancel it in your Apple Account.
The sites. www.plusone.dev sets no cookies and runs no analytics or scripts. account.plusone.dev sets a first-party cookie that keeps you signed in there and runs no analytics. The checkout it sends you to is Link’s and Stripe’s, under their privacy policies.
Lightbox and Riff
Lightbox imports and edits photos on your Mac and keeps its library in your Documents folder. When iCloud Drive syncs that folder, the library reaches your other Macs through Apple's services and your agreement with Apple. We do not receive your photos, templates, or library. Riff transcribes speech and writes notes on your Mac and keeps its library in your Documents folder on that Mac. Neither app sends library content to Plus One. Optional Plus One purchases open our web checkout, and update checks use our release server.
Diagnostics from our apps
Our apps use Iterator's Lookout service, hosted on Google Cloud in the United States, for crash reports, handled application errors, hang reports, performance measurements, and feature outcomes. These reports help us investigate failures and improve reliability.
Share diagnostics is on by default in each of our apps, and you can turn it off at any time in the app's settings. The app keeps the choice you save. Turning Share diagnostics off stops capture, clears queued reports, and deletes the random installation identifier. Turning it back on 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. While you are signed in to Plus One, reports from our apps also carry your Plus One account ID, which links them to your account and to its purchases.
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.
Feedback. You can send us a report from an app with Submit Feedback in a Mac app's Help menu or menu bar icon, by shaking an iPhone or iPad, or from the app's settings. You see the report before you send it. It carries what you wrote, the screen you were on, the screenshots, photos, and videos you add (up to 10, and 1 GB together), and the app version, build, platform, and device model, and it is sent whether or not Share diagnostics is on. A photo or video you add is sent without its location. With Share diagnostics on, the report also carries the installation and session identifiers, your Plus One account ID while you are signed in, and the screens and actions just before it, so we can match it to a crash or failure. With Share diagnostics off, the report offers an Include diagnostics switch, off until you turn it on for that report. Turned on, it adds the screens and actions just before the report and your Plus One account ID while you are signed in, but never the installation or session identifiers. A screenshot or video can show anything that was on your screen. Reports and their attachments are stored in Lookout, kept for 400 days, and never used for advertising. A deletion request covers them. A report sent with Share diagnostics off carries no installation or session identifier, so tell us what it said and the day you sent it.
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.
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, 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 an MP4 of the recording through the macOS sharing service you choose. Lightbox syncs its library through your iCloud Drive. 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, Lightbox, and Riff keep no library 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. You can add passkeys to your Plus One account in our apps, and we correct its email address or name when you email us.
- 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. You can delete your Plus One account yourself in any of our apps or at account.plusone.dev.
- 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, GitHub account, or Plus One 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. When you delete your Plus One account, we keep the records of its purchases, refunds, and credits, linked to the account ID and without your personal data, for seven years, as tax and dispute rules require.
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.