PLAIN-LANGUAGE DATA SUMMARY

What EasyShiftPlan keeps, and what it does with it.

This page describes the product's current behavior so you can decide what information to enter. It is a practical summary, not a complete legal privacy notice.

For a first look, use the demo. It starts with sample data in a separate browser session. Avoid putting real employee details into a public demo.

Private workspaces

A signed-in workspace stores the information needed to build schedules, such as employee names, roles, availability, time off, staffing rules, schedules and any optional cost figures you enter. Exact wages are not required; a relative cost signal can be used instead. Employee email addresses are optional.

Files and AI interpretation

For a scheduling request, the AI may receive the text you type and relevant saved context such as employee names, roles, work-hour limits, availability, time off, shift setup and scheduling rules. Exact pay rates saved in employee records are left out of this context; the scheduling solver uses cost data on EasyShiftPlan's server. If you type pay details or include them in a file or image, that submitted content may still be sent for interpretation, so remove anything unnecessary first. Uploaded images are sent as image content when image-capable cloud parsing is used; text and spreadsheet files are extracted and the relevant content is sent to the parser. The original upload is not retained as a file. For review and troubleshooting, submitted or extracted text, the filename, structured interpretation and error details may be stored in encrypted audit fields; those audit records do not yet have a published deletion schedule. The parser follows server configuration: a cloud request may use DeepSeek and fall back to Gemini on quota or rate limits; if cloud parsing is unavailable, local fallback is text-only. The exact provider used for a request is shown in the admin audit record.

Anonymous demo

The demo uses an HTTP-only browser cookie to keep each visitor's sample workspace separate. The demo cookie expires after 24 hours. Basic traffic records can include the IP address, browser user-agent, page or endpoint, response status, referring site and campaign tags so the team can diagnose failures and understand how people find the product. These records are not shown to other visitors.

Product learning and improvement notes

The admin learning view summarizes first-party demo-session activity, AI outcomes and core API errors from records EasyShiftPlan already keeps. Per-action demo audit details used by this view are deleted after 180 days when the learning data is next read. Funnel percentages use one cohort of newly created demo sessions; AI and API rates count attempts or requests, not people, and may include signed-in use. The summary does not copy IP addresses, browser strings, employee details, wages, schedules, uploaded content or typed requests. Crawler detection is a browser-string heuristic and cannot verify a person. An administrator may add a sanitized summary of customer or manager feedback, then track a testable hypothesis, owner role and success measure. Improvement hypotheses and review notes are encrypted and admin-only; records are deleted 365 days after creation the next time the learning data is read. Do not include names, contact details or private information.

AI assistant connections

An MCP-compatible assistant can connect only after a signed-in manager approves the requested access and explicitly selects one or more store workspaces. The manager can review and disconnect approved assistants in Connection settings; after disconnection, the service rejects that assistant’s access token. The assistant may receive staff names, roles, availability, time off, rules and schedule context from only the selected stores as needed for the task; exact hourly pay rates are omitted, although a draft may include an aggregate cost estimate. Usage events are linked internally to the signed-in account for aggregate counts and include the assistant-client label, tool name, outcome and time. This separate usage view does not copy prompts, tool results, rosters or uploaded content, and records are removed after 180 days when the admin panel is next refreshed. General operational access logs may still record IP address, browser user-agent, endpoint and status. A separate, optional permission allows the assistant to send a generalized feedback note. Feedback is associated with the signed-in account and assistant-client label, encrypted, visible only to platform administrators, and removed after 180 days when the admin panel is next refreshed. The server rejects known employee names and contact details in feedback; do not include wage amounts, exact shift contents, uploaded text or private store details. An assistant cannot change saved settings, confirm or publish a schedule.

Public demo for AI assistants

No account is needed, and only fictional sample teams are used. One run_public_demo call accepts optional parameters, creates a fresh isolated sample workspace internally, generates and checks a draft, then discards that workspace. No workspace ID is returned or needed, and no schedule is saved or published. Demo instructions and generated schedules are returned to the calling assistant and are not stored in the demo workspace or MCP usage metrics. Aggregate tool and outcome counts and a daily count of natural-language demo requests may be recorded without their contents. Natural-language instructions and relevant fictional setup are sent to EasyShiftPlan’s configured scheduling parser, which may use a cloud AI provider; that provider’s privacy practices also apply. Standard operational access logs may separately include IP address, browser user-agent, endpoint and response status. Do not send real staff, customer or store information.

Contact and billing

If you submit the contact form, your name, email and any optional phone, store name or message are stored so the team can respond. The source or campaign label available from the link or referring site may also be attached to the request to understand how people find EasyShiftPlan. New contact requests are not linked to anonymous demo sessions by an IP-derived visitor code; older requests may still contain a pseudonymous visitor code from the previous setup. Billing choices and subscription events are recorded to operate checkout and understand which plan was selected. EasyShiftPlan does not keep a first-/last-visit campaign profile in browser storage. During a visit, limited source and campaign labels may be carried in same-site links and recorded when you start a demo, submit a contact request or select a plan. When someone clicks a plan, a random first-party browser identifier (not derived from an IP address) can connect that plan click with related billing events for up to 90 days, including after sign-in or checkout from the same browser. Billing funnel events are retained for 180 days. Submitted contact requests, including their source labels, do not yet have a published deletion schedule. Card details are entered in Stripe Checkout; EasyShiftPlan does not ask you to send card numbers by email.

What to avoid entering

  • Do not upload identity documents, bank details or unrelated personal conversations.
  • Use employee names only when needed; employee email is optional.
  • Use relative cost levels if you do not want to enter actual pay.
  • Check extracted text and rules before applying them to a schedule.

Retention and questions

The anonymous demo cookie expires after 24 hours. Access logs, billing attribution and funnel events have a 180-day limit; access logs are cleaned when a new access is recorded or an administrator opens the access-log view. Demo action details and MCP usage/feedback records are deleted after 180 days when their admin panel is next read, and product-improvement notes are deleted 365 days after creation when the learning data is next read. Other contact, workspace, demo-session and audit records do not yet have a published, product-wide deletion schedule. If you need information about a record or want to discuss a data request, contact [email protected]. We will review requests manually.

Daily public-site activity counts

EasyShiftPlan counts public demo-page visits, demo starts, plan or trial clicks, contact clicks and completed contact submissions as daily totals. This small reporting table stores only the UTC date, event category and count; counts older than 400 days are deleted when a new count is recorded or an administrator refreshes this report. The table does not store visitor IDs, IP addresses, browser strings, referrers or campaign tags. Separate operational access logs may still contain request details as described above, and automated traffic may be included in page-visit counts.

Need a clear answer before using real staff data?

Tell us what data you plan to use and what your store needs to retain. We will answer plainly before you move it into EasyShiftPlan.

Contact support →