Understand Data Encryption

What this guide covers

This guide explains the encryption measures JobsiteOn uses to protect your data. You will learn about encryption in transit, encryption at rest, key management, and what additional protections apply to sensitive fields.

Encryption in transit

All data transmitted between your browser and JobsiteOn servers is encrypted using TLS 1.2 or higher. This applies to:

• Web application traffic.
• API calls from mobile apps and integrations.
• Webhook payloads sent to third-party services.
• Emails sent through the platform.

You can verify encryption by checking for the padlock icon in your browser's address bar.

Screenshot: A browser address bar showing the padlock icon and "https://app.jobsiteon.com" with a security certificate popup.

Encryption at rest

All data stored in JobsiteOn databases is encrypted using AES-256, the industry-standard encryption algorithm used by financial institutions and government agencies.

Encrypted data includes:

• Contact records, property details, and job data.
• Invoice and payment information.
• File attachments (photos, documents, logos).
• Database backups.

Key management

Encryption keys are managed through a dedicated key management service with:

• Automatic key rotation on a regular schedule.
• Separation of duties -- keys and encrypted data are stored in different systems.
• Audit logging -- all key access events are recorded.

Animation: A simplified diagram showing data flowing from your browser through TLS encryption to JobsiteOn servers, then being stored with AES-256 encryption.

Sensitive field protection

Certain fields receive additional protection beyond database-level encryption:

• Payment card tokens -- stored by the PCI-compliant payment processor, never by JobsiteOn directly.
• OAuth tokens -- integration credentials encrypted with application-level encryption.
• Password hashes -- stored using bcrypt with a high work factor, making them resistant to brute-force attacks.

What encryption means for you

• Your data is unreadable without the key. Even if someone gained access to the database files, the data would be encrypted gibberish.
• Intercepted traffic is useless. TLS ensures that data captured in transit cannot be read.
• No action required. Encryption is always active and requires no configuration on your part.

Tip: While JobsiteOn handles server-side encryption, you can further protect your account by using a strong password and enabling two-factor authentication.

Note: JobsiteOn does not support client-side encryption or bring-your-own-key (BYOK) at this time. All encryption is managed by the platform.

Related articles

• Security Commitments Overview
• SOC 2 Compliance
• API Security Best Practices