Rotulus Privacy Policy
Version 1.0 · Effective date: 2026-10-12
The short version
- We sell software, not data. We do not sell personal information, we do not use it for targeted advertising, and we do not share it with advertisers. We send news about Rotulus by email only to people who ask for it.
- Your scripts stay on your computer. Rotulus has no feature designed to send them to us. A script leaves your computer only when you send it somewhere yourself: to other computers with Show Sync, to web browsers with Share Script in a Browser, or in a file or message you choose to send. Error reports, if you turn them on, are built to leave script text out.
- The app has no advertising, no analytics and no tracking. Rotulus's own features use the internet only to send error reports, which are off until you turn them on, to download Google Docs you link to a script, and to check, about once a day, never within 20 hours of the last check, for a new version and for withdrawn License Keys. That check sends no License Key, name or email address, and you can turn it off. The browser engine inside Rotulus can also make a few requests of its own (see "The app: what can leave your computer"); Rotulus does not add your scripts to them.
- Our website sets no cookies, runs no analytics and loads nothing from other websites. If you pick light or dark mode, your browser remembers that choice.
- Licenses are not on sale yet. When they are, Stripe will take the payment and we will never see your full card number. We will keep a record of the sale and of your License Key.
- If you write to us, use a form on rotulus.io, ask for a Trial Key, apply for the beta, book a demo or answer the demo survey, we keep what you send only as long as this policy says.
- You can ask to see, correct or delete what we hold about you. Write to privacy@rotulus.io.
Who we are and what this policy covers
Rotulus is made by Mathusek Technologies LLC, a Utah limited liability company, which will also sell licenses. In this policy, "we" and "us" mean Mathusek Technologies LLC.
- Privacy requests and questions about this policy: privacy@rotulus.io
- Support and legal notices: support@rotulus.io
- Mail: Mathusek Technologies LLC, 10939 N Alpine Hwy PMB 119, Highland, UT 84003
- Website: rotulus.io
If Rotulus is ever transferred to another company, that company will take over this policy and the information it describes. We will post a notice of the change at rotulus.io and email license holders and beta testers before it takes effect.
This policy covers:
- the Rotulus app for Windows and macOS, every version we release;
- the website rotulus.io and its forms;
- buying a license from us, and Trial Keys;
- the closed beta, including feedback calls with testers, and demo calls and the demo survey.
This policy says what happens to information. What you and we agree to for using Rotulus, buying a license or joining the beta is in our separate agreements.
The app: what stays on your computer
Rotulus runs on your computer. Your scripts are saved wherever you save them. Rotulus also keeps working files in its settings folder:
- on Windows:
%APPDATA%\rotulus - on a Mac:
~/Library/Application Support/rotulus
Help → About Rotulus (on a Mac, Rotulus → About Rotulus) shows the exact path. Updating from version 3.67 or earlier copies the older settings folder (jumbo-pro beside it) once, the first time the new version starts, and leaves the older folder in place until you delete it. None of these files is sent to us. The one exception is error reports, which leave your computer only if you turn them on (see "Automatic error reports").
| What | What it holds | How long it is kept |
|---|---|---|
| Settings | Your preferences, your default and last save folders, speaker names, Style Key rules, client names with their script settings and show folders, the spreadsheet column mappings for run-of-show imports, which sheets of a run-of-show workbook you use as sessions (kept as short one-way codes made from the sheet names, never the names themselves), the list of fonts you imported, Show Sync settings (role, address, port and pairing code), the Share Script in a Browser codes, your error-report choice and error-report ID, your last screen layout, your choice for the update and license check, and which license and update notes you put away | Until you change or clear them |
| Copies of your settings | A copy of the last settings file that loaded correctly, a damaged settings file if one is found, and a copy taken before each Import Settings so it can be undone. A code you clear with Clear Local Data can remain in these copies | The last good copy is replaced each time Rotulus starts; a damaged file until it is replaced or you delete it; the 20 most recent Import Settings copies |
| Migration record | What the one-time copy from the older settings folder did (counts and codes, no names), and a copy of any file it had to set aside | Until you delete the settings folder |
| Auto-save snapshots | Copies of your open scripts, including their text, and the run of show you imported, taken every 30 seconds by default (you can choose 10 to 600 seconds) while something is unsaved, so you can recover your work after a crash | The newest 20 snapshots. Snapshots are not deleted by age, so one can be days old |
| Show state | While you present: that a show is being presented, which script is on air (its number and name) and how many scripts are open, the paragraph being read, the speed, the mirror setting, the presenter clock and when all this was recorded, but no script text, so a recovery after a crash can put the show back where it was | Replaced twice a second while presenting; deleted with the auto-save snapshots |
| Recovery markers | The time Rotulus last closed normally, when the current session started and when everything was last saved. No script text, names or paths | Rewritten as Rotulus starts, saves and closes |
| File backups | A copy of a file taken just before Rotulus overwrites it, and a list of the folders those files came from | The newest 100 copies, and none older than 60 days |
| Linked-source versions | A copy of each version of a Word, PDF or Google Doc file you linked to a script. For a saved script they are kept in a Versions folder beside it; otherwise in the settings folder. A newer version waiting for your decision is kept in the settings folder | Until you delete them. A version waiting for your decision is deleted if you keep your current version or close the review, and at the next start |
| Imported fonts | Copies of the font files you import | Until you delete them from the settings folder. Rotulus has no button to remove an imported font |
| Spell-check dictionary | Words you add to the spelling dictionary, kept in the file Custom Dictionary.txt in the settings folder. On Windows and macOS the operating system may also keep its own copy of an added word in its own spelling list, outside the settings folder | Until you delete the file Custom Dictionary.txt in the settings folder; a copy in the operating system's own list stays until you remove it there |
Error log (crash.log) | Technical error messages: the time, the kind of error and its details. Each time you start presenting, Rotulus also notes your displays and graphics card, including its driver version, and when you stop, how smoothly the picture was drawn. Your user name, your computer name (each unless it is shorter than three characters) and the path of your home folder are removed, and every other folder and file name in a file path is replaced by a short code that cannot be turned back into the name (the same name gets the same code until Rotulus closes; standard folders such as Documents stay readable). An error message can still contain text Rotulus was working on, such as a file name or a few words of a script | Up to about 1 MB, plus one older file (crash.log.1); older entries are deleted |
| Local crash dumps | If the app's engine crashes, technical crash files that can hold part of the program's memory, which may include script text. They are never sent anywhere | Rotulus does not delete them, and Clear Local Data does not remove them; deleting the settings folder does |
| License | Your License Key, which contains its license number, the name and email address it was issued to, the organization (if any), the edition, the number of computers and its dates, and the time you entered it | Until you remove it (Help → About Rotulus → Remove License) |
License check record (license-meta.json) | What the update and license check last found: when it last ran, the date of the last file it accepted from rotulus.io and the date Rotulus takes from that file as a check on the computer's clock, the latest version of Rotulus in that file with its date and download address, and the license numbers that file lists as withdrawn, each with the reason (never a name or email address). It also holds the license number of the last valid License Key on this computer, the last date Rotulus found it valid and, for a Trial Key, Show Pass or beta key, its end date, the day Rotulus first found that key missing, unreadable or withdrawn (for the 3-day grace period; cleared when a valid key is found again), and the latest date Rotulus has seen | Removing your License Key (with Remove License, or with Clear Local Data) deletes the last valid key's license number and dates and the day it was found missing. The rest is kept even then, so that setting the computer's clock back cannot extend a key; it is removed when you delete the settings folder |
| Unsent error reports | Error reports waiting for an internet connection (only if error reports were on) | Until they are sent. Turning error reports off deletes them, and so does Clear Local Data |
| Error-report ID | A random ID made when you first turn on error reports. It is not made from your name, license or hardware; each report carries it with the details listed under "Automatic error reports" | Until you clear the crash log and unsent error reports, which removes it (and makes a new one if error reports are on) |
| Browser-engine files | Rotulus is built on Chromium, the engine inside several web browsers, and it keeps the usual browser working files: caches, cookies, local and session storage, and a list of internet addresses it has contacted. The engine can also fetch things by itself, such as a spell-check dictionary (see "The app: what can leave your computer"). Google Docs downloads add nothing to them, because Rotulus makes those downloads in a separate session kept only in memory (see "Google Docs you link") | Managed by the engine; removed when you delete the settings folder |
Removing this information
Clear Local Data (Preferences → General) removes only the items you tick from this list: auto-save snapshots (with the show state); file backups; the last save folder; the crash log and unsent error reports (this also resets the error-report ID); the Show Sync pairing code (this also clears the Share Script in a Browser codes and stops sharing); and your License Key (this also deletes the last valid key's license number and dates, and the day it was found missing, from the license check record). It never touches your script files.
Everything else stays, including your other settings, the copies of your settings, the rest of the license check record, imported fonts, the spell-check dictionary, local crash dumps, the browser-engine files and the Versions folders. To remove everything Rotulus keeps, quit Rotulus and delete its settings folder, then delete any Versions folders beside your scripts, and the older jumbo-pro settings folder if you updated from version 3.67 or earlier.
Exported settings. If you use Export Settings, the file you save holds your client names and their show folders, Style Key rules, speaker names, Format Script options, shortcuts, defaults, preferences, the spreadsheet column mappings for run-of-show imports and imported fonts. It never holds your Show Sync or Share Script in a Browser codes, your save folders, your error-report choice or ID, or your License Key. Rotulus does not send this file anywhere; you decide where it goes.
The app: what can leave your computer
Rotulus has no advertising and no analytics. Apart from files you save or send yourself, Rotulus's own features send information off your computer only in the five ways below. Four of them start only when you turn them on or use them. The fifth, the update and license check, is on by default, and you can turn it off. Links in Rotulus, such as Help → About Rotulus → Privacy Policy or a Renew button, open in your own web browser, like any other link you open there.
What the browser engine may do. Rotulus is built on Chromium, the engine inside several web browsers. The engine can make requests of its own that Rotulus's own code does not make. For example, on Windows it may download a spell-check dictionary from a Google server, which sees your computer's IP address. Rotulus does not add your scripts or settings to any such request.
Show Sync
When you turn on Show Sync, Rotulus connects the computers you join with the same pairing code: for example a backup prompter, or an editor station where a producer edits the script. They exchange the scripts, the runlist and the playback state (speed, play or pause, and position), and an editor station sends its edits back. The connection goes directly between those computers. It does not pass through our servers or any internet service. Show Sync never starts by itself when Rotulus opens.
The pairing code protects the connection. A computer that does not know the code cannot join or send commands. The scripts, the runlist, the playback state and an editor station's edits are encrypted with a key made from the code, so other devices on the network cannot read them. While Show Sync is on, the primary computer accepts connections on every network it is joined to, so use a code others cannot guess.
Share Script in a Browser
When you start sharing, Rotulus serves a page from your computer. People you give the link and the watch code can open it in a web browser and follow the script, the runlist, where it is being read and how long it is expected to take. People you also give the edit code can type changes, which come back to your computer. Everything goes directly between your computer and their browsers, never through our servers or any internet service, and it stops when you press Stop Sharing or close Rotulus.
The code is needed to open the script. The script, the runlist, the reading position, the expected time and the edits are encrypted, and only a device that knows the code can read them. The page itself is delivered without encryption, so on a network you don't trust, someone able to tamper with network traffic could alter the page. Use your own network for sensitive scripts. While sharing is on, the page can be reached from every network your computer is joined to. A viewer's browser keeps the code, and whether the page shows the script or its timing, for that browser tab, and remembers the text size the viewer picks.
Google Docs you link
If you import a Google Doc or link a script to one, Rotulus downloads that document from Google as a Word file. For a document shared by link, it does so:
- when you import it, and when you review a newer version;
- every 5 minutes while the linked script is open in Rotulus, to see whether it changed, except while you present (to stop this, unlink the document or close the script);
- when you choose File → Pull Latest from Source;
- every 10 seconds while you present, only if you turn on "Apply source changes live while presenting" in Preferences.
Rotulus does not sign in to Google and never sees your Google password. The download works the way a web browser's does: it goes to docs.google.com and to the other Google addresses Google sends it on to, and Google receives what any web request carries: your computer's IP address, the document's address, an identification of the program making the request (which normally names your operating system and the versions of Rotulus and of the browser engine it is built on) and your system language. Rotulus makes these downloads in a separate session that it keeps only in memory, so it saves no cookie from Google, and any cookie Google sets is gone when Rotulus closes. Nothing goes to us or through us.
If a document turns out not to be shared by link, Rotulus opens it in your own web browser instead, where you may already be signed in to Google, and picks up the Word file your browser downloads. It looks for the file in your Downloads folder, the folder of the script (and of the script open on screen, if that is a different one), the last folder you saved to and your default save folder: it moves the file out of your Downloads folder, or copies it if it lands in one of the others. Google handles these requests under the Google Privacy Policy.
Automatic error reports
Error reports are off until you turn them on. Rotulus asks you when it starts, until you answer, and you can change your answer at any time in Preferences → General → Send error reports. The change takes effect at once.
When reports are on, Rotulus sends one only when something goes wrong: for example an error in the Rotulus window, a window that stops unexpectedly, a file that could not be saved, or a backup copy that could not be made before a file was overwritten. Nothing is sent while Rotulus works normally. Rotulus never shows anything on screen or pauses while it sends a report. If you are offline, the report waits in the settings folder until you are back online.
A report contains only:
- the error: its message, when it happened, where in Rotulus's program code it happened and which part of Rotulus caught it (for a file that could not be saved, or a backup copy that could not be made, only which kind of save or backup failed and the system's error code, for example that the file was in use; for a window that stopped unexpectedly, the reason and exit code the system gave);
- the Rotulus version, and whether it is a beta or a regular release;
- the operating system, its version and its architecture (such as x64 or ARM);
- the error-report ID (a random ID, see the table under "The app: what stays on your computer"), so we can tell whether one computer hit an error many times or many computers hit it once;
- whether Rotulus was editing or presenting when the error happened, and its earlier switches between editing and presenting, each with its time;
- the Show Sync states recorded before the error, each a single word such as off or connected, with its time (none if Show Sync was not used);
- the report's own technical details: an ID for the report, its severity, the name and version of the error-reporting software that sent it, and the programming platform that software runs on (always "node"; this is not your operating system).
Reports leave out the other details that error-reporting software often adds, such as the processor, memory, screen, graphics cards, and the language and region setting.
Rotulus is built to remove file and folder paths, file names, your user name and your computer name before a report is sent, and to leave out your script text and your license details. It cannot catch everything: an error message could, rarely, quote a few words of your script or part of a file name, and a user or computer name shorter than three characters is not removed. A report never contains a memory dump of the program.
Every report reaches Sentry over the internet, so Sentry receives your computer's IP address with it. We have set Sentry not to store IP addresses. Sentry still uses the address to estimate an approximate location, such as the country, and may keep that location with the report.
Reports are processed for us by Sentry (Functional Software, Inc.), an error-monitoring service, under its data processing agreement with us, in its United States data region. We use Sentry's Developer plan, on which Sentry keeps each report for 30 days. Sentry's own scrubbing of sensitive data on its servers is also turned on. If we change plans, we will update this policy first. See the Sentry Privacy Policy.
If you turn reports off while some are still waiting to be sent, Rotulus deletes them. Clear Local Data, with "Crash log and unsent error reports" ticked, deletes them too.
Update and license check
Rotulus checks, about once a day, for a newer version and for withdrawn License Keys.
- When your computer is online, about once a day, never within 20 hours of the last check, Rotulus downloads a small file from rotulus.io. When a check is due, it runs shortly after Rotulus starts; a check that gets no answer is tried again later. The file lists the latest version of Rotulus and the license numbers of withdrawn keys, each with a reason code, such as "replaced", "leaked" or "other", and never a name or email address. A license number does not tell anyone who you are (unless they also hold the key itself, which carries the name it was issued to); only our private records link it to a person. The file is public: anyone who asks rotulus.io for it can read it, and a withdrawn license number stays on it while any version of Rotulus that could accept the key is still supported. We sign the file, so Rotulus can tell that it came from us.
- Rotulus compares the file with its own version and with your key, on your computer. The request carries no License Key, no name, no email address and nothing from your scripts or settings. Like any request to a website, it shows your computer's IP address and a short identification, the name Rotulus and its version number, which also tells the server which version is asking. Amazon, which hosts rotulus.io for us, handles it like a visit to the website (see "The website"). The check is not limited by country. Rotulus keeps what the check found in its license check record (see "The app: what stays on your computer").
- If a newer version is out, Rotulus shows a note in edit mode with a link to the download page. It does not download or install an update by itself; you install updates yourself.
- If the file shows that your key has been withdrawn, presenting, playback, Show Sync and sharing in a browser stop working with that key the next time Rotulus starts. A key is withdrawn, for example, after a refund, after a payment dispute that is not decided in our favor, when a license moves to someone else, when we replace a lost key, or when a key has become public. If the computer had a valid key in the last 3 days, a lost key we replaced, or one that became public, keeps working there for 3 days, with a banner, so that you have time to enter a new key. The old key of a license that moved to someone else does not. The check never stops a show that is running.
- If the check fails, for example because you are offline or because the file is not available, Rotulus shows nothing and carries on. It does not need the internet to present.
- The check is on by default. You can turn it off in Preferences. Rotulus then makes no such request, and a withdrawn key is refused only by a later version of Rotulus that carries its license number in its own list.
Your License Key
Your License Key contains the name and email address it was issued to, the edition, the number of computers and its dates. Rotulus shows the name in Help → About Rotulus. Rotulus checks the key on your computer and does not send it to us or anyone else to check it. Rotulus also compares it, on your computer, with the list of withdrawn keys described under "Update and license check".
The website
Hosting. rotulus.io is hosted by Amazon Web Services: the pages are stored in Amazon S3 and delivered through Amazon CloudFront. Like any website host, Amazon receives the information every web request carries (your IP address, the page you ask for, your browser's identification and the page that sent you there) and uses it to deliver the page. We have not turned on Amazon's access logs for the website (Amazon S3 and Amazon CloudFront), so we have no log of visits to read. The same goes for the update and license check that Rotulus makes (see "Update and license check"): Amazon handles each check like a page request, and we have no log of it. Amazon may keep its own operating records, as its privacy notice describes. The download page and the installers are intended for visitors in the United States. Every other page, and the update and license check, are delivered the same way to every country.
No cookies, no analytics, no outside requests. Our pages set no cookies and run no analytics. They load their fonts and every other file from rotulus.io itself, so visiting a page sends nothing to any company other than Amazon. If you pick light or dark mode with the theme button, your browser remembers the choice in its local storage under the name rotulus-theme. It stays in your browser and is never sent to us. Going back to the system setting removes it, and you can also clear it with your browser's site data.
Links to other companies. Once licenses are on sale, the Buy button will be a plain link to Stripe's checkout page. The demo page links to our page on Zoho Bookings. Our pages load no code from Stripe or Zoho. When you follow such a link, you are on that company's site, and its own policy applies there as well as this one.
Do Not Track and Global Privacy Control. We do not track visitors across websites, and we do not sell personal information or use it for targeted advertising, so there is nothing for a Do Not Track or Global Privacy Control signal to switch off. The site works the same way whether or not your browser sends one. Apart from Amazon, which delivers the pages for us, no company receives information about your visit, and none collects it across websites. Once licenses are on sale, Stripe will collect information on its own checkout page under its own policy, including through cookies, and will use it for its own purposes, such as preventing fraud.
The forms on rotulus.io are described under "Writing to us, the beta and demos".
Buying a license
Licenses are not on sale yet. When they are, this section applies. We will sell Rotulus licenses only to customers in the United States, through Stripe. In this policy, "the United States" means the 50 states, the District of Columbia, US territories and APO/FPO addresses.
Checkout. The Buy button will take you to a checkout page run by Stripe, Inc. Stripe will ask for your email address, your card details, your billing address and the name the license is issued to (for an Organization License, the organization's name and how many keys you want), with the email address of the person or organization the license is issued to, which is yours unless you enter another. For a Show Pass, it will also ask for the start date you choose. Stripe may screen each payment for fraud. We will check that an order comes from the United States; an order that does not will get no key and will be refunded in full, unless US law requires us to hold the payment. Stripe may also collect information about your device and connection, including through cookies, to help prevent fraud, and it may keep what you type into its checkout page even if you do not finish. Stripe processes the payment for us. It also uses this information for its own purposes, such as preventing fraud and loss and meeting its legal duties, as an independent company under the Stripe Privacy Policy. Stripe may email you a receipt for us.
Quotes and invoices. An organization can ask us by email for a written quote. For 10 or more keys, or to pay a quote, we may send a Stripe invoice instead of the checkout page: we give Stripe the name, email address and organization you gave us, and you pay the invoice through Stripe before we issue any key. We keep your request and our quote with our emails.
What we receive. We will never see or receive your full card number. Stripe will show us each payment: your name, email address and billing address, the name and email address the license is issued to, the amount, any tax, the date, the payment's status, Stripe's reference numbers, and that you accepted our Terms of Sale. If Stripe shows us the card's brand, last four digits or country, we may see those too. We will use the billing address, and the card's country if Stripe shows it, to confirm that the order comes from the United States and to note the US state of the sale. Our own records of a purchase hold only what is listed under "Our records" below, so they keep the state of the sale but not your billing address or card details. A written quote you ask for keeps the address on it, with our emails (see "Quotes and invoices").
Checks before we send a key. Before we issue any key, including a free Trial Key, beta key or Tester License, we check the person or organization it is issued to, and anyone who pays for it, against the US government's restricted-party lists (its Consolidated Screening List), which name people and companies that US export and sanctions rules restrict. We search the list on the government's website, trade.gov, so the names and organizations we look up reach that site. We note the result with the sale, with the Trial Key record (see "Trial Keys") or with a beta tester's beta-key record or completion record (see "The beta"). A listed party gets no key, and any payment for that key is refunded in full, unless US law requires us to hold it. If we cannot accept an order for another reason, we refund it in full.
Our records. We keep two records of each purchase:
- a transaction record: the buyer's name, what was bought (the license and the number of keys), the order number, the date, the amount, any tax, the US state of the sale, whether it was refunded or disputed, Stripe's reference numbers, the versions of the Terms of Sale and the End User License Agreement you accepted, and the result of the screening check;
- a license record: the name and email address the license is issued to, the organization (if any), the license number, the edition (Personal or Organization; Annual, Lifetime, Show Pass or Tester License), the number of computers, the key's dates (when it was issued, and when it starts and ends; a Lifetime License key has no end date, so its record holds the end of its Update Period instead), whether the key has been withdrawn, and a copy of the key.
We keep these records in our Stripe account and on our own computer, with its backups. Our backups are kept offline and encrypted. When we delete or reduce a record, older backup copies keep it until they are overwritten, within 90 days. The emails we send you about your purchase, such as the one with your License Key, also stay in our mailbox. We use the records to deliver and re-send keys, to send the reminders described under "Emails from us", to answer refund requests and payment disputes, to work out a credit you ask for (such as Show Pass spending credited toward a license, or what you paid in the last 12 months credited toward a Lifetime License), and to keep our sales and tax records. Tester Licenses, which we give free to beta testers who complete the beta, have a license record too. The free beta keys we give testers during the beta have their own record (see "The beta"). How long we keep each record is under "How long we keep it".
Trial Keys. Once licenses are on sale, you can ask for a free Trial Key, which works for 14 days, by email to support@rotulus.io. We ask for your name and email address and, if you choose, your organization. We never ask for payment details. We use what you give us to check the request (Trial Keys are only for people who live in the United States and are 18 or older, which we take from what you tell us, and we check names against the Consolidated Screening List as we do for a purchase), to issue the key in your name and email it to you, and to keep to one Trial Key per person and per organization. To keep to that rule, we keep a record of each Trial Key (the name, email address and organization, the license number, its dates, a copy of the key and the result of the screening check), with the emails about it, for 2 years after the key ends, or less if you ask us to delete it. Then we delete the emails and remove the name, email address, organization, copy of the key and screening result from the record. We keep the license number, the kind of key, its dates and any withdrawal of the key. Asking for a Trial Key does not put you on any news list.
Your key by email. We email your key within one business day of payment, usually the same day. We send it to the licensee's email address you gave at checkout, which is yours unless you entered another. If you entered another, you chose at checkout whether we send the key there or to you. If you lose it, we aim to re-send it within one business day to the email address on file. If you can no longer use that address, write to support@rotulus.io: once you prove the order (for example with your Stripe receipt), we can move the key to a new address, and the key it replaces is withdrawn.
Refunds and disputes. If you get a refund, or a payment for a key is returned to the payer through a dispute or chargeback that is not decided in our favor, we mark the key as withdrawn and keep that with the transaction record. We also note an open dispute with the transaction record. We also withdraw a key that we replace (for example when we move a lost key to a new address), the old key of a license that moves to someone else (we issue a key in the new name), and a key that has become public. A renewal or an Update Year does not withdraw the key you already have. We may also withdraw a key on the other grounds the End User License Agreement gives. Later versions of Rotulus may refuse a withdrawn key. For that, each version of Rotulus carries a list of withdrawn license numbers, and its update and license check reads the newest list (license numbers with the reason for each withdrawal, never a name or email address). To answer a payment dispute, we may give Stripe the records of your purchase.
Discount requests. If you ask for a school, nonprofit or house-of-worship discount, we ask for the organization's name and a document showing its status, and we keep a short note of what we checked.
Writing to us, the beta and demos
If you email us, we keep your message and anything you attach (for example a log file, a screenshot or a sample script) in our mailbox. Please don't send a client's confidential script unless you have permission to share it, and please don't send health information. We use what you send to answer you and to keep a record of your request. We keep emails to support@rotulus.io and privacy@rotulus.io, and our replies, for 3 years. The emails that send you a License Key stay with the license record, emails about a Trial Key stay with the Trial Key record, and emails about the beta or a demo follow the rules for the beta and for demos below. Our mailboxes (support@, privacy@, beta@ and demo@rotulus.io) are hosted by Proton AG, a Swiss company. If you paste the text from Help → About Rotulus → Copy Diagnostics, it includes the path of your settings folder, which usually contains your user name on that computer.
The support, beta and survey forms
The support form asks for your name and email address, whether your request is about a show running now or in the next 24 hours, a topic and your message. If you choose, it also takes your Rotulus version, whether you use Windows or Mac, and one file of up to 3 MB, such as a crash log or a screenshot. The form passes what you send to a small program we run on Amazon Web Services. The program turns it into one email to support@rotulus.io, sent through Amazon's email service (Amazon SES) in the United States. The email holds every field, the attached file with its name, a request number and the time. Our replies go to the email address you gave.
The beta application form asks for your name and email address, your company (or that you are freelance), your role, how many live shows you prompt a month, the prompter software you use now, whether you use Windows, Mac or both, whether you can test with two computers, a description of a typical show (up to 2,000 characters) and, if you choose, how you heard about Rotulus. The same program emails every answer, with a request number, the time and what happened with Zoho (see "The email to us" below), to beta@rotulus.io through Amazon SES. When the connection to Zoho is switched on and the checks under "When an email address also makes a Zoho record" pass, the program also sends your answers to Zoho CRM, the customer database we use (from Zoho Corporation), where they are kept as one record (a Lead) under your email address. If Zoho has no record with your email address, the program creates one with all your answers. If it has one already, for example because you applied before or answered the demo survey, the program changes only the answer fields that the beta form alone fills: how many live shows you prompt a month, your prompter software, Windows or Mac, whether you can test with two computers and, if you gave one, how you heard about Rotulus, which replaces what was there. It changes nothing else on that record: your name, company, role and description of a typical show reach us only in the email. We send Zoho no network address and no cookie. If the connection to Zoho is off, skipped or fails, your application still reaches us by email. If both deliveries fail, the form shows you beta@rotulus.io so you can email your application instead.
The demo survey is for people who have seen a demo. Its only link is in the email we send after the demo; the page is not in the site's menus or sitemap, and it asks search engines not to list it. It asks 13 questions: your role, how many live shows you prompt a month, the prompter software you use now, whether you use Windows or Mac, what you would consider a fair price for Rotulus (and whether you think of it as a one-time, yearly or per-show price), which features matter most to you and one that is missing, what worries you about switching and what would stop you, how likely you are to switch within 6 months, what you would need to see before using Rotulus on a real show, who decides on prompter software and whether you would buy for yourself or through your company, which license shape suits you, and anything else. Every question is optional; the form needs at least one answer, and you can stay anonymous, because your name and email address are optional too. Below them is an unchecked box, "You may email me about my answers". Written answers are limited in length (at most 2,000 characters). The form passes your answers to the same program as the other two forms. The program turns them into one email to demo@rotulus.io, sent through Amazon SES in the United States. The email holds every answer and, if you gave them, your name and email address, which is also the reply address.
If you give an email address, the program also puts your answers in Zoho CRM whenever the checks under "When an email address also makes a Zoho record" pass, whether or not you tick the box. The box decides only whether we write to you about your answers; it does not decide whether a Zoho record is made. When the checks pass, the program looks in Zoho CRM for a record (a Lead) with your email address. If one exists, for example because you applied for the beta, the program changes only three survey fields on it: your answer on how likely you are to switch, your answer on price (cut to 255 characters) and a field holding all your answers, whose first line says whether you ticked the box. It changes nothing else on that record, not the name. If none exists, the program creates one with your name (or "Survey respondent" if you gave none), the company "Not given" and the same three fields. A survey with no email address never goes to Zoho. We send Zoho no network address and no cookie. If the connection to Zoho fails, your answers still reach us by email, and if the email fails, they still reach Zoho. If both fail, the form shows you demo@rotulus.io so you can email your answers instead.
When an email address also makes a Zoho record. For a beta application, and for a survey that includes an email address, the program writes to Zoho CRM only if all of these are true:
- the connection to Zoho is switched on;
- your browser sent the proof-of-work code described below, stamped by your device's clock within a day of ours, and the code has not been used before;
- the same email address has not already had a Zoho write from the same form in the same 6-hour period of the UTC day (the beta and the survey count apart, and a period counts as used as soon as a request with a valid code reaches this check, even if something later stops the write);
- the form's daily limit on Zoho writes, counted in UTC, has not been reached (the beta and the survey each have their own limit, which we set in the program and may change); it counts the requests that passed the checks above, not only the writes that succeeded;
- the request is not already slow: the Zoho step is skipped if the request has already taken too long when the step starts, or again just before the first call to Zoho; and
- the program could reach its counter table (see "What the program keeps").
If any of these is not true, your application or answers still reach us by email, you see the same "received" answer (unless the email also fails; then the form shows the mailbox address, as above), and Zoho is not called. The email to us then says "Zoho CRM: skipped" with the reason, "Zoho CRM: not configured" if the connection to Zoho is off, or, for a survey without an email address, "Zoho CRM: not sent (no email given)". When the connection to Zoho is on, a beta application, or a survey with an email address, that passes the form's checks and the limits on requests is never answered faster than a minimum reply time, whether or not Zoho is written, so that the time it takes does not show whether an address is already in Zoho.
The proof-of-work code. While you fill in the beta form or the survey, your browser works out a small code and sends it with your answers. It is the result of a short calculation, usually well under a second of your device's processor, and it holds only the time on your device's clock and a counter: no cookie, no identifier and nothing about you. Each code works once. Its only purpose is to make it costly for a program to fill the form thousands of times and write to our customer database. If your browser cannot make the code in time, it sends your answers without it: they still reach us by email, and only the Zoho record is skipped. For a request that reaches the Zoho step, the program keeps a one-way hash of the code, marked to expire 48 hours later (see "What the program keeps"), and nothing else about it; the code is not logged, not emailed and not sent to Zoho. The support form sends no code.
The email to us. Free text that you type (the support message, the typical show of a beta application and the written answers of the survey) appears in the email with "> " at the start of every line, so that nothing you type can pass for one of our own lines. The quoting removes nothing; the program only takes invisible control and formatting characters out of what you type. One-line fields such as your name are not quoted. The same quoted text goes into the survey-answers field in Zoho. An email that has a Reply-To address says that it is the one typed on the form and has not been verified. The beta and survey emails also carry a line "Zoho CRM:" that says accepted, failed, not configured, not sent (no email given) or skipped with the reason; and the email of a beta application that updated an existing Zoho record says that the name, company, role and typical show were not written to Zoho and are in the email.
What the program keeps. Apart from the few fixed choices its logs record (see "Logs and alerts"), it does not store your answers, your message, your name, your email address, your network address or any file you attach. To limit abuse it keeps counters in a table at Amazon (Amazon DynamoDB, in the same US region as the rest of the program). A counter is a label and a number. Some labels are one-way hashes made from your network address or from your email address. A hash is not the address itself, but these are made without a secret key or a salt, so anyone who has the table and knows or guesses an address can compute its label and look for it; we therefore treat these labels as personal information. The counters are:
- From your network address, for each form: how many requests come from one sender in an hour (five are allowed) and, for the beta and the survey, in a day (ten are allowed). The label is a hash of the hour or day and the sender's address, and for the beta and the survey also of the form; for an IPv6 address the sender is its first 56 bits (the size of block a home or office normally gets), or its first 64 bits for the support form. An hourly counter is marked to expire 1 to 2 hours after your request, a daily one 24 to 48 hours after it.
- From your email address, for the beta and the survey, only for a request that reaches the Zoho step: a counter whose label is a hash of your email address in lower case and of the 6-hour period of your request (the day, in UTC, is split into four periods starting at midnight, 6 a.m., noon and 6 p.m.), so that one address causes at most one Zoho write per form in each period. The hash is unsalted and has no secret key: anyone with the table and an address can compute the label for a period and see whether that address used that form in it. It is marked to expire 6 to 12 hours after your request.
- From the proof-of-work code: a hash of the form and the code, which stops a code being used twice. It is made from a clock reading and a counter, not from anything about you. It is marked to expire 48 hours after use.
- Counters that hold only a form and an hour or day: the limits on requests to each form as a whole, per hour and per day, and on Zoho writes per day. They hold no personal information.
Amazon deletes a counter in the background after it expires, typically within a few days but with no fixed deadline, so a counter can stay in the table for some time after the times above. If the table cannot be reached, the program skips the limits on requests, so the form still works, and it does not write to Zoho.
Logs and alerts. The program keeps technical logs for 30 days: a request number, which form was used, the outcome and its status code, how long it took, the topic and show choice (support), the role and Windows or Mac choice (beta), or your answer on how likely you are to switch (one of five fixed words) and whether you gave an email address, yes or no (survey), whether each delivery worked, how many calls were made to Zoho (one or two) and Zoho's response code, whether Zoho was written or skipped and, if skipped, which of six fixed reasons applied (no proof-of-work code, code already used, same address in the same 6-hour period, the day's limit on Zoho writes, request too slow, or counter table out of reach), why a request was refused for too many requests or because a form-wide limit was reached, why a request was rejected as automated (if it was), and the name of any error, including that the counter table could not be reached. Amazon adds its standard lines with the request number, running time and memory used. The logs never hold the text you typed, your name, email address, file or network address, and never the proof-of-work code or any of the hashes described above; the only survey answer a log holds is that one choice about switching. A request that looks automated (a hidden field filled in, sent faster than a person could, or sent without the page's own timing) is dropped: nothing is sent, and only the log line above is kept. If a delivery fails, the program emails us an alert with the request number, the form, the topic and show choice or which delivery failed, the error name and the time, and none of your message, survey answers, name, email address or file. When a form-wide limit is reached, or the day's limit on Zoho writes, it also emails us an "Abuse ceiling reached" alert, normally at most one every 30 minutes, with the form, which limit was reached, a request number and the time, and no address, answer or name.
When a limit is reached. A sender over the hourly or daily limit is told "Too many requests from this connection", and when a form-wide limit is reached the form says "We are receiving a lot of requests right now. Please try again later" with the address of that form's mailbox. Such a request is sent neither to our mailbox nor to Zoho. The support form has no daily or form-wide limit: only the five requests an hour for one sender.
Emailing support@rotulus.io, beta@rotulus.io or demo@rotulus.io directly works too; the forms are not required.
The beta
The closed beta has not started. It is planned to run from November 2026 through December 31, 2026, its last day, unless we extend it; we will announce a new last day at rotulus.io and tell testers by email. It is open to people aged 18 or older who live in the United States; we take your age and where you live from what you tell us. Before we send a tester a build, the tester accepts a Beta Test Agreement by email.
- If we don't offer you a place, we delete your application from Zoho CRM (and from Zoho's Recycle Bin, which otherwise keeps deleted records for 60 days) and from our beta mailbox after we tell you our decision, unless you asked to hear from us about Rotulus. Then we keep only your name, email address and that request. Zoho's audit log can keep a note of the deleted record, with its name, for as long as Zoho keeps that log.
- If you join, we keep your application during the beta and for 90 days after it ends, so we can confirm who completed it and issue Tester Licenses. Then we delete it the same way, from Zoho's Recycle Bin too (which otherwise keeps deleted records for 60 days). If you asked to hear from us about Rotulus, we keep only your name, email address and that request. Zoho's audit log can keep a note of the deleted record, with its name, for as long as Zoho keeps that log.
- When you accept the Beta Test Agreement by email, we keep a record of it: your name, the email address you replied from, the version you accepted and a copy of the exact text we sent you, when we sent it and when you replied, and your reply, saved with its full email headers (the technical lines that show where and when it was sent, including its message ID). We keep the same record when you accept a new version of the agreement or a Testimonial Release.
- Your beta key. After you accept the Beta Test Agreement, and before we email you a free beta key with the download link, we check you against the Consolidated Screening List (see "Buying a license"). We keep a record of the key with the record of your acceptance: the name and email address it is issued to, its license number, the date we issued it and its last day, whether it has been withdrawn, a copy of the key and the result of the screening check. If we extend the beta and send you a new beta key, we add it to the same record.
- Once you have done your show or rehearsal and booked your feedback call, we keep a completion record: the date of your real show or full rehearsal with a short description of it (no client names), when you booked your feedback call and its date, your answer about recording when you booked it, whether the call was recorded, when we wrote our notes and when the recording was deleted, when we confirmed your show or rehearsal and your booking, when we confirmed that you completed the beta (or that the call was not held in time and we withdrew your Tester License), the result of the screening check we make before we issue your Tester License (see "Buying a license"), and your Tester License's number, issue date, end date and value (the price of the same license on the day we issue it).
- Beta builds. A tester receives the download link for a beta build by email after accepting the Beta Test Agreement. Like any download, it shows the downloader's IP address and what any web request carries to the company that hosts the file. If that company is not Amazon (see "The website"), we will name it in this policy before the first link is sent.
- Public posts. During the beta, every two weeks, we look at public posts about Rotulus, so that we can ask a tester to add the disclosure the Beta Test Agreement asks for. We note when and where we looked, a link to each post we find and the tester who posted it, whether the disclosure was there, and what we did about it.
- A Tester License is issued in your name or, if your employer does not allow you to accept it, to your employer as an Organization License. We keep the same license record as for any license (see "Buying a license").
How long we keep the acceptance record, the completion record and the notes of public posts is under "How long we keep it".
Feedback calls
Completing the beta includes a feedback call of about 20 minutes on Zoom. The call is required; recording it is not. You book the call on our Zoho Bookings page. What you enter there (for example your name, email address, the time you pick and your answer about recording) goes to Zoho, which handles it for us, and to Google Calendar, which we connect to Zoho Bookings.
We record a feedback call only if you agree, and we record it on our own computer, not in Zoom's cloud. We do not record demo calls. When you book, we ask whether you agree to a recording (on the booking page, or by email). If you say no, we do not record your call. Whenever a call is recorded, Zoom also shows everyone that recording is on, and we ask for consent again at the start of the call. You can ask us to stop recording at any time and still complete the beta. We keep the booking, with your answer about recording, until the recording is deleted, or until we have written our notes if the call was not recorded.
We use a recording only to write our notes, and we do not share it. We quote from a recording, or use a clip of it, only with your written permission in a Testimonial Release. We save the recording only on our own computer, in offline encrypted storage and never in a synced folder, and we delete it within 60 days of the call. Zoom's cloud holds no recording of the call. The only exception is a clip you allow us to keep in a Testimonial Release. A transcript made from a recording is treated the same way. Recordings are not processed by AI tools.
Our notes from the call carry your name during the beta and for 90 days after it ends. After that, we keep only feedback that does not name you. Zoom carries the call for us and handles it under the Zoom Privacy Statement.
Testimonials
Testers are welcome to talk about Rotulus in public. We publish a tester's words, name or picture only with that tester's separate written permission, and always with a note next to it: "Rotulus beta tester; testers receive a free license", or, once that tester's own license has been issued, "Rotulus beta tester; received a free Tester License". That permission is a Testimonial Release or, to repost or quote one of the tester's own public posts, a short written OK by email for that post. A Testimonial Release lasts 2 years; before it ends, we may ask you by email to confirm it for 2 more years, and if you don't confirm it, we stop using the testimonial as if you had withdrawn it. You can withdraw your permission for future use at any time by writing to support@rotulus.io. Within 14 days we then remove the testimonial from rotulus.io, from our own social media posts and from our slides, and delete any clip of your feedback call. We keep the Testimonial Release or the OK, the record of your acceptance and any email withdrawing it after we stop using the testimonial, so that we can show we had your permission (see "How long we keep it").
Booking a demo
The demo page links to our booking page on Zoho Bookings. What you enter there (for example your name, email address and the time you pick) goes to Zoho, which handles it for us, and to Google Calendar, which we connect to Zoho Bookings. It does not pass through rotulus.io. Emailing demo@rotulus.io works too. The demo itself is a video call on Zoom, which carries it for us. We do not record demo calls. We keep a booking, its calendar entry and the emails about it for 90 days after the demo. Then we delete the calendar entry and the emails, and cancel the booking in Zoho Bookings, which keeps its own record as Zoho's policy describes. After the demo we email you a link to the optional demo survey (see "The support, beta and survey forms").
Emails from us
We email you about your purchase, your License Key, your license (for example reminders 30, 7 and 1 day before an Annual License ends), your requests, the beta, your demo (including the link to the demo survey) and changes to our terms or this policy. We do not send news email yet. If we start, we will send news about Rotulus, such as new versions and offers, only to people who ask for it, through a box or request that says so. Every news email will carry our postal address and say how to unsubscribe, and when you unsubscribe, we will delete your address from that list.
Who receives your information
We do not sell personal information, we do not use it for targeted advertising, and we do not share it with advertisers. We share it only as this policy describes:
| Company | What it does for us | What it receives | Its privacy policy |
|---|---|---|---|
| Stripe, Inc. | Will take payments and send invoices, and may screen payments for fraud, once licenses are on sale. Stripe also uses payment information for its own purposes, such as preventing fraud | What you enter at checkout or on an invoice, your card and billing address, and information about your device and connection | Stripe Privacy Policy |
| Amazon Web Services, Inc. | Hosts rotulus.io, including the file that the update and license check downloads, runs the form program and sends its emails | Website requests and update and license checks, form contents on their way to our mailboxes, and the program's logs and counters (some counters are one-way hashes of a network address or, for the beta and the survey, an email address) | AWS Privacy Notice |
| Proton AG | Hosts our email | Emails you send us, the emails our forms create, the emails we send you, and their attachments | Proton Privacy Policy |
| Zoho Corporation | Keeps beta applications and demo-survey answers (a survey only when an email address is given, and both only when the checks under "The support, beta and survey forms" pass) in Zoho CRM, and runs our booking pages for demos and feedback calls (Zoho Bookings) | Your email address and beta answers (for a new record, all of them with your name; for an existing one, only the answer fields the beta form fills), your email address and demo-survey answers if you give an email address (with your name, if you gave one, for a new record), and what you enter when you book | Zoho Privacy Policy |
| Functional Software, Inc. (Sentry) | Receives error reports, only if you turn them on | Error reports as described above, with your IP address | Sentry Privacy Policy |
| Zoom Communications, Inc. | Carries demo calls and feedback calls with beta testers; it holds no recording of them | The call and the name you join with | Zoom Privacy Statement |
| Google LLC (Google Calendar) | Holds the calendar connected to our Zoho Bookings pages | The details of a demo or feedback-call booking that Zoho Bookings passes on: your name, email address, the time and your answers on the booking form | Google Privacy Policy |
Google appears in two ways. When you link a Google Doc, your computer asks Google for it directly (see "Google Docs you link"); Google is not our service provider for that. Google Calendar is the calendar connected to our Zoho Bookings pages: through Zoho Bookings' calendar connection it receives the details of a demo or feedback-call booking that Zoho Bookings passes on: your name, email address, the time and your answers on the booking form. Google handles both under the Google Privacy Policy.
We also share information:
- with the people and computers you choose, when you use Show Sync or Share Script in a Browser;
- with Google Calendar, the calendar connected to our Zoho Bookings pages (Google Privacy Policy), for demo and feedback-call bookings;
- with the US government's screening-list search on trade.gov, for the names and organizations we check (see "Buying a license");
- with our professional advisers, such as an accountant or attorney, when they need it to advise us;
- when the law requires it, for example to answer a valid court order;
- with a company that takes over Rotulus, as described under "Who we are and what this policy covers".
Nevada residents: we do not sell covered information. You may still send a request not to sell to privacy@rotulus.io.
How long we keep it
What stays on your computer is in the table under "The app: what stays on your computer". For everything else:
| Information | How long we keep it |
|---|---|
| Transaction record of a purchase, with the result of the screening check | 10 years from the purchase |
| License record, with the copy of your key and the emails that sent it to you | While the license can be used or re-sent. If you ask us to delete it, we delete those emails too, remove the name, email address, organization and copy of the key from the record, and can no longer re-send your key. We keep the license number, the kind of key, its dates and any withdrawal of the key; the transaction record stays |
| Trial Key record, with the emails about it | 2 years after the key ends, or until you ask us to delete it if that is sooner. Then we delete the emails and remove the name, email address, organization, copy of the key and screening result from the record; we keep the license number, the kind of key, its dates and any withdrawal of the key |
| A withdrawn license number, with its reason code, in the public list at rotulus.io and in the list each released version of Rotulus carries | While any version of Rotulus that could accept the key is still supported |
| Discount-request note | With the transaction record |
| Payment records held by Stripe | As the Stripe Privacy Policy says |
| Emails to support@rotulus.io and privacy@rotulus.io, our replies, support-form requests and written quotes, with attachments (the emails that send a License Key stay with the license record, and emails about a Trial Key with the Trial Key record) | 3 years after we receive or send them |
| Form program logs | 30 days |
| Form counters (see "What the program keeps") | Marked to expire: counters from your network address 1 to 2 hours (hourly) or 24 to 48 hours (daily) after your request; the counter from your email address 6 to 12 hours; the proof-of-work counter 48 hours after use; form-wide counters up to 2 days. Amazon's automatic expiry then removes them, typically within a few days but with no fixed deadline |
| Beta application, if we don't offer you a place, with the matching emails to beta@rotulus.io | Deleted after we tell you our decision, from Zoho CRM (and from Zoho's Recycle Bin, which otherwise keeps deleted records for 60 days) and from the beta mailbox, unless you asked to hear from us; then only your name, email address and that request. Zoho's audit log can keep a note of the deleted record, with its name, for as long as Zoho keeps that log. |
| Beta application, if you join, with the matching emails to beta@rotulus.io | During the beta and for 90 days after it ends; if you asked to hear from us, then only your name, email address and that request |
| Record of your acceptance of the Beta Test Agreement or a new version of it, with your beta-key record; your completion record; our notes of public posts | As long as the agreement could matter to you or to us, for example in a disagreement about it, and no longer than 6 years after the beta ends |
| A Testimonial Release or a written OK to repost, with the record of your acceptance and any email withdrawing it | While we use the testimonial, and after its last use for as long as we may need to show that we had your permission, and no longer than 6 years after its last use |
| Booking for a feedback call, with your answer about recording | Until the recording is deleted, or until we have written our notes if the call was not recorded |
| Feedback-call recording, and any transcript of it | Deleted from our own computer within 60 days of the call (Zoom's cloud holds no recording). A clip you allow us to keep in a Testimonial Release is kept while we use the testimonial |
| A testimonial and any clip | While we use the testimonial; if you withdraw your permission, we remove it within 14 days |
| Our notes from a feedback call | With your name: during the beta and for 90 days after it ends. After that, only feedback that does not name you |
| Demo booking, its calendar entry and the emails about it | 90 days after the demo; then we delete the calendar entry and the emails and cancel the booking in Zoho Bookings, which keeps its own record as Zoho's policy describes |
| Demo survey answers: the email to demo@rotulus.io and, if you gave an email address, the survey fields in your Zoho CRM record | 90 days after the demo (answers we cannot tie to a demo: 90 days after we receive them), then deleted: the email, the survey fields of a record that also holds a beta application, and a record the survey created, which we also delete from Zoho's Recycle Bin, which otherwise keeps deleted records for 60 days. Zoho's audit log can keep a note of the deleted record, with its name, for as long as Zoho keeps that log. If you ticked "You may email me about my answers", we then keep only your name, email address and that request |
| Error reports at Sentry | 30 days |
| Your address on a news list, if we keep one | Until you unsubscribe; then we delete it from the list |
Your choices and rights
You can ask us to show you, correct or delete the information we hold about you: your purchase, license and Trial Key records, your emails and form requests, your beta records, your demo booking and your demo survey answers. Write to privacy@rotulus.io. We confirm a request by replying to the email address we have on file, and we answer within 30 days. When we delete a record from Zoho CRM at your request, we also delete it from Zoho's Recycle Bin, which otherwise keeps deleted records for 60 days. Zoho's audit log can keep a note of the deleted record, with its name, for as long as Zoho keeps that log.
Some information we cannot delete on request. We keep the transaction record of a purchase for the period in "How long we keep it", because we keep sales records for tax and legal reasons. If we delete your license record, we remove the name, email address, organization and copy of your key from it, and we can no longer re-send your License Key, so keep a copy of it. We keep the license number, the kind of key, its dates and any withdrawal of the key, none of which is a name or email address. A withdrawn license number also stays in the public list described under "Update and license check", and in the list each released version of Rotulus carries, which we cannot recall.
Information on your own computer is in your hands; see "Removing this information". You can also turn error reports off at any time in Preferences → General and turn the update and license check off in Preferences.
Depending on where you live, you may have more rights under local law. Write to us and we will respond as that law requires.
Children
Rotulus and rotulus.io are made for professional use and are not directed to children under 13. We do not knowingly collect personal information from children under 13. If we learn that we have, we will delete it. To buy a license, to get a Trial Key or to join the beta, you must be 18 or older. If you buy for an organization, you must also be able to bind it. Someone under 18 may use Rotulus when a parent or guardian, or the organization they use it for, accepts the End User License Agreement for them.
Where your information is handled
We are in the United States. For now, we sell licenses only to customers in the United States, and we issue Trial Keys and run the beta only for people who live in the United States. Amazon Web Services handles our forms and their emails in its US East region, and delivers the website, including the file that the update and license check downloads, through Amazon CloudFront, from its locations in North America and Europe. Sentry keeps error reports in its United States data region. Zoho keeps beta applications and demo-survey answers in its United States data center; Zoho's own policy says it may also process data in other countries through its group companies, and Zoho handles bookings as its own policy describes. Our mailboxes are hosted by Proton AG, a Swiss company. Stripe, Zoom and Google handle information as their own policies describe, which can include other countries. If you contact us from outside the United States, we handle your information the same way.
Changes to this policy
The top of this page shows the version and the date it takes effect, and the change log below lists every version. If we make a material change, such as collecting new information or using it in a new way, we will post the new version here and email license holders and beta testers before it takes effect. We will not use information we already hold in a materially different way without your consent.
In Rotulus itself, a new feature that sends information off your computer will be off until you turn it on, as error reports, Google Docs links, Show Sync and Share Script in a Browser are. The one exception is the update and license check, described under "Update and license check": it is on by default, and you can turn it off. If we ever add to what it sends, we will first say so here and email license holders and beta testers, and the same switch will turn it off.
Contact
Privacy requests and questions about this policy: privacy@rotulus.io. Support and legal notices: support@rotulus.io. Mail: Mathusek Technologies LLC, 10939 N Alpine Hwy PMB 119, Highland, UT 84003.
Change log
- Version 1.0, effective 2026-10-12: first published version.