Your data: where it lives and who can see it
Where OpalSketch keeps your projects today and with the cloud service, who on your team and which clients can see what, and how to take everything with you.
Today: a preview in your browser
The designer and the portal run in your browser now. Your projects, designs and settings are saved in that browser, on that device, and another browser or device does not see them.
Saved in this browser
The portal keeps your workspace in this browser's storage, and the designer keeps your design there too. Clearing the browser's data for the site deletes them, and a private window starts empty.
Export a backup, often
In the portal, Modules, then Your data, then Export backup downloads the whole workspace as one file. Import backup puts it back, in this browser or on another computer.
A copy of each design
In the designer, the plan file saves the whole design, and every export is made in your browser: nothing is uploaded to make it.
Client links stay on this device
Because your projects live in your browser, a client link, and the client's own page, show only projects stored in that browser. Use them to show a client their page at your desk.
With the OpalSketch cloud service
The cloud service is built and not live yet. When it is, your workspace is kept on the server, follows you to any device, and works like this.
Sign in with a code, not a password
You sign in with your email address and a 6-digit code sent to it. A code works for 10 minutes and five tries, and a new one can be asked for at most every 30 seconds and five times an hour. There is no OpalSketch password to remember, reuse or leak.
Clients sign in the same way
A client signs in with the email address you have on file and a code. A code goes out only when a project is shared with that address, and the page answers the same either way, so it does not reveal who your clients are.
Your own workspace, no lost changes
Your first sign-in creates your workspace with you as its owner. Projects, contacts and settings are kept as separate records, each with its own version; when two people change the same one, the portal merges the two instead of one overwriting the other.
Codes and sessions stored as fingerprints
Sign-in codes, sign-in sessions, client accounts and client sessions are stored only as a SHA-256 fingerprint. A copy of the database signs nobody in.
Limits on guessing
Sign-in, invitations, client sign-in and client links are rate limited per visitor, and a connection that keeps trying wrong client codes or email addresses is turned away for a few minutes.
Daily backups
The cloud service includes a daily backup of its database that keeps the newest 14 copies. Expired sign-ins, codes, client accounts and sessions, and unused invitations, are deleted on their own.
Card numbers never reach OpalSketch
Paying for a plan happens on a hosted checkout page. The card details go to the checkout, not to OpalSketch.
Email notices
With email switched on for the service, invitations and client links can be emailed, and owners and admins hear when a client messages, approves, declines, signs or completes a form. A failed notice never blocks the action it is about.
Who can see what
Everyone on your team signs in as themselves and sees what their role allows. A client sees only the project you shared with them.
Everything, including the plan and billing. The only one who changes roles. The owner cannot be removed.
Everything except removing the owner. Invites people and can remove members and viewers.
Works in projects, quotes and the designer.
Can look at everything but change nothing.
Sees only the projects you shared with them, and only what you sent: no costs, drafts, tasks, time, purchase orders, notes or activity. Can approve, sign, answer and message.
Everyone but the owner can leave a workspace. Team accounts come with the cloud service; paid plans include unlimited users, and Free is for one person.
Client links, checked by the server
With the cloud service, the server decides what a client link may show and do.
How the client portal works- Each project link carries its own random code, and the server checks it before it shows anything.
- When the client on the project has an email address on file, the server also asks for that address.
- A client who signed in with that address and a code sees every project shared with it, and opens each one without the link's email check.
- The client receives a reduced copy of the project made on the server: no costs, drafts, tasks, time, purchase orders, notes or activity.
- A client can approve, decline, answer, sign and message, and nothing else. Approvals, signatures and answers also get an entry in the project's activity log.
- Make a new link and the old one stops working. Switch off the client portal and every link stops.
Your data stays yours
You keep ownership of the designs, notes, files, contacts and documents you put in, and you can take them with you at any time.
One-file backup
Export the whole workspace as one file and import it again whenever you like. The file is plain JSON text.
Standard file formats
Every design downloads as a plan file, and as PNG pictures, a GLB model, a DXF drawing and CSV parts lists that other programs open.
Your catalog is yours
Products you import in My catalog go with your backup, and catalog data built for you on request stays yours.
OpalSketch has no AI features today, so nothing you make is sent to an AI service. How personal information is handled is in the privacy policy; ownership is in the terms.
Questions about your data?
Write to hello@opalsketch.com, or look around first: the sample workspace in the portal has made-up clients and numbers.