Information Security Policy
Crossvora is run by Oakwell Technologies. It helps sellers list products and manage orders across marketplaces. This policy sets out how we protect the data sellers trust us with. It applies to everyone who works on Crossvora.
Last updated: 15 November 2026.
What we protect
- Seller accounts: name, shop name, email and login details.
- Seller content: products, photos, prices, costs and notes.
- Marketplace connections: the access tokens marketplaces give us when a seller connects a shop.
- Orders, including the buyer details a marketplace shares so an order can be recorded.
Data classification
We sort the data we hold into three classes, and protect each one accordingly.
- Restricted: passwords, marketplace access tokens, API keys and other secrets. Passwords are stored only as salted hashes. Tokens are encrypted before they are stored. Secrets live only in the server's configuration.
- Confidential: personal data and business data: seller names and emails, buyer details on orders, products, costs and notes. Encrypted in transit, kept in a database that cannot be reached from the internet, and seen only by the seller it belongs to and by staff who need it to give support.
- Public: what a seller chooses to publish, such as listing titles, photos and prices.
Access control
- Access follows least privilege: each person gets only the access their work needs, and it is removed when they no longer need it.
- Only named staff can reach the server, the database and the admin area. Accounts are personal and are not shared.
- Each seller's data is kept apart from every other seller's. A seller can only see and change their own workspace.
- Only the people who run Crossvora can reach the server and database, and only to keep the service working or to help a seller who asks.
- When our staff open a seller's workspace to give support, it is written to an audit log.
- We never ask for, see or store a seller's marketplace password. Sellers connect on the marketplace's own login page, or stay logged in within their own browser.
Staff devices and accounts
Everyone who works on Crossvora follows these rules on the computers and accounts they use for it.
- Anti-virus protection is switched on and kept up to date.
- The operating system and browser are kept up to date.
- The screen locks automatically when the computer is left, and needs a password or PIN to open.
- Passwords are long, different for every service, and kept in a password manager.
- Two-step login is turned on wherever it is offered for accounts that reach Crossvora: source code, hosting, domain and email.
- Seller data is not copied to personal devices, printed or left on show.
How data is protected
- All traffic between browsers, our service and marketplaces is encrypted with HTTPS (TLS).
- Passwords are stored only as salted hashes, never as readable text.
- Marketplace access tokens are encrypted before they are stored.
- Keys and secrets live only in the server's configuration. They are never put in source code or shared in messages.
- Logins and sign-ups are rate limited to slow down password guessing.
- Uploaded files are limited to checked image types and given random names, so an upload cannot be run as code.
Marketplace data
- We use marketplace data only to do what the seller asked: list, edit and remove their items, and record their sales.
- We don't sell it, and we don't share it with anyone other than the providers that run the service (hosting, email delivery and payments).
- A seller can disconnect a marketplace at any time. Its access tokens are then removed.
Keeping and deleting data
- Data is kept while the seller's account is open.
- A seller can download their data, or close their workspace to delete it, from Account & team.
Changes to the software
- Every change is recorded in version control and tested before it goes live.
Vulnerability management
- Server: security updates for the operating system are installed automatically.
- Software libraries: at least once a month we check the libraries Crossvora uses against published security advisories, and update any that are affected.
- Network: the firewall blocks everything except the website and administration, and repeated failed logins are blocked automatically.
- Reports: anyone can report a weakness to oakwelltechnologies@gmail.com. We confirm the report and judge how serious it is.
- How fast we fix: critical and high-risk weaknesses within 7 days, others within 30 days. If a fix needs longer, we reduce the risk another way in the meantime.
Incident response
A security incident is any event where data may have been seen, changed, lost or taken without permission, or where the service is under attack.
How to report one. Anyone (staff, sellers, marketplaces or the public) can report a concern to oakwelltechnologies@gmail.com. Staff report anything suspicious as soon as they see it.
Who does what.
- Incident lead: the director of Oakwell Technologies. Decides how serious the incident is, leads the response, and is the one who tells sellers, marketplaces and the regulator.
- Technical responder: the developer on duty. Stops the access, protects the evidence, finds the cause and fixes it.
- All staff: report quickly, and change nothing that could destroy evidence.
What we do, in order.
- Contain: stop the access. Block the source, and replace any passwords, keys or marketplace tokens that may be exposed.
- Assess: use the logs to find what was affected, whose data, and for how long.
- Notify: tell the affected sellers and marketplaces without undue delay, and no later than 72 hours after we confirm that personal data was affected. Tell the regulator where the law requires it.
- Fix: remove the cause and restore the service safely.
- Learn: write down what happened and what we changed, so it cannot happen the same way again.
Review
We review this policy at least once a year, and whenever the service changes in a way that affects it. See also our Privacy Policy and Terms of Service.