Work made only for you
Your add-ins, scripts, content built to your standard, and documentation: assigned to you in writing once paid in full.
Delivered as full source code in your Git repository, with installers and build steps.
Security, NDA & IP
Security, confidentiality and IP: the plain version
You're trusting us with models of buildings that are often under NDA. Here's exactly how we handle your Autodesk® Revit® software models, your project data and the code we write for you, and what we don't claim.
At a glance
Eight practices you can hold us to.
We're a small, founder-led firm. Instead of certificates we don't have, we give you a short written list of practices, and we'll put them in the contract.
NDA first
Signed before any file changes hands. Yours, after a quick review, or our mutual one.
Your environment
Where possible, we work inside your systems, on an account you control and can remove.
MFA everywhere
Multi-factor authentication on every account we use, and only the access the task needs.
Separate credentials
A separate set of credentials for each client. Files stored encrypted, only for the project.
AI only with your approval
We don't put your models, drawings or project data into AI tools. Read the AI policy.
Deleted at close-out
We delete your files from our systems within 30 days of close-out and confirm in writing.
Undo-safe tools
Changes run inside Revit transactions you can undo, with a preview before bulk edits.
Your IP in writing
Work made only for you is assigned to you in writing once paid in full.
NDA & confidentiality
The NDA comes before any file.
Before any file changes hands, we sign an NDA: yours, after a quick review, or our mutual one.
- We never name your company or project publicly without written permission.
- No client names, logos or project details appear on this site or in our marketing unless you agree in writing.
- Please don't attach models to the contact form or the first email. We sign the NDA first, then agree how files move.
Your models stay in your environment
Where possible, we work inside your environment: a project in Autodesk Forma (formerly Autodesk Construction Cloud), your SharePoint or your virtual desktop, on an account you create. You can remove our access at any time.
If files must move, we use the transfer method you choose.
When the work happens in your cloud models, your written scope states who supplies the Revit and Autodesk Forma Design Collaboration seat for that account.
Access & storage
Least access, and only for the project.
- MFA on every account we use, including any account you create for us in your systems.
- Least access: only the access the task needs, for as long as it needs it.
- Separate credentials per client, never shared between projects.
- Encrypted storage: any files we hold are stored encrypted, only for the project.
- Source code in your repository: we deliver to your own Git repository, so you control who can see it.
Security questionnaires welcome
Send us yours. We'll fill it in and answer honestly, including the items where the answer is "no".
We can also send a vendor onboarding pack on request: the tax form for our entity, banking details, and a certificate of insurance where required.
AI policy
Your project data stays out of AI tools.
We don't put your models, drawings or project data into AI tools. We may use AI coding assistants on our own code, and a person reviews and tests every line before delivery. AI is used on your data only with your written approval, in tools you approve.
If your contract has its own rules on AI, tell us on the scoping call so the scope reflects them.
Close-out
Deleted, and confirmed in writing.
We delete your files from our systems within 30 days of close-out and confirm in writing. We keep only what the contract requires (the signed scope and invoices) and anything you ask us to keep for warranty work.
Your source code and handover files stay with you, in your repository.
Where is your team?
A remote company, confirmed in writing before any file moves.
SS Technologies is a remote company. Before any file changes hands, we confirm in writing our registered entity and where your data would be accessed from, so you can check it against your contract (for example, US-persons-only access, background checks or CUI).
If your project restricts who can see files, tell us on the scoping call.
Restricted projects
Some data center owners limit who may access project files. Raise it before you share anything. We'll tell you plainly whether we can meet the requirement, and if we can't, we'll say so before any work starts.
Our code-quality standard
Tools built not to damage your model.
- Changes run inside Revit transactions you can undo.
- Bulk edits show a preview first.
- Tools log what they changed.
- Tested on sample models and on a copy of yours.
- No telemetry: our tools don't send usage data anywhere.
- No license server and no license keys.
- Open-source parts listed in your handover with their licenses.
As with any new tool, keep a backup or work on a detached copy the first time you run it.
Cloud apps with Autodesk Platform Services (APS)
You create and own the APS app and its keys. We request the smallest set of permissions the tool needs, and you can revoke them at any time.
APS usage is billed by Autodesk to your account, not ours. We estimate usage before we build. See pricing and costs outside our price.
IP ownership
Who owns what, in three parts.
The assignment is written into the contract, not left to a "work made for hire" label. Our reusable components are named in your contract, so there's no doubt about which is which.
Our reusable components
Including the data center Revit kit: you get a permanent, firm-wide, royalty-free license to use and change them on any project. We keep ownership so we can keep improving them.
The kit is licensed, not sold outright: a permanent license for your firm to use and change it on any project. Changes we make to fit your standard are yours.
Open-source parts
For example pyRevit (GPL-3.0). They stay under their own licenses, listed in your handover.
Each one is listed by name and license, so your IT team can check it.
No license keys, no license server and no lock-in. If we stop working together, the tools keep working and any developer can maintain them. All engagement terms
What we don't claim
Plain about our limits.
- We don't hold SOC 2 or ISO 27001 certification, and we won't say we do.
- We're not an engineering firm. We don't provide engineering design, calculations of record, code-compliance reviews or stamped drawings.
- We're not affiliated with Autodesk. We build tools for Autodesk software, but we are not an Autodesk partner and Autodesk does not endorse our services.
- We don't have client names, logos or testimonials to show yet. SS Technologies started in October 2026, and we won't invent them.
Engineering responsibility
Our tools apply rules and values that your engineer of record provides. Their outputs are drafting and data aids, not engineering calculations, code-compliance reviews or sealed documents. Your licensed professionals review the results and remain responsible for the design.
Report a security issue
Found a problem? Tell us directly.
If you find a security problem in a tool we built, in this website, or in how we handled your files, email [email protected] with "Security issue" in the subject line.
- Say what you found, where, and how to reproduce it.
- Please don't include client model files or passwords in the email.
- We reply within one US business day and tell you what we'll do next.
The same contact is published in this site's security.txt file.
NDA first · then the scoping call
Need our NDA before the first conversation?
Ask for our mutual NDA, or send yours for a quick review. Then book a free 30-minute scoping call. Within 2 business days of the call you get a written scope with a fixed price for a pilot or first phase, and an estimate range for anything bigger.