Data residency and privacy

Last updated October 29, 2026

Goshen is run by Goshen Labs Inc. This page says what we store, where, for how long, and what we never store.

Where data lives

Everything that handles your data runs on servers we rent from Hyperstack in its CANADA-1 region in Quebec, Canada: the API gateway, the dashboard, the database, the GPU server that runs the models and trains your adapters, and the encrypted backups. Hyperstack is run by NexGen Cloud, a company headquartered in the United Kingdom. Your data stays on its servers in Quebec. Traffic between our servers travels over an encrypted WireGuard tunnel. We run in one region; we do not copy your data to other regions or countries.

API requests

We do not store prompts or completions. The text of a chat or embeddings request passes through memory on its way to the model and back to you. It is not written to the database, to logs or to disk. An automated test sends marked text through every API path and checks the database and logs for it.

For each request we keep:

• the account, project and API key it used, the model, the endpoint and the time;
• the number of prompt and completion tokens, the HTTP status and how long it took.

These counts are how we invoice you. We keep them for as long as invoicing and accounting records require, including after an account is deleted. They contain nothing about what a request said.

Server logs record the method, route, status and timing of each request, and the first 8 and last 4 characters of the API key used, as your key list shows them. They never record bodies or query strings. Each service's logs are capped at 50 MB and rotate out after that.

Fine-tuning data

Fine-tuning is different: to train a model on your examples, we have to keep the file you upload until you delete it.

• Each file is encrypted with AES-256-GCM using a key that belongs to that file alone. That key is itself encrypted with a master key held on our servers, with recovery copies kept off those servers by our administrator.
• During training, the decrypted examples exist only in the training server's memory, never on its disk, and are dropped when the job ends.
• Training logs record step numbers and loss values, not your examples.
• The adapter weights a job produces are yours. Only your API keys can call or delete the resulting model.
• We do not use your files, your adapters or your requests to train anything for anyone else.

Deleting a file removes the encrypted file and its key. Deleting a fine-tuned model unloads it and removes its adapter from the GPU server. Both happen when you ask, not on a schedule.

Account data

• Your email address, the name you give us, and a password hash (argon2id). We never see your password in plain text after sign-up.
• A SHA-256 hash of each API key and its first 8 and last 4 characters, which your key list shows. The first 8 include the gsk_ that starts every key. We cannot recover a key.
• The names of your organizations and projects, and who belongs to each organization with which role. Members of an organization see each other's email address, name and role.
• For each invite link: a SHA-256 hash of the link, the role it gives, and the email address it is limited to if the person who made it gave one. The service sends no email, so the person who made the link passes it on.
• An audit log of security-relevant actions: sign-ins, key creation and revocation, file and model deletion, project, member and invite changes, and admin actions, with the IP address they came from. It holds no request content. Members of an organization can read the entries for its projects, without the IP addresses.
• Two cookies on app.vpcloud.ca: one keeps you signed in, the other remembers which project you are looking at. The site uses no analytics, tracking cookies or third-party scripts.

Deleting your account revokes your keys and removes your email, name and password hash. Organizations you are the only member of are deleted with everything in their projects: jobs are cancelled, and files and models are deleted as above. From organizations you share with others you are removed, and what you made there stays with the organization; if you are the only owner of one, make someone else an owner first. Usage counts and audit entries stay, linked to an account id that no longer has an email attached.

Backups of the database and of the encrypted files go to a separate storage volume in the same Hyperstack CANADA-1 region in Quebec, attached to the server that runs the API and the database. They are encrypted twice: the volume is encrypted with its own key, and the backup software encrypts each backup again. Backups are deleted when they are 14 days old, so data you delete is gone from the backups within 15 days.

Third parties

The model weights come from their publishers on Hugging Face; we download them to our GPU server. No customer data is sent there. We do not use US analytics, error tracking, payment processors or CDNs.

Security

• HTTPS for every public hostname. From the internet, the API server accepts traffic only on ports 80 and 443, and SSH from a short list of our own addresses. It accepts the encrypted tunnel only from the GPU server, over the provider's private network. The GPU server accepts connections only from the API server.
• Server administration is by SSH with ed25519 keys only (no passwords, no root login). The GPU server takes SSH only from the API server.
• Account administration, such as activating or suspending an account, uses an admin-only page of the dashboard, which needs a signed-in admin account, or an admin command run on the API server over that SSH access. Every admin change to an account is recorded in the audit log.
• Disks that hold customer data are encrypted.

We do not hold security certifications at this time. If you need details for a security review, write to us.

Your choices

You can download your training files and see your usage in the dashboard, and delete files, models or your whole account at any time. For anything else, including a copy of the personal information we hold about you or a correction, write to michael@goshen.fyi.

Because prompts and completions are not stored, we have none to disclose to anyone, including in response to legal demands.