Your data

Team isolation

Every board, card, comment and file belongs to exactly one team, and every request Noeto handles is confined to the team it came in for. Your team’s data is not filtered out of a shared view — it is never fetched in the first place.

Membership is re-checked on every request rather than trusted from a session that was valid when it started. Removing someone takes effect immediately.

Where it lives

Noeto runs in the European Union, on AWS in Frankfurt. Boards, cards and comments are in a Postgres database; uploaded files are in object storage. Nothing is copied anywhere else.

The site you are reading has no analytics, no cookies and no third-party requests — see privacy.

What Noeto emails

Only what is described in notifications: assignments, comments on cards you are on, invitations, and role changes. There is no newsletter and no product marketing.

Getting your data out

Anything you can see, an access token can read through the API — boards, cards, descriptions, comments. That is the export route today.

There is no one-click export file yet. Saying otherwise would be more comfortable than it is true.

Leaving

Removing yourself from a team, or being removed, cuts your access immediately and revokes the tokens you issued there. Your cards and comments stay — they are the team’s record of its own work, and pulling them out would leave holes in it.

Deleting a whole team deletes everything in it: boards, cards, comments and files. That one is not recoverable.