Last updated: 18 November 2026. Effective from: 18 November 2026.
Agency Billing Hub is a software product developed and operated under the Alphonomic brand by Stjepan Adžaip, based in Novi Travnik, Bosnia and Herzegovina.
The service provider is Stjepan Adžaip, operating under the Alphonomic brand. Business and Legal Information gives the central operator and contact information.
1. Parties, scope and duration
This DPA forms part of the Terms of Service between the business customer identified in its account or order ("Customer") and Stjepan Adžaip, operating under the Alphonomic brand ("Provider"). Contact: Stjepan Adžaip, [email protected].
The Customer is controller of personal data it puts into a product, and the Provider is its processor. If the Customer is itself a processor, it confirms that it has authority to appoint the Provider as subprocessor and to give the instructions described here. The Customer remains responsible for the lawfulness of its instructions, notices and authority to disclose data. The Provider remains responsible for its own duties under data protection law.
This DPA applies only to processing on the Customer's behalf. The Provider's own account administration, billing, marketing and security records are described in the Privacy Policy. The DPA lasts while the Provider processes Customer personal data, including restricted copies awaiting lawful deletion.
Applicable data protection law includes Bosnia and Herzegovina's data protection law and, where applicable, the GDPR. The product annex below states the subject matter, purpose, nature of operations, data categories and data subjects. Special category data, criminal-record data and other restricted data are excluded unless separately agreed with appropriate safeguards.
2. Documented instructions
The Customer instructs the Provider to process data only to supply the selected product, including hosting, retrieval, permitted sharing, email delivery, export, support, backups and deletion as described here. Account settings, authorised actions in the product and lawful written support instructions are documented instructions. Instructions may be sent by an authorised Customer contact to Stjepan Adžaip, [email protected]. These instructions include only international processing expressly identified and lawfully arranged under Section 7.
The Provider will not process Customer personal data for its own advertising or to train its own AI models. No external document-answering AI integration is represented as part of this ABH processing annex.
The Provider will tell the Customer immediately if, in its opinion, an instruction infringes applicable data protection law. It may suspend the affected processing while the parties clarify that instruction. If law requires processing outside the Customer's instructions, the Provider will inform the Customer of that requirement before processing unless the law prohibits notice on important public interest grounds. It will limit any legally required disclosure to what is required.
3. Confidentiality and security
The Provider will ensure that people authorised to process Customer personal data are bound by confidentiality obligations or an appropriate statutory duty. Access must be limited to what is necessary for authorised work, including support and incident response.
The Provider will implement and maintain appropriate technical and organisational measures having regard to the risks, data, available technology and costs. These include access control, secure authentication, protection during transmission, separation of customer records, backup and recovery procedures, and a process for assessing the effectiveness of controls. The factual product measures and known limits appear in the annex. This is a contractual obligation to maintain appropriate measures, not a certification or a guarantee that every risk is eliminated.
Changes to measures must not materially reduce the overall protection of Customer personal data. The Customer is responsible for its users' access choices, lawful public sharing and security of its own devices and credentials.
4. Rights requests and compliance assistance
Taking account of the nature of processing and the information available, the Provider will assist the Customer through appropriate technical and organisational measures with requests for access, correction, erasure, restriction, objection and portability. It will forward requests concerning Customer-controlled data without undue delay and will not answer on the Customer's behalf unless instructed or legally required. The Customer decides the lawful response. Requesters concerning the Provider's own controller records are handled under the Privacy Policy.
The Provider will assist with processing security, breach notification, data protection impact assessments and prior consultation with authorities as required by applicable law. Assistance charges for exceptional bespoke work must be agreed in advance and must not prevent mandatory assistance or compliance with legal deadlines.
5. Personal data breaches
The Provider will notify the Customer without undue delay after becoming aware of a personal data breach affecting Customer personal data. It will not wait for a complete investigation before notifying and will provide updates as information becomes available.
The notice will describe the nature of the breach, affected data and people and approximate numbers where known, likely consequences, measures taken or proposed, and a contact for further information. The Provider will take reasonable steps to contain and remedy the breach, preserve relevant evidence and assist the Customer's assessment. Notice is not an admission of fault. The Customer remains responsible for notifications it must make as controller. Any authority notification period applying to the Customer is not a waiting period for the Provider.
6. Subprocessors
The Customer gives general written authorisation for the subprocessors identified for its product on the Subprocessors page. That page and its approved register form the subprocessor annex to this DPA. It states roles so that payment providers acting independently are not treated automatically as Customer-content subprocessors.
The Provider must impose substantially the same data protection obligations on each subprocessor through a written contract, including appropriate security and assistance duties. It remains responsible to the Customer for the subprocessor's performance. The Provider will give at least 30 days' advance email notice of intended additions or replacements affecting Customer data. The Customer may object on reasonable data protection grounds. The resolution and termination process on the Subprocessors page applies before the affected data is processed by the disputed new provider.
7. Processing locations and transfers
Approved locations, recipients and actual transfer mechanisms are in the Subprocessors page and approved register: The ABH integrations described below. Contracted legal entities, all processing countries, signed processor terms and transfer safeguards require separate verification; source integration alone does not establish approval of those arrangements. Storage and access locations: Hetzner production application and database hosting, and the configured Hetzner Object Storage upload endpoint in Nuremberg, Germany. Operator access from Bosnia and Herzegovina and onward provider processing mean this is not an EU-only arrangement. Processing must stay within those documented instructions and lawful arrangements.
Where applicable law requires a transfer safeguard, the parties must put an appropriate valid arrangement in place before the transfer. This DPA alone is not a set of EU Standard Contractual Clauses, does not execute them, and does not claim that Bosnia and Herzegovina has an EU adequacy decision. Any required clauses, modules, annexes, transfer assessment and supplementary measures must be completed for the actual parties and flow. Legally required transfer clauses prevail over conflicting terms here.
8. Return, deletion and backups
On termination, the Provider will, at the Customer's choice, return Customer personal data in an available usable electronic format or delete it and existing copies, unless applicable law requires retention. The Customer should communicate that choice before instructing irreversible deletion. Where a self-service export is incomplete, the Customer may request the remaining data through support. No incomplete self-service export discharges the Provider's return obligation.
The applicable product retention schedule below and the backup schedule specify how and when deletion and return are completed. The Provider will confirm deletion on request. Data retained because law requires it must be restricted to that purpose and deleted when that requirement ends. Backup copies awaiting scheduled expiry must be protected from ordinary use, and a restoration must reapply relevant deletion instructions. Retention cannot be extended merely for convenience.
Backup expiry and restoration handling: Database backup storage is separate from live records. The inspected remote backup lifecycle expires objects after 90 days; this does not promise complete uploaded-file backup coverage or immediate erasure from backups. Copies retained for lawful needs are restricted from ordinary use.
9. Information, audits and inspections
The Provider will make available all information needed to demonstrate compliance with this DPA and applicable processor duties, and will allow and contribute to audits and inspections by the Customer or an auditor mandated by it. The parties will normally start with current documentation and agree reasonable notice, scope, confidentiality and safeguards for other customers' data.
Routine audits should be arranged during support hours with minimal disruption. These arrangements do not restrict an authority's powers or prevent an audit required by law or reasonably needed after a breach or identified compliance concern. Any agreed allocation of reasonable audit costs must not prevent the exercise of mandatory audit rights. No certification or external audit is represented as existing merely because this DPA is available.
10. Liability, precedence and notices
The Terms' lawful business liability provisions apply between the parties; this DPA does not create an additional contractual cap. Nothing limits a data subject's rights, mandatory compensation rights, a supervisory authority's powers or liability that cannot legally be limited.
For Customer personal data processing, this DPA takes priority over conflicting product sections or general Terms. Mandatory transfer clauses and applicable law take priority over this DPA. Governing law and business venue follow the Terms without limiting mandatory rights. Changes follow the Terms' notice procedure and cannot retrospectively authorise a new processing purpose or an unlawful transfer.
Send instructions, objections and DPA questions to Stjepan Adžaip, [email protected]. The Customer must keep its authorised account and security contact details current.
Product processing annex
Agency Billing Hub
Subject matter and purpose: hosting and operating the Customer's agency or freelance administration workspace, delivering selected email and providing support. Duration: the service period and the verified return and deletion period below.
Operations: collection, organisation, storage, calculation, retrieval, authorised sharing, public link access, transmission of customer-selected email, export and deletion. Data subjects: the Customer's clients, prospective clients, suppliers, staff, contractors and other business contacts. Data categories: names, contact and business details, client and lead records, proposal and contract content, projects, tasks, time records, invoices and recorded payments, expenses, payroll records, notes, attachments and email records supplied by the Customer.
Controls and limits evidenced in application code include authenticated and agency-scoped access, password hashing, rate limiting, consent checks for optional analytics and logged administrative impersonation. Avatars, logos and receipt files use public URLs and are accessible to anyone with the exact link. This exception must be considered before uploading confidential material. Support attachments use a separate private flow. The personal export contains selected records and row limits; it is not a complete workspace return tool.
ABH does not collect payments on the Customer's own invoices. Polar bills the ABH subscription. Configured SMTP delivers email; storage and infrastructure providers and their roles appear in the approved register. Processing locations and subprocessor changes follow Sections 6 and 7. Retention and completion periods: Self-registered, unverified owner accounts become eligible for cleanup after 72 hours; cleanup runs on selected authentication requests, not at an exact expiry time. The inspected implementation preserves invited users. System logs older than 90 days are purged by a running scheduler. Marketing attribution lookup keys are cleared after the 30-day window and touch records are deleted after 13 calendar months by that scheduler. Code also provides cleanup for support tickets closed for at least 30 days, but a running schedule for that endpoint was not verified. No general automatic deletion period for customer business records, uploaded files or accounting records was established by this inspection..