Your data stays yours

Where it lives, who can see it, how it is backed up and what happens if something goes wrong. All written here, without the jargon.

Montréal
Where your data lives, by default
Every table
Protected by access rules
Every day
A database backup
Every minute
A check on the tool

The path of a piece of data

From your employee's screen to the backup, every stage has its protection. The whole trip is encrypted.

  1. Anywhere

    Your teams

    • Office
    • Field
    • Your clients
  2. Firewall

    The entrance

    • Requests filtered
    • Bots blocked
    • Rate limited
  3. Montréal

    The application

    • Personal account
    • Role checked
    • Lookups logged
  4. Canada

    The database

    • One per client
    • Access rules
    • Encrypted at rest
  5. Canada

    The backups

    • Every day
    • Kept 7 days
    • Restore tested

Always watched: the tool is checked every minute, a scheduled job that fails to run raises an alarm, and error reports carry no personal information.

Seven protections, one inside the other

If one gives way, the next one holds. Click each layer of the square to see what it does.

1 / 7

Network

The firewall filters requests, blocks bots and limits rates before anything reaches the application.

Your data

Who sees what

Your grid is drawn with you before the build. Here is what one looks like for a workshop.

  • Edits
  • Views
  • No access
OwnerOfficeFinanceShopField
ClientsOwner: EditsOffice: EditsFinance: ViewsShop: ViewsField: Views
QuotesOwner: EditsOffice: EditsFinance: ViewsShop: No accessField: No access
Prices and marginsOwner: EditsOffice: ViewsFinance: ViewsShop: No accessField: No access
Work ordersOwner: EditsOffice: EditsFinance: No accessShop: EditsField: Views
HoursOwner: EditsOffice: ViewsFinance: ViewsShop: EditsField: Edits
InvoicesOwner: EditsOffice: ViewsFinance: EditsShop: No accessField: No access
SettingsOwner: EditsOffice: No accessFinance: No accessShop: No accessField: No access

A year of backups

One copy a day. The last seven are kept, and a restore is tested every quarter under maintenance.

Daily backupKept right nowRestore tested

When something goes wrong

Our response times under a maintenance contract, on a scale running from a minute to a week.

Outage detected

Checked every minute

Critical outage picked up

30 min to 1 h, 2 h at most

Bug fixed

1 business day

Small adjustment

2 business days

If a privacy incident happens

Law 25 sets out a precise path, and the tool gives you what you need to follow it. The decision to notify stays yours: we help you through it.

  1. 1

    Detect

    An alert or a report. Limiting the damage comes first.

  2. 2

    Assess

    The log shows what was viewed, by whom and when.

  3. 3

    Record

    Every incident goes in the company's register, serious or not.

Risk of serious injury

You notify the Commission d'accès à l'information and the people concerned.

No serious risk

The incident stays recorded in the register.

Act respecting the protection of personal information in the private sector, s. 3.5 and 3.8

If we part ways

Nothing holds you with us. At the end of the project everything is in your name, and our access is an account like any other.

  • Source code

    In your repositoryStays with you

  • Database

    In your accountStays with you

  • Hosting

    In your accountStays with you

  • Domain name

    In your nameStays with you

  • Studio Plavon's access

    An account visible in your teamClosed by you in one click

Who hosts what

Every supplier is noted in your privacy impact assessment, especially those outside Quebec.

  • SupabaseDatabase, files and sign-in

    Canada (Montréal)

  • VercelApplication hosting and firewall

    Functions in Montréal, American company

  • GitHubSource code

    United States, no client data

  • Better StackUptime monitoring

    No client data

  • CloudflareDomain name (DNS)

    Global network, no client data

Depending on the project, email and text messages go through Resend and Twilio, outside Canada. If your tool needs them, we note it with you.

Questions about security

Where is our data hosted?

By default, the database and files are in Canada, in Montréal, and the application runs in Montréal. Everything is in your own accounts, in your name.

Can Studio Plavon see our data?

During the project and maintenance, our team has an account that gives it access to test and fix things. That account is visible in your team list, and you can close it in one click.

What happens when an employee leaves?

You close their account. Since everyone has their own, nobody else is affected and there is no shared password to change.

Can we recover data deleted by mistake?

Yes, from a backup, as long as it is still kept. Backups are daily and kept for seven days.

Does this make us compliant with Law 25?

The tool gives you the means, but compliance also depends on your policies and your privacy officer. We document with you what the tool holds, and our Compliance page goes through each section.

Law 25 and Law 96, section by section