Frequently asked questions
Technical questions
Where your data lives, who can see it, how Noor works and what happens when something goes wrong
When people are introduced to amana, they usually don’t ask about features first, but about trust. Here are the answers to the technical questions that boards, data protection officers and IT leads ask us most often. What we promise is set out in our contracts; the answers point you there.
Noor and artificial intelligence
Which AI is behind Noor?
Noor uses open language models from Mistral, a European AI developer. They are not run by the developer, though, but by Scaleway, a French cloud provider, in its data centers in Europe. Scaleway also turns speech into text. So your requests go neither to the developer of the models nor to an AI provider outside the EU.
Is the AI trained on our data?
No. Scaleway promises us by contract not to keep requests and answers after processing, not to use them for training and not to pass them on to the developers of the models. So the models do not learn from your questions. amana itself does not train any models.
What is Noor allowed to see?
Only what the person asking may see themselves. Noor works with exactly their rights in their current view. Someone who only looks after the youth group gets no financial figures through Noor. Noor never sees the data of another organization.
Can Noor change or send anything on its own?
No. Noor prepares, a person decides. Anything that changes something, Noor shows as a preview. It is only carried out once an authorized person visibly confirms it, and then it appears in the change log like any other change.
Are our conversations with Noor stored?
amana does not store open questions to Noor. If a conversation belongs to a task that Noor prepares, such as a message, it stays with that task so it can be traced how it came about; 90 days after the task ends, the content is emptied. For billing we only count how much Noor is used, not what was asked.
Where your data lives
Where is our data stored?
Operations, databases, files and email delivery run at Scaleway, a French cloud provider, in data centers in France. The encrypted second backup is at Hetzner in Germany, so with a second, independent provider. Both providers are bound by contract to the same data protection duties as we are.
Which service providers process our data?
We use two providers for this: Scaleway for operations, email delivery and Noor, Hetzner for the encrypted second backup and our support mailboxes. The full list with service, location and data affected is in the contract. If a provider is added, we announce it at least 14 days ahead. That also applies to services that are already built but still switched off, such as the direct bank connection and sending via WhatsApp.
Does data go to the USA?
Data processed on behalf of your organization stays in the EU. The web app loads no fonts, scripts or trackers from third parties. If you like, you can sign in with your Google account; that sign-in then takes place at Google. If you prefer not to, use an email address and password.
Does amana run its own servers?
No, we do not run our own server rooms. We use the data centers of Scaleway and Hetzner with their access controls. Production and development are fully separate: their own cluster, their own databases, their own sign-in, their own storage. Demos run only with a made-up organization. We are currently looking into a package that lets you run amana yourselves.
Who can see what
Can another organization see our data?
No. Every organization has its own separate area. All data carries the identifier of its organization, and the server checks on every single request whether the person belongs to that organization and has the required right. A new interface stays locked until it is explicitly given a permission check, and automated tests check with every code change that other organizations cannot be reached.
How do we decide who may see what?
Through roles that you assign yourselves. Reading, changing, booking, reversing and deleting are separate rights, each one individually for finances, bank data and member data. There are templates for chair, treasurer, auditor (read only) and member administration, for example; you create your own roles on top. Rights can also be limited to a single cash register, project or group. If someone has several roles, their rights add up.
Can amana look at our data?
Not in the app: amana staff have no access there to your organization’s data. But whoever runs servers can always technically reach the systems, and we say so openly. At amana, only the management has this access, only through non-public routes and with two-factor sign-in, and is bound in writing to confidentiality. It is used only for operations, backup and fixing errors, and only within the scope of our contract with you.
How is sign-in protected?
Sign-in goes through a separate sign-in service using the OpenID Connect standard; amana itself stores no passwords. Anyone can set up an authenticator app as a second factor. Anyone with rights that touch money, access, published content, sending or confidential data has to: without a second factor, exactly those rights are suspended. After repeated failed attempts, the wait until the next attempt grows.
Can we see who changed what?
Yes. A central change log records who did what and when: for bookings, receipts, bank details, exports, roles and rights, consents, sending, member data and sign-ins. For member data it shows which fields were changed, not the values. Entries cannot be changed afterwards.
Backup and outages
How is our data backed up?
Twice. Once a day the operator backs up the databases and keeps the backup for 7 days. In addition, an encrypted second backup goes to Hetzner in Germany every hour: the hourly ones for 30 days, plus one per day for 90 days and one per month for 366 days. Each of these offsite backups is locked against deletion for 30 days, even for us.
Can Hetzner read our backups?
No. The second backup is encrypted before it leaves our cluster. Even the key the cluster uses to write it can neither read nor delete it.
How much data can be lost in an outage?
At most the changes of one hour. After an outage we restore within one working day. Restoring is fully tested, an automatic restore test runs every week, and several times a day we automatically check that the second backup has arrived.
Can just our organization go back to an earlier state?
Yes, on your request. We load the chosen backup into a separate database created just for this, take only your organization’s data from it and discard the database afterwards. Other organizations are not affected. Beforehand you get a report on what will change.
How reliably is amana available?
Our target is 99 % per calendar month. If a compute node fails, it is replaced automatically. We roll out updates outside 8 to 22 o’clock where possible; a longer planned interruption we announce at least two working days ahead. Our support answers within one working day and responds to outages within 8 hours during support hours.
Data protection
How does amana handle the GDPR?
Your organization stays responsible for its members’ data; amana processes it only on your behalf. The basis is a contract under the EU Commission’s standard contractual clauses, with our technical and organizational measures and the list of all service providers. An administrator of your organization accepts it in the app. You decide the legal basis for processing as the responsible party; usually it is membership.
Our member data often shows religion. Is that taken into account?
Yes, that is exactly why we chose this approach: operations, backup and Noor run only with providers in the EU, rights are finely separated, anyone who sees confidential data needs the second factor, and technical logs contain identifiers instead of names. For a data protection impact assessment, we provide help on request.
How do we answer requests for access and deletion?
Directly in the app. For every member there is an export of their data, and you can correct or delete it yourselves. If such a request reaches us, we pass it on to your administrators straight away.
What happens to deleted data?
A deleted member can be brought back for 30 days; after that they are deleted. Records that your organization has to keep, such as receipts and books, stay locked until the end of their period. Deleted data expires from backups within 366 days.
How does amana send messages via WhatsApp?
Sending via WhatsApp is built but not yet switched on. Once it is, a message goes only to numbers whose owner has consented for exactly that number. An import or creating a member never creates a consent, and anyone who writes “Stop” or changes their number gets no more messages.
Can we always get our data, even if we leave?
Yes. You can download a full export as a ZIP file at any time: your tables as CSV and all original files. When you leave you get the same export, and your organization stays deactivated for 90 days; during that time you can take the departure back. After that we delete all your organization’s data.
Technology and development
What is amana built with?
The server is written in Java with Spring Boot and stores in PostgreSQL databases. The app is built with Flutter and runs in the browser on computer, tablet and phone. It all runs in Kubernetes at Scaleway. Your browser connects to the platform over encrypted HTTPS.
Where is the source code?
On our own GitLab server at Hetzner in Germany, not with a public code host. It is also backed up encrypted every night. Credentials for operations are not in the code but protected in the operating environment.
How do you make sure an update doesn’t break anything?
Every change goes through automatic tests, including the check that no organization can reach another’s data. Every night, further tests run against a complete, running environment. Before every rollout, the production configuration is checked so that switched-off features stay off. We keep security findings in a list; one counts as fixed only with a test or proof.
Do we have to install or update anything?
No. amana runs in the browser, and you sign in at app.amana-app.com. We roll out updates centrally, so everyone always works with the same version.
Books and receipts in Germany
How do books and receipts stay traceable?
A booking cannot be rewritten or deleted after it is posted. Corrections go through a reversal as a separate counter-entry; the original stays. Bookings are numbered consecutively per fiscal year and chained by a checksum, so a later change stands out during a review. Locking a fiscal year takes two people; after that, the database itself accepts no more changes in that year.
How long are receipts kept?
Receipts, books, donation receipts and payment proofs for 10 years from the end of the year. Receipts are stored versioned and are locked against changes and deletion for that time. A receipt attached to a booking stays there, even after a reversal.
Can our tax firm work with the data?
Yes. Bookings go to the firm in the DATEV format; the export is blocked as long as transactions, receipts or accounts are still open. A reversal appears in it as a separate counter-entry on its day. For a review, the data export delivers all bookings with status, checksum and a description of the files.
Has anyone checked the bookkeeping from the outside?
Confirmation by a tax adviser or an auditing body is still pending. That is why we do not advertise with seals of approval, but describe how amana works. Organizations in the pilot use amana alongside their existing bookkeeping, and their tax firm checks on a real month whether it suits them. We support this trial run.