Terms & Privacy
Jog’s terms and privacy policy: an agreement between you and Machine Intelligence Technologies, Inc. (“Machine Intelligence Company”, “we”), a Delaware corporation. Using Jog means you agree to them. If they change, we’ll post the new version here, dated, before it applies.
We don’t sell your data. We don’t use it for ads. We don’t use it to train AI.
What Jog does
Jog runs your GitHub Actions jobs. You add one of our GitHub Apps, change runs-on to jog, and each job gets a brand-new computer of its own. After the job, we delete the computer and its disk.
There are two Apps. Jog CI is for organizations. Jog Personal is for your own GitHub account. It runs on private repositories only.
What we collect and why
What we need to run your jobs, show them to you and bill for them, and how people use the site, so we can make it better:
- Who you are on GitHub: your user ID, username and profile picture, and the accounts and repositories you can reach.
- Where Jog is installed: the accounts that added Jog and who added it; their repositories’ names and settings; and who changed a setting or limit, or asked to add Jog.
- Your jobs: repository, workflow, job name, branch, commit, pull request and who started it, plus its size, status, timings and cost. For your jobs that don’t run on Jog yet, we note their workflow, job name and runner labels. To size Jog for you and estimate your savings, we read your last two weeks of GitHub Actions runs and save only the totals.
- Billing: your Stripe customer ID, who paid, your top-ups, receipts, refunds and disputes, credit we gave you and why, and what each job cost. If an automatic top-up fails, we note the card’s brand and last four digits so we can tell you which card.
- The waitlist: if you leave an email address while you wait, the account’s owners and our team can see it, and we use it once, to tell you you’re in.
- How you use the site: the pages you open and when, the page that sent you, what you click, how far you scroll, links you follow out, your browser, system, device, screen and window size, language and time zone, and the city, region and country your IP address points to. We don’t keep the IP address. When you sign in, we link your visits to your GitHub account. On our public pages we also record a replay of your visit: what the page showed and where you moved, scrolled and clicked. Anything you type is hidden. We do this ourselves, with no outside analytics company.
- Cookies and your browser: cookies to keep you signed in and to sign in safely, one that remembers your browser for a year for the site analytics above, and settings saved in your browser: your theme, time zone, tables, files you’ve marked viewed and notices you’ve dismissed. Profile pictures load straight from GitHub.
What we never keep
- We never store your code, logs or secrets. Your job’s computer gets your code and secrets straight from GitHub and sends its logs straight back, and we never save them. From the computer we hear only which part of the job it’s in and how long each part took. When you open a pull request or a failed step in Jog, we read its changes, comments or last log lines from GitHub and hold them in memory to show you.
- We never store your GitHub sign-in token. We use it while you sign in to read who you are and what you can reach, hold it in memory only for those reads, and never save it.
- We never store your card number. Stripe takes your card, and we never receive the number.
We don’t sell your data. We don’t use it for ads. We don’t use it to train AI.
Security
- Every job gets its own fresh virtual machine. It’s never shared with another job or another customer, and it’s deleted with its disk after the job.
- Each machine gets a single-use runner registration from GitHub, good for its one job, so there are no long-lived runner tokens to steal.
- Neither App asks for your repositories’ contents, so Jog can’t clone your repositories. They can read pull requests, including their changed lines, which Jog shows you beside your jobs.
- Jog Personal is different from Jog CI because of GitHub’s limits. Jog Personal asks for Administration on the repositories you choose, because GitHub requires it to add a runner to a repository. That permission could also change those repositories’ settings; we use it only to add, find and remove Jog’s own runners.
- Every webhook from GitHub is checked against its signature.
- GitHub decides who can see an account. We check again when someone joins or leaves, and every time someone moves money.
- Our database is backed up continuously.
Found a security problem? Email [email protected]. A real person reads it, and we’ll work with you to fix it.
Who else handles it
- GitHub
- Stripe
- Cloudflare
- Sentry
- Slack
- The server companies whose machines run our service and your jobs’ computers
Each follows its own privacy policy. At Jog, the people who run the service can see account data, to help you and fix things. Nobody else gets it unless the law requires it.
How long we keep it
- A browser sign-in lasts 30 days, unless you sign out sooner.
- A job’s computer and disk are deleted after the job.
- Your sign-in history: 90 days.
- Site analytics: 90 days, then only daily totals. Recordings of the public pages: 30 days. The analytics cookie, and when your browser first and last visited: a year after your last visit.
- Job, billing and account records, and a note that you’ve signed in before, stay until you ask us to delete them, even after you uninstall, so your history and receipts add up if you come back.
- What we delete can stay in our backups for a while.
Your choices
- Stop anytime: uninstall the Jog App on GitHub and we stop your jobs, including any that are running. Before you uninstall, turn off automatic top-ups and refund any unused credit in Billing, because Billing closes with the App. Afterwards, email us for either.
- Revoke Jog’s sign-in in your GitHub settings, under Applications, and we sign you out everywhere.
- Want a copy of your data, or want it deleted? Email us, and we’ll check it’s really you. If you ask us to delete it, we keep only what the law requires.
The rules
- Use Jog for your own builds, tests and deploys.
- No crypto mining, no attacking or scanning other people’s systems, no spam, and nothing illegal.
- Don’t try to break Jog, get around its limits, or resell it.
If a job breaks these rules, we may stop it, and we may close the account.
Paying
- You pay ahead: an owner adds credit by card on Stripe’s checkout page, and jobs draw it down. An organization adds $100 at a time. Jog Personal starts as low as $20 and steps up with how much you run, to at most $100. Credit doesn’t expire. Some accounts have free use or a credit line we’ve agreed with them.
- Every paying account gets 5,000 free minutes each calendar month (UTC), counted at 2 vCPU, so bigger machines use them faster: a minute on 32 vCPU uses 16. They’re used before your credit, while you have credit. They aren’t money: they don’t carry over and aren’t refunded.
- Each size has a price a minute, and a job is charged by the second, from the start and end times GitHub reports: 2 vCPU $0.0012, 4 vCPU $0.0024, 8 vCPU $0.0044, 16 vCPU $0.0088, 32 vCPU $0.0176.
- Your first top-up saves your card and turns on automatic top-ups: when your credit falls below $10, we add another top-up ($100 for an organization; for Jog Personal, $20 to $100, sized to your last 30 days), with the receipt in Billing. If the card is declined, we turn them off and don’t try again. You can turn them off anytime in Billing.
- New accounts may wait on our waitlist first. Automatic top-ups don’t charge while you wait. If we can’t let you in, or you remove Jog while you wait, we refund your credit.
- At $0, new jobs wait until you add credit. A job already running finishes, even if it takes you below zero. With a credit line, running jobs stop when you reach its limit.
- Unused credit you paid for is refundable from Billing, back to the card it came from, once running jobs, pending payments and any dispute have settled. Credit we gave you is spent last and isn’t refunded as cash. After a refund, neither the account nor the person refunded can add credit for 7 days, because Stripe keeps its fee on every refund.
Legal basics
We keep all rights in Jog; you keep all rights in your code and data. You must be 18 or older, or using Jog for a company that agreed to these terms. If you send us feedback, we may use it freely. JOG IS PROVIDED “AS IS,” WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. TO THE MAXIMUM EXTENT PERMITTED BY LAW, WE ARE NOT LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR LOST PROFITS, DATA, OR GOODWILL, AND OUR TOTAL LIABILITY WILL NOT EXCEED THE GREATER OF WHAT YOU PAID US IN THE PRIOR TWELVE MONTHS OR US $100. You’re responsible for what your jobs run. These terms are governed by the laws of the State of California, with exclusive venue in San Francisco County, California. You may not assign them without our consent; we may assign them freely. If part of them is unenforceable, the rest stands. This is the entire agreement about Jog.
Contact
We’re real people. Write to [email protected], or find us at 1550 Mission St, San Francisco, CA 94103.