How we handle your data and system access
Building tracking and inventory software means working inside your ERP, WMS, carrier accounts and partner data. This is how we handle that access, and what we will put in writing.
Ask a security question
An engagement gives us access to systems that run your operation and to data about your suppliers, customers and stock. The practices below apply to every engagement. The specific commitments for your project are written into its statement of work, and where your own security policies are stricter, we follow yours.
Certification: the plain answer
GenFrontier does not hold SOC 2 or ISO 27001 certification. We are a new firm, formed in November 2026, and we will not imply otherwise. What we will do is complete your security questionnaire, answer each item as it stands today, and tell you plainly where a control you ask about is not in place. If you need a non-disclosure agreement before you share documents, ask for one at the start.
Access: least privilege, under your accounts
- Named accounts in your systems. You create an account for each GenFrontier person who needs access, under your identity provider and your policies, including multi-factor authentication where you use it. We do not use shared logins.
- Only the access the task needs. Discovery usually needs read-only access or exports. Building needs write access to a test environment. Production access is requested for specific tasks, such as cutover or a support fix, and removed or reduced when the task is done where your systems allow it.
- Service accounts for interfaces. Each interface runs under its own service account that you own, separate from any person’s login, so it can be audited and rotated.
- An access register. We keep a list of every account we hold: system, person, access level, date granted and date removed. You get a copy, and it is the checklist used at offboarding.
The same rules apply to carrier portals, EDI networks, cloud consoles and code repositories.
Test environments and masked sample data
We build and test in a test environment or sandbox, not in production. When we need sample data, we ask for representative exports with sensitive fields masked or replaced: customer names and addresses, contact details, prices and anything personal. Item, location and quantity data is usually enough to build and test tracking and inventory work. The masking rules are agreed during the process walk and recorded.
If production data has to be used, for example to migrate open purchase orders at cutover, the statement of work names the data, where it is held, who can see it and when it is deleted.
Credentials
- No passwords, API keys or EDI credentials by email, chat or in documents.
- Credentials are shared through your password manager or secrets vault, or set directly by the account holder.
- Interface credentials are stored in the secrets store of the environment where the software runs, never in source code or configuration files in a repository.
- If we believe a credential has been exposed, we tell you so you can rotate it.
The same applies before an engagement starts: please do not send passwords or customer data through our contact form.
Where code and documents live
- Source code and configuration live in a repository in your organization’s account where you have one. If you do not, the statement of work says where the repository is kept during the build and how it is transferred at handover.
- Documents such as requirements, plans, test results and runbooks are kept in your document system or a shared space you control.
- Working copies of sample data on our side are kept only as long as the work needs them and are deleted at the end of the engagement.
Offboarding at the end
When an engagement ends, or when a person leaves the project:
- We send you the access register with every account we hold.
- You disable or remove those accounts, and we confirm each one is gone.
- We delete working copies of your data, apart from anything the statement of work says we keep, and confirm this in writing.
- Repository access, service account ownership and documents are handed over in full.
If you continue with Support after go-live, access continues only as that support statement of work defines.
If something goes wrong
Each statement of work includes an incident notification commitment. If we suspect a security incident that affects your data, systems or credentials, we notify your named contact within the time set in the statement of work, say what we know and what we do not yet know, and work with your team on containment and next steps.
To ask a security question before an engagement, or to send us your questionnaire, use the contact page. Answers to other common questions are in the FAQ.
Scope your project.
Tell us what you need to track, which systems you run and when it has to work. We reply with questions or a time to talk.