Working with Altioo
How an engagement works, how the price is set, and what Altioo commits to.
This page describes how Altioo usually works. What applies to your engagement is the contract you sign: most often your own, otherwise Altioo's written proposal. If it says something different from this page, it applies.
This page is made to be forwarded. Each part answers one person on your team:
- The person leading the project
- Your IT team
- Your lawyer
- Your data protection officer
- Your security officer
- A company handing Altioo part of its own engagement
- Procurement and accounts
How an engagement runs
A first conversation, free
By phone or video call. To understand your need, and say honestly whether Altioo can meet it.A written proposal
The work, what will be delivered, the timeline and the price. Nothing starts before you agree.The work
Directly with the person doing the work. If your needs change along the way, the proposal is updated in writing.The handover
What you need to carry on without Altioo, as agreed in the proposal: see the end of an engagement.
Where and when
- Where
- Altioo works mostly remotely, and on site when the project needs it, in Belgium and France.
- Hours
- Monday to Friday, 9:00 to 17:30, Brussels time.
- Outside these hours
- An email may get a reply in the evening. Work at night, on Saturdays or on Belgian public holidays is possible if agreed in writing: a production change at night, for example, or being on call as a backup. Altioo does not work on Sundays.
- Response time
- These hours are not a guaranteed response or resolution time. For ongoing support, response times are agreed in writing.
Pricing
Two ways to pay, depending on the work:
- The price
- No published rates: the price depends on the work. You get it after the first conversation, in the written proposal. Prices are given excluding VAT.
- Expenses
- Travel and other expenses are agreed in writing, before the work starts.
- Documentation
- Documentation is part of the work, and of its price. To lower the price or shorten the timeline, you can choose lighter documentation, or none: it is agreed in writing, in the proposal. Another team will then find it harder to take the work over.
- Ending early
- If an engagement ends early, whether you or Altioo decide it, what is owed is set in the contract. See also if Altioo is unavailable.
If Altioo is unavailable
- Documentation kept up to date
- The documentation agreed in the proposal is kept up to date during the work, not only at the end. If Altioo can't carry on, another team can use it to take the work over.
- Ending the engagement
- If Altioo can't carry on, you can also end the engagement, as the contract provides.
Working method
- Your change process
- Altioo follows the way you manage changes: its requests and your approvals go through your own tool, as they do for your teams.
- Tests
- When possible, a change is tested before production, on a test environment or a copy. Some settings only exist in production, such as some access rules: those wait for your approval before they are made. Code written by Altioo, such as an extension or an integration, comes with automated tests when that is possible.
- Backups
- Unless the contract says otherwise, your backups and their recovery stay your responsibility. Before a change in production, how to undo it, and the backup it relies on, is agreed with you.
- Git
- When possible, code and settings are kept in Git, with their history. It isn't always possible: some settings can't be, and not every client uses Git.
Contract
- The contract
- Altioo works for businesses and organisations, not for private individuals. Most of the time, the contract is your own: Altioo signs it once it agrees to its terms. Otherwise, it is Altioo's written proposal, accepted by you. What is signed applies where it differs from this page.
- Law and courts
- The law and the courts are those set in the contract. When the contract is Altioo's proposal, Belgian law applies, and the courts of Ghent, Kortrijk division, have jurisdiction.
- Confidentiality
- If you want to share confidential information from the first conversation, Altioo can sign your non-disclosure agreement, once it agrees to its terms.
- Insurance
- Altioo holds professional liability and general liability insurance. Certificates are sent on request.
Who owns what is delivered
- What becomes yours
- The contract says who owns what is delivered. Unless it says otherwise, what Altioo builds for you belongs to you once the work is paid for: the code, the settings and the documentation. An iTop extension written for you, for example, is yours.
- What Altioo may reuse
- Altioo only keeps the right to reuse the general parts of that work, the parts that say nothing about your organisation. Your data and what is specific to you are never reused.
- Open-source tools
- Tools Altioo publishes as open source, such as the altioo-mcp extension, keep their licence. You can use them freely, under that licence.
- Existing components
- When what Altioo delivers includes tools Altioo already had, or open-source software, these keep their own owner and licence. You still get the right to use and maintain what is delivered.
Personal data
- Altioo's role
- Work on a tool like iTop or Jira often gives access to personal data: names, emails, your colleagues' tickets. Altioo then acts as a processor, as the GDPR puts it.
- The agreement
- Before any access to that data, Altioo signs your data processing agreement (Article 28 GDPR), once it agrees to its terms. The services Altioo uses that may see your data, such as its email, are listed in that agreement. You approve them before the work starts.
- Artificial intelligence
- Altioo doesn't use an AI assistant on your data without your written consent. If you agree, it will only be with a provider and terms you have approved.
- At the end
- At the end of the work, any data Altioo holds is returned to you or deleted, as you choose, unless the law requires it to be kept, and Altioo confirms it in writing.
Access security
To work on your tools, Altioo often needs administrator rights. What you provide, such as a computer, accounts, remote access or software, Altioo uses under your rules. What you don't provide, Altioo brings. Either way, here is how that access is protected:
- Altioo's own accounts, such as email and the password manager, ask for a second check, on top of the password, when signing in on a new device;
- on your systems, Altioo signs in the way your company has set up, often with its own sign-in and its security rules. A second check is used wherever your tools offer one and your rules allow it;
- any credentials you give Altioo are kept only in an encrypted password manager;
- Altioo's computers have encrypted disks, and updates are installed soon after they come out;
- Altioo uses named accounts, which you create and can switch off at any time, and asks you to delete them at the end of the work.
If an incident may affect your systems or your data, Altioo tells you without delay. The exact deadline is set in the contract or in the data processing agreement. A personal data breach is reported as the data processing agreement and the GDPR require.
Altioo is not certified to ISO/IEC 27001, the international standard for information security. If your supplier security questionnaire asks about it, Altioo answers it question by question, with what it actually does.
The end of an engagement
An engagement ends with a handover, so that your team, or another company, can take the work over:
- the documentation agreed in the proposal;
- the code and settings, in your Git repository if you have one, or in a form agreed with you;
- a handover session with your team;
- Altioo's access removed, and your data returned or deleted, confirmed in writing.
When Altioo is a subcontractor
Altioo also works for another company, which itself holds the contract with its client. In that case, this page changes on a few points:
- the contract and the price are agreed with the company that gives Altioo the work, not with its client. That contract also sets the law and the court, which may differ from the ones above;
- what Altioo builds goes to that company, which passes it on to its client under their own contract. Altioo only reuses general parts if its contract allows it;
- for personal data, Altioo signs a contract with that company that carries its obligations towards its client. That client must also agree to Altioo taking part (Article 28 GDPR);
- the security and confidentiality rules are the end client's. What it, or the company that gives Altioo the work, provides, Altioo uses under its rules; the rest Altioo brings, protected as described above.
Everything else stays the same: a written agreement before the work starts, protected access, and a handover at the end.
Registering Altioo as a supplier
- Company details
- The company name, its company number, which is also its VAT number, and its Peppol ID are on the legal notice page.
- Electronic invoices
- Altioo sends electronic invoices over Peppol, the international e-invoicing network. Between Belgian companies, it is mandatory in most cases. In France, the e-invoicing obligation applies between companies established in France: it doesn't cover an invoice from a Belgian company.
- Checking an invoice
- To check that an invoice or a message really comes from Altioo, read Altioo's official channels.
A question before you start?
An insurance certificate, a question about this page: ask by email.
- info@altioo.com