Clear terms make better projects.

What these terms cover

These terms apply when you use priviontechnology.com or engage Privion Technologies to design or develop a mobile app, website, or related digital product. “You” means the person or organisation commissioning the work. “We”, “us”, and “Privion” mean Privion Technologies.

A project begins only when we have both accepted a written proposal or project agreement and received the initial payment. The project document records the deliverables, assumptions, estimated schedule, service fee, and any specific support arrangements. If that signed document conflicts with these general terms, the signed project document controls for that project.

Nothing on this website is a binding quotation. Early estimates can change after discovery reveals the actual scope or technical requirements.

How we work together

We agree to perform the work with reasonable care and skill and to communicate material decisions, risks, and delays. You agree to give us accurate requirements, timely feedback, necessary access, and one person authorised to approve decisions for your organisation.

You are responsible for the legality and accuracy of the text, images, trademarks, user data, business rules, and other material you supply. You confirm that we are allowed to use those materials for the project. Delays in access, content, approvals, or feedback may move the delivery date and may create additional cost if the team must pause or reschedule work.

Our payment structure

First 50%: booking and commencement

You pay 50% of Privion's agreed service fee before development starts. This reserves capacity, funds discovery and early delivery, and confirms your instruction to proceed. Once work has started, this payment is not automatically refundable; any refund is based on work completed, committed capacity, and non-cancellable costs.

Development costs while we build

Development costs are separate from Privion's service fee unless the proposal expressly includes them. They can include hosting, domains, cloud infrastructure, paid APIs, app-store accounts, third-party licences, email services, payment-provider setup, specialist tools, purchased assets, testing devices, or other resources the product needs. We will identify material costs for approval before committing to them. You must fund approved costs when requested so development is not blocked.

Final 50%: completion

The remaining 50% of our service fee becomes due when the agreed deliverables are complete and made available for final review or handover. Minor defects that do not prevent normal use do not postpone the entire final payment; we will record and correct covered defects within a reasonable period.

Invoices and late payment

Invoice currency, tax treatment, and due dates appear in the proposal or invoice. You must tell us promptly if an invoice is genuinely disputed. We may pause work, withhold deployment or handover, disable unpaid support services, and adjust the schedule while an undisputed amount is overdue. You remain responsible for approved third-party commitments already made for the project.

Software has ongoing costs

A finished product may still cost money each month or year to remain online and functional. Typical charges include servers and databases, domains, cloud storage, email or SMS delivery, maps, AI or other APIs, payment processing, monitoring, security services, app-store memberships, software licences, backups, and maintenance.

We can estimate known running costs, but third-party providers set their own prices and may change them. Usage growth can also increase costs. Where practical, accounts should be opened in your name so you retain control and pay providers directly. Failure to pay a provider can suspend or remove part of the software, and Privion is not responsible for an outage caused by an unpaid or discontinued third-party service.

Scope, revisions, and change requests

The agreed scope is the list of deliverables in the project proposal—not every idea discussed before or during development. Reasonable clarification and the revision rounds stated in the proposal are included. A new feature, changed workflow, new platform, additional revision round, new integration, or change to an approved design may be a change request.

We will explain the likely effect of a change on price and timing before carrying it out. A change becomes part of the project when both sides approve it in writing, including by email. If urgent investigation is needed before a firm estimate is possible, we may agree a paid discovery or time-based task first.

Timelines, testing, and acceptance

Delivery dates are good-faith estimates unless the project agreement explicitly makes a date fixed. Software work depends on timely decisions, third-party reviews, app-store approvals, provider availability, and technical findings that are not always predictable. We will tell you when a material delay becomes known.

You must test the completed work against the agreed scope and report reproducible defects during the review period stated in the project agreement. If no period is stated, you should review promptly and without unreasonable delay. A defect is a failure to perform materially as agreed; a new preference, feature, or changed requirement is not a defect.

App stores, payment processors, hosting providers, and other platforms control their own approvals and availability. We can prepare and submit work correctly, but we cannot guarantee that a third party will approve it by a particular date or continue offering a service unchanged.

Ownership and licences

After all project invoices and approved costs are paid, you receive the ownership or licence rights to the bespoke deliverables described in the project agreement. Until full payment, deliverables remain under Privion's control and may not be deployed, sold, or transferred without our written permission.

Privion retains ownership of pre-existing know-how, internal tools, generic code, reusable components, methods, and improvements that are not unique to your business. We grant the rights reasonably needed to use those elements as part of the finished product. Open-source software, fonts, stock assets, APIs, and other third-party materials remain subject to their own licences and terms.

We will not publish confidential project material. We may identify completed work in our portfolio only where we have permission or where the product and our involvement are already public.

Support, maintenance, and warranties

We will address reproducible defects covered by the agreed scope during any warranty or support period stated in the project agreement. This does not cover problems caused by changes made by others, unsupported devices, client-supplied systems, third-party outages, compromised credentials, misuse, or failure to install required updates.

Ongoing maintenance is a separate service unless expressly included. Without a maintenance agreement, we do not continuously monitor the product, apply platform updates, renew services, update content, or guarantee compatibility with future operating-system, browser, API, or store-policy changes.

Pausing or ending a project

Either side may end a project for a serious breach that is not corrected after reasonable written notice. You may also cancel for convenience by giving written notice. In that case, you must pay for work performed, time reserved that cannot reasonably be reassigned, approved expenses, and non-cancellable third-party commitments up to the end date.

If a project is inactive because we are waiting for you for an extended period, we may close or reschedule it after notice. Restarting depends on team availability and may require a revised estimate. Once outstanding amounts are paid, we will provide completed, paid-for work in its then-current state where reasonably practicable.

Confidentiality and data protection

Each side must protect non-public business, product, technical, and commercial information received from the other and use it only for the project. This does not cover information already public, independently developed, lawfully received elsewhere, or required to be disclosed by law.

Each side remains responsible for its own data-protection duties. If Privion will process personal data on your behalf inside the product, the parties will agree the necessary roles, safeguards, and data-processing terms before that processing begins.

Responsibility when something goes wrong

Neither side is responsible for delay caused by events reasonably outside its control, provided the affected side communicates and takes reasonable steps to reduce the impact. You remain responsible for business decisions, regulatory approvals, backups or operational controls allocated to you, and the way you use the delivered software.

To the extent permitted by law, Privion is not liable for indirect or consequential loss, lost profit, lost opportunity, or loss caused by third-party services. Any project-specific liability cap will be stated in the project agreement. Nothing in these terms excludes liability that cannot legally be excluded, including liability for intent, gross negligence, injury to life or health, or mandatory consumer rights.

Using this website

You may browse and share links to this website for lawful purposes. Do not attempt to interfere with the site, bypass security, submit malicious material, impersonate someone, or use our content or branding in a misleading way. Website content is general information, not a promise that a particular service, price, or timeline is available.

We may update, suspend, or remove website content and external links. Third-party sites have their own terms. Privion's name, visual identity, site design, copy, and original materials remain protected by applicable intellectual-property law.

Applicable law and final points

The project agreement should identify the governing law and dispute process. If it does not, German law applies to the extent legally permitted. Mandatory protections available to consumers in their home country are not displaced by this clause.

If one provision cannot be enforced, the rest remain effective. A failure to enforce a term once is not a waiver. Neither side may transfer a project agreement without the other's consent, except as part of a lawful business reorganisation that does not reduce the other side's rights.

We may update these website terms for future use. Changes do not rewrite an existing signed project agreement unless both sides agree.