Data handling
Where your company's data lives, who else is involved in processing it, how long it is kept and how you take it out or delete it.
Where it is hosted
The database and the application run on Railway infrastructure, in its US East region (United States). Files and photos are stored in Cloudflare R2.
We name the region instead of speaking in general terms because it is a concrete question that deserves a concrete answer. If your company has a data residency requirement that demands hosting in a specific country, we do not meet it today. It is better to know that before moving forward than during the legal review.
It is an infrastructure constraint, not a final decision. Write to us at soporte@nodux.link and we'll talk it through with your specific case on the table.
Who else processes the data
Nodux relies on providers to run. This is the complete list of those that can touch data from your operation, and what for:
| Provider | What for | What data it sees |
|---|---|---|
| Railway | Servers and database | All of the application's information |
| Cloudflare R2 | Files, photos and backups | Uploaded attachments and the database copies |
| Resend | Sending email | Recipient and content of the emails Nodux sends |
| Sentry | Error reporting | Technical data about the error and the ID of the affected user |
There are no advertising providers, no third-party analytics inside the application and no data enrichment providers. We do not sell or transfer information about your company or your customers.
Who at Nodux can see your data
Technical access to the production database is limited to the team that operates the platform, and it is used to resolve incidents or handle a request from you. There is no panel where someone at Nodux browses a shop's operation out of curiosity.
That access exists, as it does on any managed platform, where someone has to be able to operate the infrastructure. What matters is not denying it but how it is controlled: it is set out in writing in the agreement, and every access has a reason attached to it.
How long it is kept
| Data | Period |
|---|---|
| Operational information (tickets, customers, equipment) | While the account is active |
| Audit log | 180 days, configurable |
| Database backups | 30 days, configurable |
| Log of sent emails | While the account is active |
Exporting your information
The system's lists export to a spreadsheet from the interface itself: customers, equipment, tickets, inventory. There is no need to ask or wait.
If you need a full extraction in another format to migrate to another system, write to us and we'll prepare it. We don't charge you for leaving, and we don't hold on to your information as leverage for renewal.
Deleting your account
At the account holder's request, we delete the company's information. The deletion cascades (no loose records are left pointing to data that no longer exists) and there is a record of who requested it and when.
Backups already taken are overwritten in their normal cycle: the deleted information disappears from the copies within the retention window stated above.