Privacy statement
Praxis Percussion is operated by Backwerd Rimshot, LLC. This statement describes, plainly and completely, what the service collects and why. The separate, free Backwerd Rhythm Shop apps are account-free and store progress locally in your browser unless you deliberately use a clearly identified hosted mode.
Check the workspace label. Every organization workspace is labeled. A workspace marked fictional-records-only — the default for every organization — accepts fictional example records ONLY: do not enter real student names, identifiers, or records there, including in free-text fields.
Real student records exist only by recorded decision. An organization may hold real student records only after a deliberate, recorded, audited activation decision by its authorizing party. Its workspace is then labeled "Real student records." The server enforces this boundary per organization; no setting or button turns it on.
Children under 13
Praxis Percussion does not knowingly hold records about children under 13. An organization may be activated for real records only while it attests that the records it keeps here are about students 13 or older. A teacher whose studio also serves younger students keeps those students' records out of Praxis Percussion entirely. Records about a child under 13 will not be accepted until a verifiable parental-consent path exists and is approved; if we learn such a record was entered without that path, we will delete it through our documented erasure procedure.
What we collect from adults
- Account information: your name and email address, used to sign you in with single-use email links and to operate your account.
- Director access requests: the information you submit on the request form — your name, email, role, organization name and type, location, site descriptions, grade bands, estimated student count, under-13 status, and intended use.
- Workspace content you create: organizations, sites, class names, paths, invitations to other adults, and library, inventory, and repertoire records. In a fictional-records-only workspace this content must not include real student information.
- Studio billing, if a teacher keeps it: lesson rates,
invoices and their lines, payments the teacher records as received (an
amount, a date, and a free-text method such as "check 1042"), and a billing
contact for a student's lessons — the paying adult's name, email address,
and an optional note used as an address line. In a private studio that
paying adult is usually a parent, who may have no account here and may never
visit the site.
We never collect or process a payment instrument. There is no card handling, no stored card or bank detail, no payout, and no platform fee; a request carrying a card number, a CVV, an account or routing number, or a payment-processor token is refused outright rather than quietly dropped. Billing records are erased with the student's records, including the billing contact. - Operational records: essential session cookies, security and audit logs, and short-lived infrastructure logs (such as IP addresses and request metadata) used to keep the service working and secure.
- Praxis Tech Workspace records: adult operational information an independent technician enters for a service relationship: client organizations, adult client contacts, service offerings and availability, booking requests, confirmed services, private notes, selected adult recap recipients, and invoice-record status. Praxis Tech is not for student-private information. A public Tech profile is optional and shows only the provider information, services, and availability the provider chooses to publish; client organizations, private notes, invoice records, and unpublished recaps are not public. A recap is shared only when the provider deliberately publishes it to a selected adult recipient. Praxis Tech does not currently provide client logins or a client portal.
- Public-site analytics: on a limited set of public marketing and sign-up pages, we use Google Analytics to understand aggregate traffic, referral sources, and which public pages lead to a sign-up. The tag is not loaded on learner pages, authenticated workspaces, or operational tools. It records the page path without its query string and is configured not to store an Analytics cookie in your browser. We do not use it for advertising, cross-site targeting, or to identify a person.
Student records in an activated workspace
An organization activated for real records holds only what a teacher enters and the service derives from it: a learner name or label, an internal identifier, class or program membership, coursework attempts and evidence, teacher verification and retention events, lesson scheduling and teaching records the teacher maintains, and limited equipment-custody history.
We do not ask for and do not need: student email addresses, school-issued IDs, birth dates, student contact details, the student's own home address, precise location, health or disability information, discipline records, a student's or family's financial circumstances — household income, fee assistance, or free-and-reduced-price meal status — photos, audio, video, biometric data, advertising identifiers, or social-media data. In a private-studio workspace, students do not sign in and receive no accounts or credentials.
One item on that list needs a plain qualification rather than a flat denial, because a flat denial would be wrong. A private studio's teacher may bill for lessons, and where they do we hold what "Studio billing" above describes: rates, invoice amounts, recorded payments, and the paying adult's name, email, and optional address note. That adult is usually the student's parent, so in practice we may hold a household's contact details even though we hold none for the student. What we do not hold, for anybody, is a payment instrument. We would rather say this here than let a reader infer from the words "financial information" that a studio's invoices do not exist.
How we use it
To operate your account and workspace, deliver sign-in links and invitations you request, create the records and exports your organization authorizes, respond when you contact us, and keep the service secure. That is the whole list. We do not sell personal information, show ads, share information for marketing, build unrelated commercial profiles, or train general-purpose AI models on covered records.
Who else touches the data
Praxis Percussion runs on Cloudflare (hosting, database, security challenges, and email delivery), primarily in the United States. Cloudflare processes data on our behalf under its customer data protection agreement. We monitor Cloudflare's published list of sub-processors for changes.
Other service providers can receive limited information only to provide the feature you choose: Google LLC receives limited technical and page-visit information through Google Analytics on the public pages described above; Google LLC or Microsoft Corporation receives calendar information only when a teacher in your organization deliberately connects a Studio calendar; and Stripe, Inc. processes Praxis Tech membership billing when you choose to provide a payment method. Praxis does not store Tech membership card details. Google Analytics does not receive learner records, workspace content, or URL query strings from Praxis. Apart from those, no third party receives your information, except when disclosure is legally required or necessary to protect the service and its users.
Calendar connections you choose
This section describes Studio calendar connections, not Praxis Tech. A teacher can connect a Google or Microsoft calendar so their lesson schedule appears alongside the rest of their week. This is off until they connect it, it is per teacher and per organization, and nothing reaches either company before that. When it is connected, Google LLC or Microsoft Corporation receives what we write. Praxis Tech does not currently offer an internal calendar, Google/Outlook calendar connections, or other external calendar integrations.
What we write is a lesson time, how long it lasts, and who the lesson is with. We never write notes, observations, assignments, evidence, reports, or amounts.
Who the lesson is with depends on the kind of organization, and the difference is deliberate:
- A school or district. The event carries no student name and no student label at all — just a time. Once an event is written into a calendar we do not control, our deletion and erasure procedures cannot reach it, and sharing that calendar copies it further. An institution should not be putting its students' names somewhere it cannot later remove them.
- A private studio or independent teacher. The event carries the student's name as the teacher entered it. This is a teacher's own calendar, in their own account, about students they already teach and whose names they already write on a lesson sheet — and a calendar full of codes is one they cannot read. The same limitation applies: we cannot remove those events later, and the teacher should know that.
- A workspace using fictional example records. The event carries the example label. Nothing real is disclosed.
We ask each provider for the narrowest permission it offers — access limited to a calendar our application creates — so we can neither read nor change anything already in that teacher's own calendar. We create a separate calendar and write only there.
We are deliberate about this because a calendar entry, once written, leaves our reach: our deletion and erasure procedures cannot remove it, and sharing that calendar copies it further. That is exactly why no student name goes into one. A teacher can disconnect at any time from their schedule screen, without contacting us; disconnecting destroys the stored connection credential immediately and asks the provider to revoke it.
Praxis Percussion's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use that information only to provide the calendar feature you asked for; we do not transfer it except as necessary to provide that feature, to comply with applicable law, or in a merger or acquisition with the notice and consent required; we do not use it for advertising; and we do not allow humans to read it except with your explicit consent for specific data, for security purposes, to comply with applicable law, or where the information is aggregated and de-identified.
Staff and support access today
Praxis follows an operating policy of no routine staff access to another teacher's student records. Today that policy depends on operator discipline. There is not yet a product control that requires the organization's approval, limits support access to a stated purpose and expiration, or separately logs each support-access session.
The owner-operator can technically reach production systems when necessary to operate, secure, restore, or erase the service. This is a disclosed limitation, not a claim that routine access is technically impossible. The separate Platform Operations console does not display student records; a future delegated support-access workflow will require its own reviewed decision and implementation.
Security
We use encrypted transit and provider-managed encryption at rest, hashed credentials, secure HTTP-only session cookies, time-limited sessions, per-organization and per-capability access controls, append-only audit events, rate limiting, and the server-enforced per-organization release gate described above. No system is guaranteed secure, and we describe our controls honestly rather than claim certifications we do not hold.
Where we hold a credential to another service on your behalf — today only a calendar connection a teacher chose to make — we protect it beyond the storage encryption above. We encrypt it separately with a key kept outside the database that we can rotate without interrupting the service, we exclude it by design from logs, exports, error messages, and our own interfaces, and we destroy it outright rather than mark it deleted when a teacher disconnects, when their access to the organization ends, or when the organization is deleted. We record that a credential was destroyed; we never record its value.
Retention and deletion
We keep information only while it is needed for its purpose, agreement, security, or a legal obligation. Sessions and sign-in links expire automatically. Two different things are called deletion here and we keep them apart: ordinary deletion in the product closes access immediately and keeps governed history, so a teacher's past decision can still be explained; erasure is a separate, documented procedure that physically removes records. Erasure cannot be performed as a single action: it requires a preview of exactly which records would be removed, a distinct approval step against that preview, and a permanent record of who did each part. See "Review status" below for who performs those steps today. The periods below are erasure periods.
How long we keep the main categories:
- Student records — coursework, evidence, and teacher decisions. Kept for as long as the organization's agreement with us lasts. When that agreement ends, or when the teaching relationship ends, or on request — whichever comes first — we erase them within 60 days. If the organization asks for an export first, we provide it before erasing.
- Audit and security records. Kept for 13 months from the date of the event, so that a full school year plus the summer can be reconstructed if something is disputed or investigated. These records are how we can tell you what happened to an account, so we do not delete them when an individual record is erased — instead we remove the identifying information from them at that point, and the record itself expires on the 13-month clock.
- Backups. Our hosting provider keeps recovery copies on a rolling schedule that we do not control and cannot edit individually. Erased information stays in those copies until the cycle expires, and then it is gone. We state the current window in our data-processing agreements rather than here, so that a change of hosting plan does not silently make this page wrong. We would rather describe backup expiry accurately than claim immediate deletion from recovery media.
Where Texas Education Code §32.156 applies, a district-directed deletion is completed no later than 60 days after the request unless the agreement sets a shorter period, which it may. Evaluation and staging environments may still be reset as the product evolves; activated production workspaces are not treated as disposable.
Access, correction, and deletion requests
To access, correct, or delete your information, email taylor@backwerdrimshot.com. When we hold education records for a school, requests should normally go through that school so it can verify authority and direct us; for a private studio, requests go to the studio's teacher or to us directly. Deletion requests are honored except where a record must be retained for security or legal reasons, and we will tell you if that applies. We will not use a rights request as a reason to collect unnecessary identity documents.
A deletion request is an email. You do not need an account, a login, a portal, or a support ticket, and you do not need your organization's agreement with us to still be in effect. If your school or studio has stopped using Praxis Percussion and you want the records gone, email the address above and we will erase them within the period stated above. We mention this because losing access to a system is a common reason people never manage to get their data deleted from it.
Review status
This statement is maintained directly by the owner-operator and has not yet had independent legal review. The owner first proceeded for the owner's own studio, then recorded a narrow decision permitting two named, non-operator founding-teacher studios to seek individual activation for teacher-maintained records about students age 13 or older. Each still requires a written pilot agreement, an accepted organization-specific decision, and the reviewed one-way activation procedure. This is not a general public activation rule.
Schools, districts, learner accounts, and all records about children under 13 remain outside that decision. The approved under-13 product direction is direct guardian notice and authorization through a future guardian-consent workflow; no under-13 record is accepted until that workflow, its notice and verification method, and the applicable legal review are complete.
The same is true of erasure, and we would rather say so than let the word "approval" imply more than it currently means. The erasure procedure requires a preview, a separate approval against that preview, and an execution step, and the system refuses to let one account perform two of them. Today all three steps are performed by the owner-operator using separate accounts, so the approval is a check against mistakes and a permanent record of what was done — it is not an independent second person reviewing the decision. A genuinely independent reviewer arrives at the same point independent legal review does: before any school or third-party organization is activated. Until then, the 60-day period above is a commitment we can and do meet; the word "approval" simply describes a control, not an outside opinion.
Changes
If this statement changes, the new version will be posted here with a new version number and effective date. Material changes involving student information, purposes, disclosure, or retention follow the applicable agreement and a notice process before taking effect.