May we use Google Ads cookies to learn which ads lead to new accounts? Google receives ad-click and signup information. We don't send your email or schedule details. Your choice won't affect your account. Privacy details

Skip to content

Privacy and school use

Last updated October 29, 2026.

Para Schedule is for adults organizing their own school workday. It is built to work without information about students. This page says what it stores, who can see it, and what you can do with it.

Before you enter student information

Your school or district decides what information about students may go into any tool, including this one. Check with them before you enter anything that identifies a student. Accepting this page is not that permission.

  • Para Schedule works without student names. Rooms, group labels such as Group B, and your own role are usually enough.
  • Subjects are labels and colors you choose for scheduling. The app never asks for a student's name, and a label can be as plain as a color or initials your school allows.
  • Initials are not the same as removing identifying information. A room, a time, and a distinctive assignment together can still point to one student.
  • The product has no fields for health, diagnosis, behavior, evaluations, or education records, and it does not accept attachments.
  • Keep notes short and about the work: where to be, what to prepare, who hands off to whom.

Para Schedule does not claim to meet any particular school, district, state, or federal requirement, and it is not approved by any school. A permitted-data policy will be published here after review. Until then, do not enter information that identifies a student.

What the product stores

Only what the product needs to work:

  • Your account: your email address, your password stored only as a one-way hash (the password itself is never kept), an optional display name, and your display and print preferences.
  • Sign-in sessions: a random token kept in a cookie in your browser. The server keeps only a hash of it, when it expires, and a short description of the browser that signed in. In the Para Schedule app the same token is kept in your phone's keychain or keystore instead of a cookie, and Sign out removes it.
  • Your schedule: its title and settings, the adult labels you type, duties (times, titles, places, group labels, roles, notes, handoffs), subjects (a label, a color, and a support level), teams, which adults are ready to support a subject, who is responsible for a duty, who covers a break, done marks on those relief steps, day types, changes for particular dates, times an adult is unavailable, saved versions and the copies made current from them, saved templates and duties, and the notes you add when you review a check.
  • Sharing: for each person you invite, their email address, which adults, dates, and details they may read, and when access ends or was revoked.
  • Product events: a short list of steps such as a schedule being made current, recorded with random ids and coded values only. Titles, labels, rooms, and notes are never part of them. Product measurement below lists exactly what is recorded and for how long.
  • Feedback you send: only what you type into Send feedback, stored apart from your schedule (see Feedback).
  • Plan records: which plan a schedule is on and, for Plus, the payment provider's subscription, invoice and refund references with their dates and amounts. Card details are entered only on the payment provider's pages and never reach Para Schedule.

When you import rows, the pasted text or file is read in your browser; only the rows you choose to add are sent and saved. The fictional sample on the demo runs entirely in your browser and is never saved.

Cookies and browser storage

  • One sign-in cookie, which scripts on the page cannot read. It ends when you sign out or when the session expires.
  • Your theme and text size may be remembered in this browser for convenience; your account keeps the real setting.
  • While you set up a schedule, your starting choice is kept in this browser tab until setup is done.
  • No ads are displayed in the product. Optional Google Ads measurement on the public website and signup flow is described below.
  • In the app (see Para Schedule on your phone), a PDF you make is written to the app's private storage until you share it, and removed when you sign out. The app records the same product events as the website, plus which platform and app version they came from; never a device identifier. You can delete your account from the app or the website (see Delete your account).
  • In this browser tab only, the site notes which public page you opened first and a general source (search, TikTok, a link, or direct) so that a new account can record how people find Para Schedule. The address you came from is not kept.
  • Page views on the public site are counted with cookieless Vercel Web Analytics once the owner turns it on. It never counts the app, shared views, or sign-in pages, and it does not identify you.

Product measurement

To learn which parts of Para Schedule help and which get in the way, the service records a small set of measurements. Each one is a coded value with random ids, never what is on your schedule.

What is recorded:

  • Steps in the product, as codes: for example a first duty added, a setup step finished, a copy made current, a change for a date, a day type saved, a template applied, or an operation that failed (with a reason code, never a message).
  • When the Today screen shows your current schedule (at most once per browser session and date), when a print preview opens, and when you ask the browser to print. A print request is recorded as an intent: Para Schedule cannot know whether a page printed.
  • How you arrived when you signed up: the first public page of that browser tab, a general source class (search, social, TikTok, a link, direct, or unknown), and a campaign code only when the link was one of Para Schedule's own registered campaign links. This note lives only in that browser tab and is used once, at sign-up. It is not a cookie, and a later visit is not linked to an earlier one.
  • A coarse device class: phone, tablet, desktop, or unknown.
  • Plan and payment facts from the verified payment records: a trial started, a first payment, a renewal, a refund, a scheduled cancellation, and the cancellation reason if you choose one in the billing portal. The portal's comment box is never read.

Never recorded: names, adult labels, duty titles, rooms, notes, group labels, or anything else on your schedule; web addresses, search terms, or the page you came from; your IP address or a device identifier. These first-party product measurements are separate from optional Google Ads measurement below. There is no third-party analytics in the native app.

How long it is kept:

  • Individual measurements: 90 days.
  • Milestones linked to your account (for example when your routine was first ready) and your sign-up source: 400 days.
  • Totals and rates that are not linked to any person: up to 24 months.
  • Feedback text: 180 days, or 30 days after it is resolved, whichever comes first.

Your switch: Settings, Account & data, Product measurement. It is on unless you turn it off. Off stops the measurements your browser reports (Today use, print previews, print requests), stops linking later milestones to your account, and stops feedback questions. Every feature keeps working either way. The steps the server records as part of running your account (sign-up, a copy made current, verified payments) continue, as they did before.

Only an administrator with a separate permission, who has also confirmed a one-time code sent to their own verified address, can see the reports, which show totals and rates and leave out internal and test accounts. Measurements are not sold and are not used for advertising.

Optional ad measurement on the website

If you choose Allow ad measurement, Google Ads can use cookies to help us understand which ads lead to new accounts. This is optional and separate from email tips and Product measurement. Declining does not change any product feature. Before you allow it, we do not load the Google Ads tag or send it signup events.

With your permission, the tag receives ad-click information, a public page address, and a signup event with a random, one-time reference used to prevent duplicate counts. Google also receives network information such as your IP address when your browser contacts its servers. We do not send your email, password, account id, workspace id, or schedule content in these events. Enhanced conversions and personalized advertising are turned off.

The tag runs on public website pages and the signup flow. It is not loaded in the native app or private schedule, sharing, sign-in, or account recovery pages. We honor Do Not Track and Global Privacy Control for this measurement. We remember your choice in this browser for up to 180 days and configure Google conversion cookies for up to 30 days.

You can change your choice with Ad measurement choices at the bottom of a public page. Turning it off stops future measurement and removes Google conversion cookies that this site can access; it does not remove information already received by Google. See how Google uses information from sites that use its services.

Feedback

  • Send feedback (Settings, Account & data) stores the topic you choose, your two optional answers, whether you allowed a reply, a coarse device class, and which part of the app you were in. It is stored apart from your schedule and is never copied into measurements, logs, emails, or exports. There are no attachments or screenshots.
  • Please do not include student names, private school information, or payment-card details.
  • Only if you tick “You may reply using my account email” can an administrator look up your account email, and each lookup is recorded. Replies come from a person, by email, when we can; there is no set response time.
  • The text is deleted after 180 days, or 30 days after it is resolved; an administrator can remove it sooner. At most five messages an hour are accepted from one account.

Who can see your schedule

  • You, when signed in to the account that owns the schedule.
  • People you invite by name, only after they sign in with the invited email address, and only the adults, dates, and details you chose, until access ends or you revoke it. They can read, never edit, and they never see drafts.
  • The people who run the service, when they need to operate or repair it.

Adding an adult label such as Casey gives that person nothing: a label is not an account. Schedule content is never sold, and it is not used for advertising.

Export, deletion, and retention

In the app, Settings, Account & data is where you download a full backup or a CSV of a date range, sign out, turn product measurement off, send feedback, and delete your schedule or your account.

  • Deleting a schedule removes it right away: its routine and every saved version, dated changes, day types, adult labels, subjects and teams, saved templates and duties, and everyone's viewer access.
  • Your account stays, so you can set up a new schedule. Files you downloaded and pages you printed are not affected.
  • Para Schedule keeps no separate backup copies of schedules. If the hosting provider keeps database backups, a deleted schedule can remain in them until they expire.
  • Deleting your account (Settings, Account & data) also deletes your sign-up source record, your milestones, and your daily-use records; removes your account and schedule ids from the remaining measurements; and removes the text of your feedback and its link to you. Only the fact that a random id was deleted is kept, so that id is never linked to anything again. Plan and payment records are kept for bookkeeping without a link to you.
  • Turning Product measurement off keeps what was already recorded until its period ends, but nothing new is linked to you. Deleting the account is how to remove what is linked to you now.
  • How long old versions, sign-in sessions, and host backups are kept has not been decided yet. This section will state each period once it is set, and Settings will say the same. Product measurement and feedback periods are listed above.

Security

  • Every saved schedule needs a signed-in owner, and every read and change is checked on the server.
  • Passwords are hashed, sign-in attempts are rate-limited, and sessions can be ended with Sign out, which matters on shared school devices.
  • Invitation links are not permission on their own; they open only for the invited account.

Still to be decided

  • The hosting provider and where the data is stored.
  • The retention periods for old versions, sign-in sessions, and host backups.
  • The permitted-data policy for student information.
  • A monitored contact address for privacy questions and requests.