Changelog

A history of changes to Sprooster's privacy policy and terms of service. Each document is published in two parts: the Mantelin Core Terms (Part A) and the Sprooster Schedule (Part B). The two parts version independently, per each document's preamble.

Core Privacy Terms v1.1, Part A (October 17, 2026). Section 18 now says which changes are not material: a change that adds no kind of Personal Data or Organization Data we collect, adds no use of it, and reduces no rights. Such a change takes effect on the date we publish it and is recorded here. The notice rules for individual users and Organizations apply only to material changes.
Sprooster Schedule v1.2, Part B (October 17, 2026). S9 said a recording hides all text. A recording now also shows the Product's own wording, such as button labels and headings, so we can see which control a person used. All other text stays hidden, with form entries and images, so no Organization Data appears in a recording. This change is not material under Section 18 and takes effect on publication.
Sprooster Schedule v1.1, Part B (October 12, 2026). S9 said session replay was not enabled. We may now record sessions with our product-analytics service to find and fix problems in the Product. Recordings hide all text, form entries and images, so no Organization Data appears in them, and they are deleted after 30 days. Because no Organization Data is recorded, this change does not alter our processor obligations under Section 3.
Sprooster Schedule v1.0, Part B (September 7, 2026). Corrected before launch. S2 said hire date and birthday were collected only where an administrator explicitly mapped those fields, which described the Google Workspace connector and not the Microsoft Entra or BambooHR ones, both of which collected them from every Organization. S2 now describes one switch per date, on by default, that an administrator can turn off for the whole workspace at any time. Turning one off stops the collection and deletes the dates already held. A Member can also keep themselves off the celebration display without changing what the Organization collects. The version number does not change, because the Product has no users and the Schedule has never governed anyone.
Sprooster ToS Schedule v1.0, Part B (September 6, 2026). Corrected before launch. An Organization can now build its chart in Sprooster without connecting a directory, so T2 prices plans on the number of people on the chart rather than on the size of a synced directory. Everyone on the chart counts however they got there, the count is taken when somebody adds or removes a person as well as at sync, and someone removed stops counting that day. The plan table also still held the ceilings that were raised on August 20, and now matches the published price list: Company covers up to 500 people and Business up to 1,500. T1 records that a chart can be built by hand, and T4 that a person you entered yourself is corrected in Sprooster rather than at a source. The version number does not change, because the Product has no users and the Schedule has never governed anyone.
Sprooster Schedule v1.0, Part B (September 6, 2026). Corrected before launch. S8 answered product-specific retention with "None". Removing a person from a chart now archives them and deletes the record at the end of a window the Organization's administrators choose, 30 to 90 days or up to a year on a paid plan, so S8 describes that. It keeps data for less time than Section 13, not more, and an archived person can be restored until the window closes. S1, S2 and S3 record that an Organization can enter its people directly instead of syncing them, and S5 prices a plan on the people on a chart rather than in a synced directory. The version number does not change, for the same reason as the ToS Schedule above.
Sub-processor list (September 6, 2026). Removed Clerk. Sign-in and account management now run on our own infrastructure, so no third party receives account credentials or session data. Sessions and accounts are stored in Supabase, which is already listed. No document version changes, because the Core Privacy Terms and the Sprooster Schedule both describe the sub-processor list as a living page (Section 7 and S4) rather than restating it.
Sub-processor list (August 16, 2026). Added Resend, which delivers transactional email such as sign-in codes. Resend receives the recipient's email address and the message we send; it never receives directory records. No document version changes, because the Core Privacy Terms and the Sprooster Schedule both describe the sub-processor list as a living page (Section 7 and S4) rather than restating it.
Core Terms of Service v1.0, Part A (August 3, 2026). Corrected before launch. The published copy was missing Section 20 (Copyright and repeat infringement), which names our designated agent for copyright reports, states the repeat-infringer policy, and gives the counter-notice procedure. Section 20 is part of the Core Terms and applies from the original effective date. The version number does not change, because the Product has no users and the document was never served without it in force.
Mantelin Definitions v1.0 (July 25, 2026). Initial publication of the shared Definitions, incorporated by reference into the Core Privacy Terms, the Core Terms of Service, and each Schedule.
Core Terms of Service v1.0, Part A (July 25, 2026). Initial publication of the Mantelin Core Terms of Service.
Sprooster ToS Schedule v1.0, Part B (July 25, 2026). Initial publication of the Sprooster Terms of Service Schedule, including the plan table and how directory size is measured (T2), billing, proration, tax and cancellation terms, and Stripe as the payment processor. T3 designates Early Access per individual feature rather than for the whole Product. T7 records that plan support levels are not response-time commitments.
Core Privacy Terms v1.0, Part A (July 25, 2026). Initial publication of the Mantelin Core Privacy Terms.
Sprooster Schedule v1.0, Part B (July 25, 2026). Initial publication of the Sprooster Schedule. S5 names Stripe as the payment processor and records that card details never reach Mantelin.