jobsitecalendar.

PRIVACY & TRUST

Security, in practice.

Protect access. Keep less information. Be clear about the limits.

Updated November 6, 2026 · Invitation-only US business pilot

Security is an ongoing responsibility

These measures reduce risk; they do not guarantee that data will never be exposed or lost. Jobsite Calendar does not claim SOC 2 or ISO certification, an independent security audit, or suitability for regulated health, identity, or payment-card records.

Protected sign-in

The hosted service uses HTTPS. Passwords are salted and hashed; protected sessions expire after 12 hours. You can change your password and revoke other sessions. Sign-in attempt limits help resist guessing. When account email is enabled, invited users choose their own passwords through one-use links. Manually provisioned users replace temporary passwords before using the workspace.

Company access boundaries

Server-side checks associate each account with its company workspace and role. Managers can access company financial records. Subcontractors can access assigned work and appropriate bookings. A page URL alone does not grant access.

Optional multifactor authentication

Open Account security → Two-step verification to add an authenticator app and require a second factor at sign-in. Authenticator secrets are encrypted, and recovery codes are stored as hashes. Save recovery codes privately. Multifactor authentication protects an account only after its user enables it; no phone number is collected for this feature.

Less data in storage

Customer and site-address fields can be left blank when unnecessary. New photo uploads are checked and have supported embedded metadata removed before storage. Older photos and backups are not automatically scrubbed. QuickBooks private notes and billing email addresses are omitted from the invoice sync.

Limited connected data

Google calendar checks use free/busy intervals, not event titles or guests. Gmail access sends the invoice emails you choose; it does not read the inbox. QuickBooks imports customer invoices and balances. Provider passwords are not entered here.

Protected connection credentials

Google and QuickBooks access credentials are encrypted in the application database and omitted from workspace exports. Disconnect controls remove active local credentials and attempt provider revocation. This is not a claim that every business record is individually encrypted.

When account email is configured, you can request a sign-in link instead of entering a password. Each sign-in link expires after 15 minutes and requires an explicit sign-in action with confirmation of your account email. Opening an email does not sign you in automatically. Password resets use a one-use link valid for 30 minutes; invitations use a one-use link valid for 24 hours. Link requests are rate limited and do not reveal whether an address has an account.

The live database stores hashes of link credentials. The full link is included in the email, so Resend and your email provider can process it. Protect your mailbox and never forward an access link. Provider and mailbox copies can remain after the link expires. Account-email setup requires disabling provider open and click tracking.

Email links do not bypass enabled two-step verification. Sign-in and password reset still require an authenticator or recovery code when that protection is enabled. A password reset signs out existing sessions and invalidates other account links; it does not sign you in automatically or turn off multifactor authentication. Password retrieval is not offered because readable passwords are not stored.

Keep your workspace focused on the work

Use the minimum customer and team information needed for a job. Leave Social Security numbers, identity documents, health records, full bank or card details, passwords, and access tokens out of the service. Review the visible content of photographs before uploading; image processing cannot hide a document, face, address, or access code shown in the picture.

The app does not include advertising trackers or analytics scripts. Only necessary sign-in cookies and interface preferences are used. Company records are not used for targeted advertising or AI model training.

Operations and recovery

The app runs under a dedicated server account with restricted filesystem access. Release updates exclude live workspace data and secrets. The deployment process creates a consistent database backup before switching releases, and scheduled backups support recovery.

The pilot does not yet promise off-site recovery, a recovery-time objective, or a backup expiration schedule. Keep your own copies of critical business records. Credential encryption does not replace server access controls, key protection, and secure backup handling. The Privacy Policy explains current retention and deletion limitations.

What your team can do