Privacy policy
Last updated November 1, 2026. EveShift is run by Web Landscapes LLC, a Florida company ("we"). This page covers eveshift.com, the demo, the free schedule maker, setup help, and the EveShift app.
This website, the demo and the schedule maker
- The site uses no analytics, no advertising and no third-party scripts. Fonts are served from our own domain.
- The demo runs in your browser. Nothing you do in it is sent to us.
- The schedule maker saves your schedule in your own browser (local storage). A share link carries the schedule after the "#" in the address, a part browsers don't send to servers. Clear it with the Clear button or your browser's site data.
- Our web host (Cloudflare) processes the technical data every website request carries, such as IP address and browser type, to deliver the page and protect it from abuse.
- The setup and contact forms open your own email app. We only get what you choose to send.
The EveShift app: what's stored
| Data | Why | Who in your team can see it |
|---|---|---|
| Your name, email and language | To sign you in and send you notices in your language | Your name: everyone on your team. Your email: you, and people who manage members |
| Password | To sign you in | Nobody. Stored only as a one-way hash (PBKDF2) |
| Authenticator secret, backup codes, passkeys | Two-step sign-in | Nobody. The secret is encrypted; backup codes are stored as hashes; passkeys store only a public key |
| Your role, skills and certifications (with expiry dates) | Coverage rules | Your team |
| An age band (14–15, 16–17) or a date of birth, only if a manager enters one; hourly or salaried | Reminders about minors' working hours, overtime and breaks | People who manage members |
| Clock punches: the time, the job, whether it was made offline, every change with who made it and why | Worked hours and timesheets | You, and roles that review or approve hours. Coworkers only if you turn on sharing your clock-ins |
| Location check at a punch, only where the location uses it and you agree: "inside" or "outside" and a distance rounded to 10 meters | To show a manager the punch was made at the workplace | You, and roles that review hours. We never store where you were |
| Your jobs and the shifts you add for them | Your own schedule and hours | Only you. A team sees only the shifts you work for that team |
| Pay settings: rates, salary, tips, deductions, W-4 choices, income goal | Your pay estimate | You. Encrypted at rest with a key tied to your account; our servers decrypt it only to show it to you. If a team gives a role permission to see hourly rates, people in that role see your rate for that team's job, every look is logged, and your account page shows who they are |
| Availability, preferences, time-off balances and shift notes | Building the schedule and tracking leave | Your balances: you and people who manage leave. Availability: you and people who build the schedule. Notes: the people on that shift |
| Shifts, requests, approvals and notes | The schedule | Your team, as their roles allow |
| Sign-in records (time, IP address, browser) and a history of changes | Security and accountability | Sign-in records: nobody in the app. Change history: roles with that permission |
Your own calendar
If you paste the link of your own calendar, we treat it carefully, because that link is like a password to your calendar:
- The link is encrypted when stored and is never shown back to anyone, you included. We don't write it to logs.
- Our server reads the calendar about once an hour, and when you press "Read it now". We read events from two weeks ago to three months ahead.
- You choose what is kept. Busy only (the default): we keep start and end times and drop titles, places, notes and attendees before saving anything. Busy with titles: we also keep event titles, shown to roles allowed to see them. Only me: we keep busy times, shown only to you and used only in checks you run yourself.
- Events marked "free" or cancelled are skipped.
- Remove the link and everything read from it is deleted at once. Switching from "titles" to "busy only" deletes the stored titles at once.
Calendar feed links we give you (to put your shifts in your phone's calendar) are secret too: we store only a fingerprint of each link, and you can turn a link off any time.
Location at clock-in
- EveShift asks for your phone's location only when you tap a clock button, at a location that turned the check on, after you agree. It never reads your location at other times or in the background.
- Your phone sends its position once, with the punch. EveShift compares it with the workplace, keeps the result (inside or outside) and a rounded distance, and drops the coordinates without storing them.
- You can say no. The punch still counts, and your manager sees that the location wasn't checked.
What EveShift staff can see
A few people at EveShift run the service and answer help requests. They sign in to a staff console with two-step sign-in, and every look and every action there is recorded in a log we keep. What they can see without anything from your team:
- Each team's name, when it was made, and its people: names, roles and email addresses.
- Each account's email address, name, language, time zone, when it was made and last signed in, whether it's suspended or being deleted, whether two-step sign-in is on, and which teams it's on.
- Each account's events, with their times: sign-ins, password and two-step changes, reset and recovery requests, and when things like saving pay settings or downloading your data happened. Only that and when, never what was in them: staff never see your pay settings or the download.
- Help requests: everything you write to us, and any screenshot you add.
- Requests to get back into an account after losing everything that need a person's look: the account's name, Stripe's result and the name on the ID.
- Counts across the service (accounts, teams, shifts added this week) used to keep it running.
They can't see anyone's pay settings, clock-in locations or calendars. They see a team's schedule only while the team's owner or an admin has turned on support access under Team → Setup, for 1, 3 or 7 days; each look shows in the team's History, and the team can turn it off at any time.
Who processes it
The app and its database run on Cloudflare (Cloudflare, Inc.), in the United States. Email notices are sent through Cloudflare's email service.
ID checks (Stripe Identity). Only if you lost your password, your phone and your backup codes and you're a team owner or have no team: to get back in you can check your ID with Stripe Identity (Stripe, Inc.). On Stripe's own page you take a photo of a government ID and a selfie; Stripe processes them under its own privacy policy. We never receive or keep the images. We keep Stripe's session id, its result (whether the ID and the selfie matched) and the name on the ID, which we compare with your account's name and delete once the request is settled. If the names are close but not a clear match, two people on our staff see that result (never the images) and both have to approve it; a clear mismatch is refused.
We don't sell personal data, share it for advertising, or use it to train AI models.
How long we keep it
- Your account, your jobs and your pay settings: until you delete them, or ask us to.
- Clock punches for a team's job, and timesheets: while the team exists, because they are the employer's hours record for payroll. If you delete your account, the team keeps those hours under "Former member", with no name and no pay. Punches for your own jobs: until you delete your account.
- A team's schedule and history: while the team exists. When the owner deletes a team, it closes at once and everyone is told; the owner can cancel that for 7 days, and then all of its data is deleted. People keep their own accounts.
- Failed sign-in attempts: about a day. A record of each successful sign-in (time and IP address): while your account exists. Sessions: until they expire (12 hours) or you sign out.
Your choices
You can see and change your name, language, time zone, email settings, calendar link, jobs, pay settings and clock-in sharing in the app. You can download your own data (Account → Download my data, as JSON, pay included) and delete your account yourself (Account → Delete my account, with your password and two-step code). For help, email contact@weblandscapes.com from the address on the account. We answer within 30 days.
A team owner decides what the team keeps about its schedule. If your employer runs your team on EveShift, ask them first about their records; we'll help them answer you.
Children
EveShift is for workplaces. Workers aged 14 to 17 may be on a team their employer runs; we store only their name, email, schedule, clock punches and, if the employer sets it, an age band or date of birth. We don't knowingly let anyone under 13 use EveShift.
Changes and contact
If this policy changes in a way that matters, we'll update the date at the top and tell account holders by email. Questions: contact@weblandscapes.com or (786) 372-0287.