Terms of Service

1.1. Certive is the Document Trust Layer service developed and operated by Baliola, accessible at certive.id and app.certive.id.

1.2. Baliola is PT Baliola Adi Maha Duta, the legal entity that operates Certive together with other products in its ecosystem, including the Mandala Application Chain blockchain infrastructure.

1.3. Mandala Chain is the blockchain network used by Certive to record documents’ digital fingerprints on a permanent, tamper-proof basis.

1.4. A User is any person who creates an account and uses the Certive service, whether as a Document Holder, an Issuer, or a member of an Organization.

1.5. Verifier is anyone who checks the authenticity of a document through a Certive verification link, with or without an active account.

1.6. Issuer is a User who issues a Document through Certive, either as an individual or on behalf of an Organization.

1.7. Document Holder (Holder) is a User who receives and holds a Document issued to them.

1.8. An Organization is an entity formed within Certive by a User, made up of one or more Users with their respective roles, for the purpose of issuing Documents collectively on behalf of an institution.

1.9. Document is any digital file issued by an Issuer through Certive to have its integrity and provenance recorded.

1.10. Digital Fingerprint (Hash) is a unique representation of a Document’s contents, generated through a computation process on the Issuer’s own device, used by Certive to prove a Document’s integrity without ever storing the Document itself.

1.11. Verification Link is the unique link accompanying every issued Document, which anyone can use to check that Document’s integrity and provenance.

1.12. Issuer Trust Level is the classification displayed by Certive indicating the extent to which an Issuer’s identity has been reviewed, as set out in Article 9.

1.13. Crypto Wallet is a blockchain-based digital wallet that may optionally be linked to a Certive account, as set out in Article 12.

1.14. KPG Token is the native token of the Mandala Chain network that Users may use to take part in the Web3 Staking program, as set out in Article 15.

1.15. Service Plan is the paid or free tier chosen by a User or Organization to use Certive, as set out in Article 14.

2.1. These Terms of Service take effect once You complete the Certive account registration process, and remain in effect for as long as You hold an active account or use the Certive service in any capacity, including as a Verifier without an account.

2.2. Baliola may update these Terms of Service from time to time as set out in Article 21. Continued use of the service after an update takes effect is deemed acceptance of that change.

2.3. If You use Certive as a member of an Organization, these Terms of Service apply to You personally and to the Organization to which You belong, to the extent relevant to Your role within it.

3.1. Certive is a service that helps institutions issue official documents digitally so that anyone can verify that a file has not been altered since it was first issued, and trace who issued it.

3.2. Certive is intended primarily for notaries and law firms, universities, government ministries/agencies, state-owned enterprises, and private enterprises that issue, distribute, or verify official documents between institutions.

3.3. The original Document file is never stored on Certive’s servers. Each Document is processed directly on the Issuer’s device to generate a Digital Fingerprint, and only that Digital Fingerprint is permanently recorded on the Mandala Application Chain network. The Document’s owner retains the original file.

3.4. Users login to Certive using email and password. There is no requirement to understand blockchain technology or to hold a Crypto Wallet to use Certive’s core service, including to issue Documents.

3.5. Certive proves that a file has not changed since it was issued, and who issued it. Certive does not prove that the contents of a Document are true, and does not prove that an Issuer is a legally valid party, unless that Issuer has reached the highest trust level set out in Article 9. See Article 17 for full restrictions.

4.1. Each User is identified by a personal or corporate email address. Before being able to issue or hold a Document, a User’s email address must be verified through a link sent to their inbox.

4.2. Account registration is not currently open to the public. During this launch phase, new accounts can only be created through one of the following three paths.

4.3. Baliola may conduct a manual eligibility review of prospective Issuers, including verification of professional registration numbers or business entity documents, particularly for the notary and law firm segment, as a basis for raising an Issuer’s Trust Level as set out in Article 9.

4.4. For account security, Certive temporarily restricts repeated failed login attempts within a short period, and a login session automatically expires after a certain period, requiring the User to log in again periodically.

4.5. You are fully responsible for the confidentiality of Your account password and for any activity that occurs through Your account. Promptly notify Baliola through the channel in Article 24 if You suspect unauthorized access to Your account.

4.6. Ownership of a Crypto Wallet is entirely optional and is never a requirement to create an account, hold any role, or use any feature on Certive, including issuing Documents.

5.1. Every active account automatically holds the role of Document Holder, entitled to receive Documents issued to them, view the full history of their own Documents, and share Verification Links with others.

5.2. Other roles are contextual, as follows.

5.3. A person may issue a Document without owning a Crypto Wallet, provided their email address has been verified, their account is not suspended, and they are issuing either as an individual or as a member of an Organization that has granted them permission to issue.

5.4. The ability to issue a Document is separate from the Trust Level displayed to a Verifier. A person who has just verified their email may issue a Document, but that Document will display the “Unverified Issuer” label until their trust level rises as set out in Article 9.

5.5. There are two levels of access for Verifiers. A Verifier who is logged in (authenticated) receives the full verification result plus a limited history of that Document, including when it was issued, any changes or revocation that have occurred, and their own verification history. A Verifier who is not logged in (public) receives only the core verification result, without any Document history.

6.1. Any User with an active account may establish an Organization within Certive. The Organization’s founder automatically becomes its Owner. Other members are invited by email, and a single person may belong to multiple Organizations with different roles in each.

6.2. Roles within an Organization are set out as follows.

6.3. An Organization on the Enterprise Service Plan must maintain at least two active Admins at all times. Certive will refuse any request to remove an Admin that would bring the number of active Admins below two, to prevent an Organization from being locked out without a manager.

6.4. If a member is removed from an Organization, every Document they previously issued on the Organization’s behalf remains valid and permanently recorded. A change in membership does not invalidate issuance records that have already occurred.

6.5. An Organization may optionally require its members to use an email address on its verified domain when issuing Documents on the Organization’s behalf.

6.6. An Organization’s Owner and Admins are responsible for ensuring that every member granted issuing permission understands and complies with these Terms of Service, including the Issuer responsibility statement in Article 7.5.

7.1. When an Issuer issues a Document, the following process applies in sequence.

1. The Document file is processed directly on the Issuer’s own device to generate its unique Digital Fingerprint. The original file is never sent or stored on Certive’s servers.
2. The Issuer fills in recipient information, consisting of an email address, Document type, a brief description, and any other fields required based on the user’s needs.
3. Certive checks the Issuer’s eligibility as set out in Article 5.3. An issuance that does not meet the requirements is rejected with a clear reason.
4. The Digital Fingerprint is checked against Certive’s internal registry to confirm it has not been recorded before. A Document whose Digital Fingerprint is identical to a previously issued Document is rejected as a duplicate.
5. Once it passes the duplicate check, the Digital Fingerprint is permanently and immutably recorded on the Mandala Application Chain network through Certive’s additional security mechanism. Once successful, anyone, including Baliola itself, cannot alter or delete this record.
6. Once the recording is confirmed successful, the Document becomes active, and the recipient receives an email notification containing a Verification Link that can be used at any time in the future.

7.2. If recording fails due to a momentary technical disruption, the system automatically retries. A Document is not displayed as “active” until its recording is confirmed successful.

7.3. Bulk Issuance. Certive allows an Issuer to upload and issue several Documents at once within a single issuance batch, with a minimum of two and a maximum of five hundred Documents per batch, unless otherwise specified under the Enterprise Service Plan. Each Document within a batch remains individually verifiable by its own recipient, and each recipient receives their own separate Verification Link.

7.4. Duplicate Prevention. Each file may only be recorded once on Certive. Any attempt to issue a file whose content is identical to an already-recorded Document will be rejected. The duplicate-rejection message does not disclose the identity of the other Issuer or the metadata of the Document recorded earlier.

7.5. Issuer Responsibility Statement. Before being able to issue a Document for the first time, every Issuer must agree to a responsibility statement affirming that the Issuer bears full responsibility for the validity, factual accuracy, and propriety of any Document they issue through Certive. Certive functions as an integrity-recording service, not as a party that guarantees or authenticates the contents of a Document.

7.6. Every issued Document is clearly recorded with its Issuer’s identity. There is no anonymous issuance on the Certive system.

8.1. Anyone, whether or not they hold an account, may verify a Document through its accompanying Verification Link by uploading a copy of the file to be checked.

8.2. Certive checks whether the Digital Fingerprint of the uploaded file matches the one recorded when the Document was first issued. Verification results are available in under sixty seconds under normal operating conditions.

8.3. A verification result is never presented as a single “Genuine” label. The result is always divided into three independent signals, as follows.

8.4. The fact that a file is proven unchanged is never, by itself, sufficient to display a “Genuine” or “Safe” label. The Issuer Trust Level is always displayed alongside it, with equal weight: a fraudulent Document issued by an irresponsible party will still display as “intact” if it has not been altered since it was first issued.

8.5. Possible results shown to a Verifier include: an intact file with an Unverified Issuer, an intact file with Registered Issuer status, a revoked Document, a file that does not match or has been altered, an Issuer currently suspended, a Document not found, and a Document still being recorded.

8.6. Every verification result page includes an explicit explanation of what the result proves and what it does not prove, as further detailed in Article 17.

9.1. Because full legal identity verification of every Issuer is not yet available at this stage of the service, Certive displays an Issuer Trust Level as the following tiered scale.

9.2. The “Registered Issuer” level is not legal identity verification and is not equivalent to the “Identity Verified” level. This status only states that the Certive team has carried out a manual review of that Issuer’s eligibility.

9.3. Accountability as a Protective Layer. While full legal identity verification is not yet available, Certive relies on three accountability mechanisms: a mandatory responsibility statement for every Issuer before their first issuance, full traceability of the Issuer’s identity on every Document they issue, and the abuse reporting and suspension mechanism set out in Article 11.

9.4. Baliola has the right to review and raise an Issuer’s Trust Level at its sole discretion based on supporting documents submitted by the Issuer, and has the right to refuse such an increase without being obligated to provide the Issuer with a detailed explanation, provided the decision is made in good faith.

10.1. An Issuer may revoke a Document they have issued, together with the reason for revocation. The revocation is permanently recorded on the Mandala Application Chain network and cannot be undone.

10.2. After a Document is revoked, every subsequent verification of that Document displays a “Revoked” status together with the reason provided by the Issuer at the time of revocation.

10.3. Revocation is performed one Document at a time. Bulk revocation of every Document within a single issuance batch at once is not supported at this stage of the service.

10.4. Revocation does not erase the record that the Document was ever issued. The original issuance record remains permanently stored on the blockchain as part of the audit trail; only its validity status changes.

11.1. Any Verifier or Document Holder who suspects abuse, including the issuance of a fraudulent Document or impersonation of an Issuer’s identity, may report it to Baliola through the channel in Article 24.

11.2. The Certive team reviews every report. If a report is found to be valid, Baliola has the right to suspend the relevant Issuer’s ability to issue new Documents, without prior notice if the circumstances are urgent.

11.3. Documents issued before a suspension remain permanently recorded and are not deleted, but are displayed to Verifiers with a warning that the Issuer is currently suspended.

11.4. Baliola has the right, at its sole discretion, to suspend or terminate the access of any User found to have violated these Terms of Service, as further set out in Article 20.

12.1. A User already familiar with blockchain technology may optionally link their Crypto Wallet to their Certive account through the account settings menu.

12.2. Linking a Crypto Wallet is never a requirement for using any feature on Certive, including issuing Documents. Its benefit is purely additional: it strengthens the evidence that the owner of that crypto key carried out an issuance, and it serves as a prerequisite for joining the Web3 Staking program under Article 15.

12.3. The User bears full responsibility for the security of their Crypto Wallet’s private key. Baliola does not store, does not have access to, and is not responsible for any loss of access to a User’s personal Crypto Wallet.

13.1. The original Document file is never stored on Certive’s servers in any form. This is a core, permanent privacy commitment of the Certive service.

13.2. Certive only stores the Digital Fingerprint of every Document that has ever been successfully issued, within an internal registry used for the duplicate check set out in Article 7.4. This registry never stores the original file, only its digital fingerprint.

13.3. What is recorded on the blockchain is not the raw Digital Fingerprint, but a derived value that Baliola first processes using Certive’s secret key. An outside party who only holds a copy of a file cannot independently compute and match that recorded value without Certive’s involvement. This mechanism provides an additional privacy benefit. Verification against the blockchain still requires Certive’s active involvement as the holder of that key, and Baliola is developing governance and continuity procedures for this key, with any material developments to be communicated to Users.

13.4. Passwords and other sensitive User data are stored using industry-standard encryption, and all data communication between a User’s device and the Certive system is encrypted.

13.5. Certive processes User personal data in accordance with Indonesia’s Personal Data Protection Law, applying the principle of data minimization: only collecting and storing the data necessary to operate the service.

13.6. Access to the Digital Fingerprint registry is internally restricted, and every access to it is logged as part of Baliola’s security audit trail.

13.7. Certive’s data and privacy practices are set out in further detail in the Certive Privacy Policy, which forms an integral part of these Terms of Service.

14.1. Certive is offered under a monthly subscription model with four Service Plan tiers as described in the table below. Prices are set in United States Dollars (USD) as the global standard, and may be adjusted to Indonesian Rupiah or other billing terms based on the applicable commercial agreement, particularly for institutional customers in Indonesia.

14.2. The Free plan is provided at no cost to individual users, students, and freelancers, with an issuance quota of one Document per recording transaction (single stamp), without bulk issuance functionality.

14.3. The Starter/Pro and Business plans are intended for agencies, small and medium enterprises, independent notaries, universities, and mid-size local government and state-owned enterprise institutions, with larger quotas and bulk issuance capacity as set out in the table above.

14.4. The Enterprise plan is intended for central government institutions and large corporations with document quota, bulk issuance capacity, and Admin seat needs that are tailored specifically to them. The pricing and service terms of the Enterprise plan are set out in a separate commercial agreement between Baliola and the relevant customer, with a base price starting from $499 per month.

14.5. Baliola has the right to change the structure and amount of Service Plan pricing from time to time. Pricing changes will be communicated to affected Users within a reasonable period before taking effect, and will not apply retroactively to a billing period already in progress.

14.6. If usage on an account or Organization exceeds the document quota of its chosen Service Plan, the User may upgrade to a higher Service Plan, join the Web3 Staking program under Article 15 if eligible, or contact Baliola for custom adjustment needs through the channel in Article 24.

15.1. Certive offers a Staking Sweeteners program using the KPG Token native to the Mandala Chain network, as a bridge between Web2-based institutional Users and the Web3 ecosystem. A User who has linked their Crypto Wallet as set out in Article 12 may lock a quantity of KPG Tokens through Certive’s smart contract to obtain a service upgrade without any additional cost in fiat currency.

15.2. Core rule: staking benefits do not stack. A User may activate only one tier of service upgrade at a time, based on the quantity of KPG Tokens locked in their Crypto Wallet.

15.3. The tiers of the Web3 Staking program are set out as follows.

15.4. KPG Tokens locked through Certive’s smart contract cannot be withdrawn before the minimum lock period ends. The User bears full responsibility for the risk of fluctuations in the value of KPG Tokens during that lock period.

15.5. The Web3 Staking program is optional, an added value on top of the core Service Plan. A user who does not join this program still receives the full benefits of the Service Plan they have chosen as set out in Article 14, without any reduction whatsoever.

15.6. Baliola has the right to change the terms of the Web3 Staking program, including the lock requirement amounts and the benefits granted, with notice to affected Users within a reasonable period before taking effect.

16.1. Paid Service Plans are billed periodically according to the billing cycle selected at registration or upon upgrading the Service Plan, unless otherwise specified in a separate commercial agreement for the Enterprise plan.

16.2. A Service Plan upgrade takes effect immediately once payment is confirmed successful. A Service Plan downgrade takes effect at the start of the next billing cycle, and does not reduce fees already paid for the billing cycle currently in progress.

16.3. All fees already paid are non-refundable, unless otherwise specified in writing by Baliola or required under applicable law.

16.4. Repeated payment failure may result in an account or Organization being downgraded to the Free plan or temporarily suspended until payment is resolved, with prior notice to the relevant User.

17.1. Certive provides a service for recording the integrity and provenance of Documents. Certive proves who issued a Document, when it was issued, and that its file has not changed since that time, making the Issuer traceable and accountable. Certive does not state that the contents of a Document are true.

17.2. Specifically, Certive does not resolve, and cannot be claimed to resolve, the following matters.

• The substantive truth or accuracy of a Document’s contents.
• The legal validity of an Issuer, unless that Issuer has reached the “Identity Verified” level set out in Article 9, which is not yet active at the time these Terms of Service were drafted.
• Abuse by an Issuer whose identity is legitimate but who acts in bad faith, including issuing a Document whose contents are untrue.

17.3. Every verification result displayed by Certive is accompanied by an explicit explanation of what it proves and what it does not prove. A Verifier who has doubts about the substantive validity of a Document is advised to confirm directly with the Issuer through that Issuer’s official channels, outside the Certive system.

17.4. The Certive service is provided on an “as is” and “as available” basis. Baliola strives to maintain service availability with high reliability during operating hours, but does not guarantee that the service will always be free of disruptions, errors, or delays.

17.5. To the extent permitted by applicable law, Baliola’s liability for losses arising from the use of the Certive service is limited to the total fees the User has paid to Baliola for the relevant Service Plan over the preceding twelve months. Baliola is not liable for any indirect losses, consequential losses, or loss of profit arising from the use of, or inability to use, the Certive service.

17.6. The limitation in Article 17.5 does not apply to losses arising from Baliola’s gross negligence or willful misconduct, or in other cases where liability cannot be limited under applicable law.

18.1. Users must provide true and accurate information when registering an account and while using the Certive service.

18.2. Users are prohibited from issuing a Document they know, or reasonably should suspect, contains false or misleading information, or that infringes the rights of another party, including intellectual property rights and privacy rights.

18.3. Users are prohibited from using the Certive service for any purpose that violates applicable law in Indonesia or in the jurisdiction where the User is located.

18.4. Users are prohibited from attempting to access, disrupt, or damage Certive’s systems, networks, or infrastructure, including attempting to access the Digital Fingerprint registry or Certive’s secret key without lawful authorization.

18.5. Users are prohibited from using another party’s account without permission, or from misusing the invitation mechanism to register an account for a party not authorized to receive that invitation.

18.6. A violation of this Article 18 may cause suspension or termination of access as set out in Articles 11 and 20, without prejudice to Baliola’s right to pursue any other available legal remedy.

19.1. All intellectual property rights in the Certive platform, including its software code, interface, logo, and the Certive trademark, are owned by Baliola or its licensors, and are protected under applicable intellectual property law.

19.2. These Terms of Service do not grant the User any ownership rights in the Certive platform, other than a limited, non-exclusive, non-transferable right to access and use the Certive service in accordance with these Terms of Service.

19.3. Copyright and other intellectual property rights in the contents of any Document issued through Certive remain with that Document’s rightful owner. Certive only records that Document’s Digital Fingerprint and claims no rights whatsoever over its contents.

19.4. A User on the Premium-Boost plan who obtains the white-labeling feature set out in Article 15.3 still acquires no ownership rights whatsoever in the underlying Certive technology or infrastructure behind that feature. The right to use a custom domain applies only for as long as the relevant KPG Token lock period remains in effect.

20.1. A user may stop using the Certive service at any time by closing their account through the account settings menu, or by contacting Baliola through the channel in Article 24.

20.2. Baliola has the right to suspend or terminate a User’s access to the Certive service, at any time and with or without prior notice, in the event of a violation of these Terms of Service, suspected abuse as set out in Article 11, or a legal obligation requiring it to do so.

20.3. Termination of an account does not erase any issuance, revocation, or verification record already permanently recorded on the blockchain prior to that termination, given the permanent and tamper-proof nature of that record as set out in Article 3.3.

20.4. Articles 13, 17, 19, and 22 remain in effect after termination of the service, to the extent relevant to obligations or rights that arose before that termination.

21.1. Baliola has the right to change, add to, or discontinue features of the Certive service from time to time to improve service quality and security.

21.2. Baliola has the right to update these Terms of Service at any time. Material changes will be communicated to Users through their registered email or a notice within the Certive platform, at least seven calendar days before taking effect.

21.3. If a User does not agree to a change to these Terms of Service, the User may stop using the service as set out in Article 20 before that change takes effect. Continued use of the service after the effective date of a change is deemed acceptance of that change.

22.1. These Terms of Service are made and interpreted under the laws of the Republic of Indonesia.

22.2. Any dispute arising from or relating to these Terms of Service will first be resolved through good-faith deliberation to reach an agreement between the parties.

22.3. If resolution through deliberation is not reached within a reasonable period, the dispute will be settled through the District Court (Pengadilan Negeri) with jurisdiction over Baliola’s legal domicile, without prejudice to the parties’ right to pursue any other dispute resolution mechanism agreed in writing.

23.1. If any provision of these Terms of Service is held invalid or unenforceable by a court of competent jurisdiction, the remaining provisions of this document remain in full force and effect.

23.2. Baliola’s failure to enforce any right or provision of these Terms of Service shall not be construed as a waiver of that right at a later time.

23.3. These Terms of Service, together with the Certive Privacy Policy and any separate commercial agreement applicable to the Enterprise plan, constitute the entire agreement between the User and Baliola regarding use of the Certive service, and supersede any prior oral or written agreement on the same subject.

23.4. A User may not transfer or assign their rights and obligations under these Terms of Service to another party without Baliola’s prior written consent. Baliola may assign its rights and obligations under these Terms of Service in connection with a reorganization, merger, or transfer of Baliola’s business, with notice to Users.

24.1. Any question, complaint, or report of suspected abuse relating to the Certive service, including matters set out in Article 11, may be submitted through email: support@baliola.io.

24.2. Baliola responds to every complaint received within a reasonable period, and follows up on abuse reports in accordance with the review procedure set out in Article 11.