Weeksolved holds your schedules and your team's names and hours. Here is exactly how that data is protected — in plain words, with nothing overclaimed.
Encrypted, everywhere. Every connection to Weeksolved runs over HTTPS/TLS, and your data is encrypted at rest on Google Cloud infrastructure — the same platform that runs Google's own products.
Your account is an island. Data is partitioned per account and enforced at the database layer: your schedules are readable and writable by your login and no one else's. Sign-in is handled by Google's identity service; passwords are never stored by us in any readable form.
We never see a card number. When paid plans open, checkout and billing run on Stripe's PCI-compliant systems. Card details go to Stripe, never to us, and never touch our infrastructure. Weeksolved is the seller of record for your subscription; Stripe processes the payment.
No staff contact data is required. Weeksolved works without collecting employee emails or phone numbers at all — schedules can go out by print, export, or calendar file. If you do add contact details, they stay inside your account like everything else.
Your data leaves when you say so. Everything exports as a spreadsheet (CSV) and PDF whenever you want it. Close your account and your data stays exportable for 30 days; ask us to delete it sooner and we will. Backups are kept for 14 days and then expire, so a deleted account disappears from those within two weeks rather than instantly — the privacy policy sets out how to make a deletion request, how we handle it and how long it takes.
Backed up daily, kept for 14 days. The database is backed up daily and those backups are kept for 14 days. They are there so we can recover from our own mistakes. They are not a substitute for the exports you keep yourself.
We can reach the database. We'd rather say so. Like the operator of any hosted service, we can open the Google Cloud console behind Weeksolved. We don't read customer schedules in the ordinary running of the business, and we'd only look to fix a fault you'd reported or where the law required it. Anyone claiming their staff cannot technically reach a hosted database is describing end-to-end encryption, which this is not — and if that matters to your business, staying signed out keeps everything in your own browser.
Your people's details never leave your account. Names, phone numbers, pay rates, accrued time off, license dates, notes, and every shift you've ever scheduled someone for — none of it is sold, rented, published, handed to anyone for their own purposes, or used to train any model. That's written into section 3.1 of the Terms, so it's a promise we owe you contractually, not a policy line we could quietly rewrite. Three ways it ever leaves: you send it, our database provider stores it so the service can exist, or a valid court order compels it — and in that last case we tell you first unless a judge forbids it.
No ads, no trackers, no selling data. The product is the business. Your schedule data is used to draw your schedule — nothing else. It is never sold, never shared for advertising, and never used to train anything.
One file comes from somewhere else, and we'll name it. Opening Weeksolved fetches the sign-in library from Google. It does not receive your schedule or your staff — it serves a file — but a request carries an IP address, so we won't pretend the page contacts nobody. It used to be three: the typefaces and the PDF library are now carried inside the page itself, so Google Fonts and Cloudflare's CDN are not contacted at all. Block the one that is left at your firewall and Weeksolved still opens, still drafts a week, still places every break and still exports a PDF in the designed typefaces; the only thing you lose is signing in to an account.
Anyone can build a page that looks exactly like this one. What they cannot do is behave the way we do. These four things are always true, and a message that breaks any one of them is not from us:
Real mail from us comes from weeksolved.com, with one exception we'll name. Account mail — the sign-up confirmation and password resets — is sent by Google's Firebase service on our behalf and arrives from a noreply address at Google. Everything else, and anything at all that asks you to do something, comes from an address ending @weeksolved.com. Not a lookalike domain, not a free mailbox, not a domain with an extra word in it. Read the part after the @ and nothing else — the sender name is the easiest thing in the world to fake.
Every link we send goes to weeksolved.com. Never a shortened link, never a redirect through somewhere else, never an attachment you have to open to find the link. If you are not sure, do not press it: type weeksolved.com yourself and sign in. Anything real will be waiting for you there.
We will never ask you for your password. Not by email, not by text, not on the phone, not to “verify” anything, not to help you with a problem you reported. There is no situation in which we need it, so anyone asking is not us. We also never ask you to move money, change bank details, or send your staff's details by email.
An email tells you something happened. It never makes it happen. Changing your password, changing your email address, and deleting your account can only be done inside the app, after signing in. So a message saying “click here to keep your account” is not a thing we would ever send.
If a message looks wrong, forward it to security@weeksolved.com and we will look at it and warn everyone else if it matters. You are never wasting our time by asking — we would far rather see ten harmless ones than miss the real one.
That first Google-sent message often lands in spam or Promotions, because your inbox has never seen the address before. Mark it “not spam” once, and a password reset will reach you when you actually need it.
We're a small company, which cuts both ways — no security theater, and no ticket queue between you and a fix. If you believe you've found a vulnerability, email security@weeksolved.com with the details and you'll reach the person who can fix it. We acknowledge within three business days, keep you posted, and credit you if you'd like.
Machine-readable version, for anyone who looks for one: /.well-known/security.txt.
We won't take legal action against anyone who reports a problem in good faith, stops at proof of concept, and doesn't access, change or keep anyone else's data.
Weeksolved schedules staff. It is not built for patient information and we are not a HIPAA business associate — we will not sign a BAA, and our terms do not permit protected health information to be put into the product. If you run a clinic or a pharmacy, that is not a limitation you will feel in practice: a schedule needs your employees’ names, hours and credentials, none of which is patient data. Keep patient information in the system built for it, and if you are unsure whether something counts, leave it out and ask us.
No SOC 2 report. No ISO 27001 certificate. No third-party penetration test. Weeksolved is a small team, and that is a choice about where the money goes: into the isolation model rather than into audit fees. Your account is separated at Google's database layer rather than by our own code, which is the control those audits would mostly be checking. We would rather build the control than certify it. If one of the three is a hard requirement for your procurement, tell us before you evaluate us rather than after, and we'll say honestly what's realistic and when.
We'd rather write that paragraph than have you find it in a security review. Everything on this page describes what is running today, not what is planned.
We don't display compliance badges we haven't earned. What's written here is simply true.