Privacy Policy

Effective date: October 18, 2026

Roots Playbook ("Roots Playbook", "we", "us") is a football play-design app, on the web at rootsplaybook.com and in our iOS app. It is provided by Akeem Jones, an individual based in Texas, United States.

This policy explains what information the app collects, how it is used and shared, how long it is kept, and the choices you have.

Contact: akeem.jones@ksr-media.com

1. Who Roots Playbook is for

Roots Playbook is a football play-design tool for coaches, players, parents and team staff. People of any age can use it. Roots Playbook is offered in the United States.

What you can do depends on how you use it:

• On your device, without an account (any age). Your plays stay on your device. Nothing about you is sent to us, apart from anonymous usage counts that you can turn off (section 3.7).
• Team View (any age). A coach can share a link or code that lets someone view the team's playbook. The viewer gives only a name. We ask for a first name or nickname, not a full name, and never for an email address or other contact details (section 3.4).
• An account (13 and older). An account uses your email address, so it is for people 13 and older. If you are under 13, please don't create an account. Everything else works without one.

Age checks in the iOS app. Where state law requires it (currently Texas), Apple confirms the age range of the person using the app and shares it with the app.

• If Apple tells us the person is under 13, the app doesn't offer account sign-in. Everything else keeps working.
• We use the age range only for that. We don't send it to our servers and we don't keep it. The app keeps only the time of the check.

2. Using the app without an account

You can use Roots Playbook without an account. The plays, formations and playbooks you make are then stored only on your device, in your browser's or the app's storage, and are not sent to us. The app may send anonymous usage counts, which contain none of your content and which you can turn off (section 3.7).

3. Information we collect

3.1 When you sign in

You can sign in with Google or with Apple. We do not offer passwords.

From the sign-in provider

• When you sign in, the provider gives our authentication service (Supabase) your email address and, if the provider shares it, your name.
• Apple may give us a private relay email address instead of your real one.
• Our authentication service also keeps an internal account identifier and basic details of the sign-in.

What we keep in your profile

• your email address;
• a display name you choose (2–60 characters), which is how your team sees you;
• a profile type you choose: Head Coach, Coach, Assistant Coach, Coordinator, Player, Parent, Team Staff or Other;
• when your profile was created and last updated.

Sign in with Apple. If you sign in with Apple, we keep Apple's refresh token for your sign-in, encrypted. We use it for one purpose only: to revoke your Sign in with Apple authorization with Apple when you delete your account.

3.2 When you sync or share a playbook

When you turn on sync for a playbook, add it to a team, or join a team, the playbook's content is sent to our servers so it can reach your other devices and your team.

Content

• Playbooks: names, team name, team colors and team logo. A logo may be a photo you take with your device's camera.
• Formations and plays: player positions, routes, motion, defensive assignments, play options, notes, and play and formation names.
• Player details you enter: for each player on a play, a position, a jersey number, a profile name of up to 40 characters (a first name, nickname or initials), and an optional short note.
  • Please don't enter players' full names, contact details or other personal information.
  • If you coach minors, enter only what your team needs to run its plays.

Records kept with that content

• Revision history: earlier versions of a play, who published each version, when, and a short description of what changed. Descriptions may mention a player's profile name.
• A change log: a record of each change sent to our servers, so that a change sent twice is applied only once.
• Who changed what: for each item, the account that last changed it, and an identifier and label for the device used. The label is the device type (for example "iPhone") or a name you typed.
• Who created each play: the account or Team View guest that first added it to the team. This decides what an Editor may do with the play (section 7). For plays added before we started recording this, we record a creator only where our records show it for certain; otherwise no creator is recorded.

3.3 Teams

When you are part of a team, we keep:

• your role (Owner, Admin, Editor or Viewer);
• who invited you;
• when you joined;
• when you were last active in the team.

Who sees what

• All team members see each member's display name, profile type, role, join date and last-active time.
• Owners and Admins also see members' email addresses.
• Team invitations are single-use links. We store only a scrambled (hashed) form of the link.

3.4 Team View guests (no account)

To view a playbook through a Team View link or code, a guest enters a name (2–60 characters). The app asks for a first name or nickname; please don't enter a full name.

What we keep about a guest

• the name;
• when the guest joined and when they were last seen;
• a scrambled (hashed) form of a credential tied to their device.

Who sees it. The coaches who manage the playbook see the guest's name, join time and last-seen time.

What we don't keep. We never store the guest's device key itself.

3.5 Live collaboration

While Owners, Admins and Editors of a team playbook edit at the same time, the app shares the following live with the others in that playbook:

• your display name and initials;
• whether you are on a phone, tablet or computer;
• which play you are viewing;
• what you are selecting or editing;
• a live preview of a drag you are making.

The app does not store this information. It disappears when you leave. Changes you save are stored as described in 3.2.

3.6 Technical information

Device identifiers. The app creates a random device identifier and stores it on your device. It is sent with the changes you sync, so that conflicting edits can be told apart.

IP addresses

• When someone uses a Team View link or code, we keep a scrambled (hashed) form of the IP address, to limit guessing of codes. These records are deleted once they are more than 2 days old, the next time a code is checked.
• When the app sends anonymous usage counts (section 3.7), we keep a scrambled (hashed) form of the IP address for up to 2 days, only to limit how much any one address can send.
• We do not use IP addresses to identify you or to find your location.

Hosting and service providers

• Our hosting and backend providers (section 5) receive the usual technical information with each request, such as IP address, browser or device type, and the address requested. They may keep it in their logs.
• Team View links include an access code in the web address, so the code can appear in our host's request logs.

Error logs. When something fails on our server, we log an error code and a short message, with personal information removed.

3.7 Anonymous usage analytics

Anonymous usage analytics. To improve Roots Playbook we count how the app is used — for example that a play was created, an animation was played or an export was made — with a random identifier made on your device. It is not linked to your account, contains nothing you write or draw (no play names, routes, notes or player names), and is never shared with or sold to anyone. There are no advertising or third-party analytics tools. You can turn it off at any time in Settings › Privacy, which also clears anything not yet sent.

What a count can include, besides the random identifier:

• what happened, such as a play created, an animation played, an export made or a feature used, and when;
• the kind of play, such as offense or defense and the field size, but never its name or content;
• the app version, the platform (iPhone, Android or web), the operating system's major version, and the region your device is set to (for example "US"), which is a setting and not your location;
• how long the app took to open, and when something failed, the kind of failure but never its details.

Your controls. Settings › Privacy has the switch, shows the start of your random identifier, and can Reset it to a new one. The first time you open a version of the app that sends these counts, it tells you before anything is sent.

Our website. When you arrive at rootsplaybook.com from a link tagged with a campaign (for example a partner's post), we add one to a daily count for that campaign. Nothing else about the visit is kept, and nothing is counted when your browser sends a Global Privacy Control signal.

3.8 What we do not collect

We do not collect:

• your precise or approximate location;
• your contacts;
• health or financial information;
• payment information;
• advertising identifiers.

We do not use third-party analytics or advertising tools, and we do not use cookies to track you.

Roots Playbook has no artificial-intelligence features, and your content is not processed by AI services.

4. How we use information

We use information only to provide and protect Roots Playbook:

• to sign you in;
• to sync your playbooks across your devices;
• to share playbooks with your team and with Team View guests;
• to run live collaboration;
• to keep history;
• to prevent abuse, such as code guessing;
• to fix problems;
• to understand, with anonymous usage counts, how the app is used so we can improve it (section 3.7);
• to respond to you.

We do not:

• sell personal information;
• share it for advertising;
• send marketing email.

If we change these purposes, we will update this policy first (section 12).

5. Who we share information with

Your team. Content you sync to a team is visible to that team according to each member's role, as described above.

Team View guests. Guests see the team's published plays, including the player details entered in them, and the team name and logo. They do not see member lists, email addresses, revision history, or the device labels recorded with changes.

Service providers who process information for us

• Supabase: authentication, database, server functions and live collaboration. Data is stored in the United States (Ohio).
• Netlify: hosting of rootsplaybook.com.
• Google and Apple: sign-in.
• Apple: distribution of the iOS app.

These providers process information only to provide their services to us, and their terms require them to protect it.

Legal reasons. We may disclose information if the law requires it, or to protect the rights, safety or security of our users or of the service.

Where information is processed. Information is stored and processed in the United States.

6. How long we keep information

We are putting the 30-, 90-, 180- and 365-day periods into effect in stages. Until automatic deletion runs for a type of record, that record is kept while the playbook is shared. The 90-day window for restoring deleted plays applies now.

Backups and provider logs. Our database provider does not keep restorable backups of our database on our current plan. Our providers keep their own request and system logs for limited periods under their own policies.

7. Deleting information and your account

Plays and playbooks. You can delete plays and playbooks in the app.

• Deleting a play in a team playbook removes it for the whole team.
• Who may delete: Owners and Admins may delete any play. Editors may delete only plays they created. If the team requires approval for changes, an Editor's deletion is a request until an Owner or Admin approves it.
• Owners and Admins can restore a deleted play from Recently Deleted for 90 days.
• If you edited a play on an offline device while someone else deleted it, your edits are kept on your device as a private copy. They are not put back on the team unless someone chooses to.

Exporting and copying plays. Owners and Admins, and anyone the team allows to export, may export or copy any of the team's plays. Other Editors may export or copy only the plays they created.

Leaving a team. Copies of the team's playbooks are removed from your devices the next time they sync. If you leave or are removed, the plays you created are kept on your device as your own private copy. Nobody else's plays are kept.

Team View guests. A guest can remove a shared playbook from their device. The team's coaches can disconnect a guest; the guest's record, including their name, is then deleted after 90 days (section 6). A guest can also email us to have their name removed sooner.

Deleting your account. Go to Profile → Account & Sign-In → Delete Account. Deletion happens right away. When you delete your account:

• Your profile and your sign-in are deleted.
• Playbooks you own:
  • In a team with another owner, your playbooks are handed over to that owner.
  • Teams where you are the only owner are deleted, along with their playbooks.
  • If a team you solely own holds another coach's playbook, deletion waits until you hand over ownership or that playbook is removed. The app explains this before you confirm.
• Edits that stay with teams. Changes you made to playbooks that stay with a team remain part of that team's playbooks and history, no longer linked to your name. Device labels and other identifiers attached to them are removed.
• Your devices. Information stored on your own devices is not deleted. Remove the app, or clear this site's data, to erase it.
• Sign in with Apple. If you signed in with Apple, we ask Apple to revoke your Sign in with Apple authorization. You can also remove Roots Playbook yourself in your Apple Account's Sign in with Apple settings.

8. Your choices and rights

Requests you can make. You can ask us for:

• access to the personal information we hold about you;
• a copy of it in a portable format;
• correction of it;
• deletion of it.

Email akeem.jones@ksr-media.com. We will respond within 30 days. We may need to confirm that a request comes from the account holder before acting on it.

Anonymous usage counts are not linked to you or your account, so we can't find them from your name or email. If you send us the identifier shown in Settings › Privacy, we will delete the counts sent under it.

Tools in the app

• You can turn anonymous usage analytics off, or reset its random identifier, in Settings › Privacy.
• You can correct your display name and profile type.
• You can export your playbooks as files.
• You can delete your account.

Withdrawing consent. You can stop sharing a playbook, leave a team, sign out, or delete your account at any time.

Do Not Track. Roots Playbook does not track you across other sites or apps, and no third party does so through Roots Playbook. Browser "Do Not Track" signals therefore don't change how the service works.

Marketing. We do not send marketing email.

9. Security

What we do

• Data is sent over encrypted connections (HTTPS).
• Our server checks access to synced data on every request, according to your role.
• Links, codes and device credentials are stored on our server only in scrambled (hashed) form.
• iOS: the app is built to block screenshots, screen recordings and the app-switcher preview, so playbooks can't easily be copied that way. It relies on how iOS works today, so it may not work in every situation, and it can't stop someone photographing the screen.

Limits. No way of storing or sending information is completely secure, and we can't guarantee absolute security.

If something goes wrong. If a breach affects your personal information, we will notify you and the authorities where the law requires.

10. Children and teens

People of any age can use Roots Playbook on their device and view a team's playbook with Team View. Accounts are for people 13 and older (section 1).

Children under 13. We do not knowingly collect personal information from children under 13, such as a full name, an email address or other contact details.

• Team View asks only for a first name or nickname. It also keeps a scrambled credential that lets the device open the playbook, and when the guest joined and was last seen. These are used only to run Team View.
• If you believe a child under 13 has given us personal information, for example by typing a full name, email us and we will delete it.
• Anonymous usage counts (section 3.7) use a random identifier only to understand and improve how the app works. They are never used to contact anyone, to build a profile, or for advertising, and a parent can turn them off in Settings › Privacy.
• A parent or guardian can ask us to review or delete information their child gave us by emailing the address above.

Defaults that protect everyone

• Nothing in the app is public.
• Sharing is limited to the teams and Team View guests a coach chooses.
• There is no advertising, no profiling and no sale of information.

Parents in Texas. Where state law requires it, Apple asks a parent or guardian to approve a minor's download, and the parent or guardian can withdraw that approval through Apple. Apple then stops the app from opening on the minor's device.

11. Coaches entering information about players

Coaches decide what to enter about players. Please enter only what your team needs to run its plays, and avoid full names, contact details or other personal information about players, especially minors. The app says this under the profile name field.

12. Changes to this policy

We will post changes on this page and update the effective date. If a change is material, we will also tell you in the app before it takes effect. Where state law requires it, we will also notify Apple of a significant change, and Apple may ask a minor's parent or guardian to approve it.

13. Contact

Akeem Jones · akeem.jones@ksr-media.com