Effective September 28, 2026
A plain-English summary for orientation only. It is not part of the agreement — the numbered sections below are what govern.
LazShift ("LazShift", "we", "us") provides shift-scheduling software to businesses ("Customers") and the people they invite ("Users"). This policy explains what personal information the Service handles, why, who it reaches, how long we keep it, and what you can ask us to do with it.
It covers the LazShift application at lazshift.com and the emails, text messages, and push notifications the Service sends. It forms part of our Terms of Service.
Two different relationships run through this policy, and which one applies changes what we can do for you.
The practical consequence is in section 10: if your employer added you, most changes to your record are theirs to make, and we will point you to them rather than act behind them.
Nearly all of it is provided directly by you or by your employer. We do not buy personal information, and we do not collect it from data brokers, social networks, or advertising networks.
| Category | What it includes | Where it comes from |
|---|---|---|
| Account and profile | Name, email address, phone number, profile photo if one is added, role, employment type, hire date, last day of work, whether the record is active, and — if a manager records it, to apply limits on a minor's hours — date of birth. | The Customer, or the User editing their own profile. A User who signs in with Google also shares the name and email address on that Google account. |
| Pay | Hourly pay rate, and the estimates derived from it. | The Customer. |
| Scheduling | Shifts, availability, standing shifts, shift preferences, hour and rest limits, time-off requests, approvals and balances, shift-swap and pool requests, day notes. | Customers and Users. |
| Notifications | Per-category email, text, and push preferences; browser push subscriptions; the notifications we have sent you. | The User's own settings. |
| Business settings | Business and location names, logo, brand colour, operating hours, shift types, pay-period settings, and — if a manager sets them — approximate coordinates for a location's weather forecast and a state for payroll tax estimates. | Administrators. |
| Billing | Subscription status, plan, seat count, trial dates, and Stripe's reference identifiers. Card details go to Stripe directly and never reach our systems. | Stripe, and the Administrator who subscribes. |
| Account security | Authentication credentials in hashed form, the time of each sign-in, and audit records of privileged actions — including a manager changing someone's sign-in details, a data export, and our own staff's administrative actions. | Generated by the Service. |
| Calendar sync | If enabled, a private feed token tied to that User's account. | Generated by the Service at the User's request. |
| Technical | Server and error logs — including IP address, browser type, and timestamps — kept to operate, debug, and secure the Service. | Generated automatically. |
| Support | What you tell us when you contact us, and our replies. | You. |
We do not track individual users' locations — the only location in the Service is an approximate one for a business site, used to fetch a weather forecast. We do not collect government identifiers, payment card numbers, biometric data, health or medical information, precise geolocation, or racial, religious, political, or sexual-orientation data, and the Terms of Service prohibit entering them. We collect no sensitive personal information as California defines it, and we therefore have nothing to limit the use of.
We use personal information to:
We do not use personal information for advertising, profiling for marketing, or automated decisions that produce legal or similarly significant effects about a person. The AI feature in section 5 produces written suggestions for a manager to weigh; it decides nothing on its own.
Access inside the app is role-based, and enforced at the database level so one business can never read another's data.
If you would rather your colleagues not have your personal mobile number, give your employer a work number, or ask them to leave the phone field empty — notifications will fall back to email.
Our staff do not access a Customer's data except to provide support that has been requested, to investigate a security or billing problem, or where the law requires it. The Service includes an administrative "view as" capability for that purpose; every use of it is recorded in an audit log, along with other privileged administrative actions.
We may disclose information if we are legally compelled to, to enforce our Terms, or to protect the rights, safety, or property of LazShift, our customers, or the public. Where we are permitted to notify the affected Customer first, we will. If LazShift is involved in a merger, acquisition, or sale of assets, data may transfer as part of it, subject to this policy; we will give notice before it becomes subject to a materially different one.
LazShift offers an optional AI scheduling assistant. It is switched off unless an Administrator enables it for a location, and it runs only when a manager asks for analysis after building a schedule.
When it runs, we send Anthropic the facts behind that run: employees' first names and last initials (enough for a manager to tell two people called Sarah apart, and no more), roles, employment types, hour minimums and caps, marked availability, stated shift and day preferences, dates of approved and pending time off, standing shifts, start and last-work dates, and the coverage figures our scheduler computed. We do not send pay rates, email addresses, phone numbers, or any other contact information.
Anthropic processes the request to return the analysis and does not use it to train its models. Neither do we. Turning the feature off stops the transfer entirely — the Service then shows the numbers-only summary its own scheduler produced.
We protect personal information with measures appropriate to its sensitivity, including:
No system is perfectly secure, and we cannot guarantee absolute security. If a breach affects your personal information, we will notify affected Customers and, where required, regulators and individuals, without undue delay and within the timeframes the law sets. Report a suspected vulnerability or compromise to support@lazshift.com; our security page sets out what to expect when you do, and states plainly which assurances we do not yet have.
We keep personal information only as long as it serves the purpose it was collected for.
Your employer controls your record, and we handle it on their instructions. Ask them first: most changes — correcting your name, phone number, hire date, or pay rate, adjusting availability, or removing your record — an Administrator can make immediately in the app, and you can edit much of your own profile and notification settings yourself. An Administrator can also download a copy of the account's data at any time. If you contact us directly with a request about employer-controlled data, we will refer you to them and let them know you asked, unless the law requires us to act ourselves.
If you are a California resident, the CCPA as amended by the CPRA gives you the right to:
These rights apply to employment-related information as well as to consumer information.
Residents of states with comprehensive privacy laws — including Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, and others as they take effect — have comparable rights to access, correct, delete, and obtain a copy of their personal information, and to opt out of targeted advertising, sale, and profiling, none of which we do. If we decline a request, you may appeal by replying to our decision; if the appeal is denied, you may complain to your state attorney general.
Email support@lazshift.com, telling us what you are asking for and the account or email address involved. We will verify your identity — usually by confirming control of the email address on the account, and asking for more only where the request is sensitive. We respond within 45 days, and may extend once by a further 45 days where the request is complex, telling you why. There is no charge unless a request is manifestly unfounded or excessive. An authorised agent may act for you with written permission we can verify.
LazShift is a workplace tool and is not directed to children. Whether someone is old enough to work, and on what terms, is for their employer under the law that applies to them, and a Customer that adds a minor is responsible for any consent that law requires. We handle a minor's information, including a date of birth used to apply limits on their hours, as Customer Data on the Customer's instructions, and we do not sell or share it. The Service is not directed to children under 13, and we do not knowingly collect personal information from them; if you believe a child under 13's information has been entered, contact us and we will delete it.
LazShift is operated from the United States, and personal information is stored and processed there. The Service is intended for businesses in the United States and is not offered to individuals in the European Economic Area, the United Kingdom, or Switzerland. If you use it from outside the United States, you understand that the information will be processed in the United States, where privacy law differs from your own.
We may update this policy as the Service changes. We will update the effective date above, and for material changes — a new category of information, a new purpose, or a new provider receiving personal information — we will notify Administrators by email or in the app before the change takes effect. Continued use afterwards is acceptance of the updated policy.
Questions about this policy, or a request about your personal information, go to support@lazshift.com. We will provide a mailing address for formal notices on request.