Terms of Service

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

1.2. Baliola is PT Baliola Adi Maha Duta, the legal entity hosting Certive along with other products within its ecosystem, including the Mandala Application Chain blockchain infrastructure.

1.3. Mandala Chain is the blockchain network used by Certive to record document digital fingerprints permanently and tamper-resistantly.

1.4. User is any person who creates an account and uses Certive services, whether as a Document Holder, Publisher, or Organization member.

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

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

1.7. Document Holder (Holder) is a User who receives and stores a Document issued for them.

1.8. Organization is an entity formed within Certive by a User, comprising one or more Users with their respective roles, to issue Documents collectively on behalf of an institution.

1.9. Document is any digital file issued by a Publisher via Certive to record its integrity and provenance.

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

1.11. Verification Link is a unique link accompanying each issued Document, which anyone can use to check the integrity and provenance of that Document.

1.12. Publisher Trust Level is the classification displayed by Certive regarding the extent to which a Publisher's identity has been reviewed, as regulated in Article 9.

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

1.14. KPG Token is the native token of the Mandala Chain network that Users can use to participate in the Web3 Staking program as regulated in Article 15.

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

1.16. Certificate of Document Integrity is an official digital proof document in PDF format issued by the Certive system, containing document metadata summary, validity status (STAMPED), full identity details of the Publisher and Organization, public verification QR code, and blockchain transaction recording proof (Transaction Hash) proving document integrity and origin.

1.17. Organization Cloud Storage is a third-party cloud-based storage service (such as Google Drive) connected to an Organization account on Certive, functioning to automatically store original document files that have been stamped under the full control and ownership rights of that Organization.

2.1. These Terms and Conditions apply from the time you complete the Certive account registration process, and remain effective as long as you have an active account or use Certive services, including as a Verifier who does not have an account.

2.2. Baliola may update these Terms and Conditions from time to time as regulated in Article 21. Continued use of the service after updates take effect shall be considered your agreement to such changes.

2.3. If you use Certive as a member of an Organization, these Terms and Conditions apply to you personally as well as to the Organization under 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 primarily intended for notaries and law firms, universities, ministries/government agencies, State-Owned Enterprises (SOEs/BUMN), and private enterprises that issue, distribute, or verify official inter-institutional documents.

3.3. Original Document files are never stored on Certive servers. Each Document is processed directly on the Publisher's device to generate a Digital Fingerprint, and only this Digital Fingerprint is recorded permanently to the Mandala Application Chain network. Document owners always retain their original files.

3.4. Users log into Certive using an email address and password. There is no requirement to understand blockchain technology or possess a Crypto Wallet to use Certive's core services, including issuing Documents.

3.5. Certive proves that a file has not changed since issuance and who issued it. Certive does not prove that the content of the Document is correct, and does not prove that the Publisher is a legally valid party, unless the Publisher has achieved the highest trust level as regulated in Article 9. See Article 17 for full limitations.

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

4.2. Account registration is currently not 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 manual eligibility reviews for prospective Publishers, including checking professional registration numbers or business entity documents, especially for notary and law firm segments, as a basis for increasing the Publisher Trust Level as regulated in Article 9.

4.4. For account security, Certive temporarily limits repeated failed login attempts within a short timeframe, and login sessions automatically expire after a certain period, requiring Users to log back in periodically.

4.5. You are fully responsible for maintaining the confidentiality of your account password and for any activity that occurs through your account. Immediately report to Baliola via the channel in Article 24 if you suspect unauthorized access to your account.

4.6. Ownership of a Crypto Wallet is completely optional and is never a prerequisite to creating an account, holding any role, or using any feature in Certive, including issuing Documents.

5.1. Every active account automatically acts as a Document Holder, entitled to receive Documents issued to them, view their full Document history, and share Verification Links with other parties.

5.2. Other roles are contextual as follows.

5.3. A person can issue Documents without holding a Crypto Wallet, provided their email address is verified, their account is not suspended, and they publish as an individual or as a member of an Organization granted publishing permissions.

5.4. The ability to issue Documents is separate from the Trust Level displayed to Verifiers. Someone who has just verified their email can issue Documents, but those Documents will display with the label “Unverified Publisher” until their trust status is elevated as regulated in Article 9.

5.5. There are two access levels for Verifiers. Verifiers logged in with an account (authenticated) obtain complete verification results along with limited Document history, including when the Document was issued, any changes or revocations that occurred, and their own verification history. Verifiers not logged in with an account (public) only obtain core verification results without Document history.

6.1. Any User with an active account can establish an Organization in Certive. The founder of the Organization automatically becomes the Owner. Other members are invited via email, and one person can belong to multiple Organizations with different roles in each.

6.2. Roles within an Organization are configured as follows.

6.3. Organizations on Enterprise Service Plans must maintain at least two active Admins at all times. Certive will reject requests to delete Admins that would cause the active Admin count to fall below two, to prevent Organizations from being locked without managers.

6.4. If a member is removed from an Organization, all Documents previously issued by them on behalf of that Organization remain valid and recorded permanently. Membership changes do not invalidate past issuance records.

6.5. Organizations may optionally require members to use email addresses on verified domains when issuing Documents on behalf of the Organization.

6.6. The Organization Owner possesses exclusive authorities that cannot be accessed by other roles, including:

• Connect, configure, or disconnect Organization Cloud Storage (Google Drive) integrations.
• Transfer primary ownership of the Organization to another user.
• Submit a request for permanent deletion of the Organization account from the Certive platform by contacting Baliola through the official channel in Article 24.

6.7. Organization Owners and Admins are responsible for ensuring that every member granted issuance permissions understands and complies with these Terms and Conditions, including the issuance responsibility declaration in Article 7.5.

7.1. When a Publisher issues a Document, the following sequence applies:

1. Document files are processed directly on the Publisher's own device to generate a unique Digital Fingerprint. Original files are never sent or stored on Certive servers.
2. The Publisher fills in recipient information, including email address, Document type, short description, and other fields according to user requirements.
3. Certive checks Publisher eligibility as regulated in Article 5.3. Issuance failing to meet requirements is rejected with clear reasons.
4. The Digital Fingerprint is checked against Certive's internal registry to ensure it has not been recorded previously. Documents whose Digital Fingerprints match previously issued Documents are rejected as duplicates.
5. Upon passing duplicate checks, the Digital Fingerprint is recorded permanently and tamper-resistantly to the Mandala Application Chain network via Certive's additional security mechanism. This recording cannot be altered or deleted by anyone once confirmed, including Baliola itself.
6. Once recording is confirmed, the Document achieves active status, and the recipient receives an email notification containing a Verification Link usable at any time in the future.

7.2. If recording fails due to temporary technical disruptions, the system retries automatically. The Document is not displayed as “active” until recording is successfully confirmed.

7.3. Mass Issuance. Certive allows Publishers to upload and issue multiple Documents simultaneously in a single issuance batch, ranging from a minimum of two to a maximum of five hundred Documents per batch, unless specified otherwise in Enterprise Service Plans. Each Document within a batch remains individually verifiable by its respective recipient, and each recipient receives a separate Verification Link.

7.4. Duplicate Prevention. Each file can only be recorded once in Certive. Attempts to issue files with content identical to previously recorded Documents will be rejected. Duplicate rejection messages do not reveal the identity of other Publishers or metadata of previously recorded Documents.

7.5. Publisher Responsibility Declaration. Before issuing Documents for the first time, every Publisher must agree to a responsibility declaration confirming that the Publisher bears full responsibility for the validity, truthfulness of content, and propriety of issuing Documents through Certive. Certive functions as an integrity recording service, not as a party guaranteeing or attesting to Document content.

7.6. Every issued Document is recorded clearly with the Publisher's identity. There is no anonymous issuance in the Certive system.

7.7. Certificate of Document Integrity Feature. Users or Organizations that have successfully issued a Document can generate and download a Certificate of Document Integrity in PDF format. This certificate serves as an official proof of validity sheet equipped with a QR Code for quick public verification, metadata summary, full issuer identity, and blockchain recording details.

8.1. Anyone, with or without an account, can verify a Document via the Verification Link that accompanies it 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. Verification results are never presented as a single "Authentic" label. Results are always broken down into three independent signals as follows.

8.4. Proven file integrity is never in itself sufficient to display an “Authentic” or “Safe” label. The Publisher Trust Level is always displayed alongside and with equal weight: fraudulent Documents issued by irresponsible parties will still appear "intact" if they have not been altered since first issued.

8.5. Possible results displayed to Verifiers include intact file with Unverified Publisher, intact file with Registered Publisher status, Document revoked, file mismatch or altered, Publisher suspended, Document not found, and Document pending recording.

8.6. Every verification result page is accompanied by an explicit explanation of what is proven and what is not proven by the result, as further detailed in Article 17.

9.1. Because full legal identity verification for every Publisher is not yet available in the current service phase, Certive displays Publisher Trust Levels as a tiered structure as follows.

9.2. The "Registered Publisher" level is not legal identity verification and is not equivalent to the "Verified Identity" level. This status merely states that the Certive Team has conducted a manual review of the relevant Publisher's eligibility.

9.3. Accountability as a protective layer. Pending full legal identity verification, Certive relies on three accountability mechanisms: mandatory responsibility declarations for every Publisher before their first issuance, full traceability of Publisher identity on every issued Document, and abuse reporting and suspension mechanisms as regulated in Article 11.

9.4. Baliola reserves the right to unilaterally review and elevate a Publisher's Trust Level based on supporting documentation submitted by the Publisher, and reserves the right to deny such elevation without obligation to explain detailed reasons to the relevant Publisher, provided such decisions are made in good faith.

10.1. A Publisher can revoke a Document they have issued along with the reason for revocation. Revocation is permanently recorded to the Mandala Application Chain network and cannot be undone.

10.2. After a Document is revoked, any subsequent verification of that Document will display the status "Revoked" along with the reason provided by the Publisher at the time of revocation.

10.3. Revocation is performed individually for each Document. Mass revocation of all Documents within an issuance batch simultaneously is not supported in the current service phase.

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

10.5. In addition to issuance and revocation, Publishers or Organization Admins can manage Document lifecycle through the following mechanisms:

• Document Unpublishing (Unpublish): Publishers or Organization Admins reserve the right to change Document access status to Unpublish to hide Document details from the public verification browser. This action does not delete or alter transaction records saved on the blockchain network.
• Document Version Update (Update): Publishers or Organization Admins can upload newer versions of an issued Document (v1, v2, etc.). Each version update will be recorded as a new history on the blockchain without erasing the audit trail (Document Timeline) of previous document versions.
• Restamping Processing (Retry Stamp): If Digital Fingerprint recording to the blockchain network experiences delay (pending) or technical system failure, Publishers or Organization Admins can trigger the Retry Stamp function to reprocess recording until reaching active status (STAMPED).

11.1. Any Verifier or Document Holder who suspects abuse, including fraudulent Document issuance or Publisher identity fraud, may report the matter to Baliola through the channel in Article 24.

11.2. Every report is reviewed by the Certive Team. If a report is proven valid, Baliola reserves the right to suspend the relevant Publisher's ability to issue new Documents, without prior notice in urgent circumstances.

11.3. Documents issued prior to suspension remain recorded permanently and are not deleted, but will be displayed to Verifiers with a warning that the Publisher currently holds suspended status.

11.4. Baliola reserves the right, at its own discretion, to suspend or terminate access for any User proven to violate these Terms and Conditions, as further regulated in Article 20.

12.1. Users who are familiar with blockchain technology may optionally link their Crypto Wallet to their Certive account via the account settings menu.

12.2. Linking a Crypto Wallet is never a requirement to use any feature in Certive, including issuing Documents. Its benefits are supplementary: strengthening proof that issuance was conducted by the owner of the respective cryptographic key, and serving as a prerequisite to participate in the Web3 Staking program in Article 15.

12.3. Users are fully responsible for the security of their Crypto Wallet private keys. Baliola does not store, have access to, or bear responsibility for any loss of access to Users' private Crypto Wallets.

12A.1. Separation of Personal Google Account and Organization Storage Functions. Certive strictly distinguishes between personal Google account usage for authentication and organization storage integrations:

• Personal Google Account (Single Sign-On / SSO): Used at the individual account level (under the Personal Account menu) specifically for registration, identity verification during sign-in (login), and User account security.
• Organization Cloud Storage: Used at the organization level (under Organization Management Settings -> Storage) to automatically store original document files that have been stamped to Google Drive.

12A.2. Email Address Independence for Organization Storage. The Google Drive account email address connected as Organization Cloud Storage is not required to match the Google account email address used by Users (whether Owner or Admin) to register or log into the Certive platform. Organizations are free to designate and use dedicated institutional Google Workspace/Drive accounts belonging to the company or team.

13.1. Document files are never stored on Certive servers in any form. This is a core and permanent privacy commitment of the Certive service.

13.2. If an Organization enables third-party cloud storage integration features (such as Google Drive), uploaded original files will be sent directly to the connected Organization storage account. Under these conditions, Certive only stores issuance metadata and delivery reference links, while storage, governance, and security of original files remain entirely subject to the terms, conditions, and controls of the third-party storage provider.

13.3. Certive only stores the Digital Fingerprint of each successfully issued Document in an internal registry used for duplicate checks as regulated in Article 7.4. This registry never stores original files, only digital fingerprints.

13.4. What is recorded on the blockchain is not the raw Digital Fingerprint, but a derived value processed beforehand by Baliola using Certive's secret key. External parties who merely possess a copy of a file cannot compute and match that value independently without Certive's involvement. This mechanism provides additional privacy benefits. Verification against the blockchain still requires active involvement of Certive as the key holder, and Baliola is developing governance and continuity procedures for this key, with any material developments communicated to Users.

13.5. User passwords and sensitive data are stored using industry-standard encryption, and all data communication between User devices and the Certive system is encrypted.

13.6. Certive processes User personal data in accordance with applicable Personal Data Protection laws in Indonesia, applying data minimization principles: collecting and storing only data necessary to run the service.

13.7. Access to the Digital Fingerprint registry is restricted internally, and any access to it is logged as part of Baliola's security audit trail.

13.8. Certive privacy data and policies are regulated in more detail in the Certive Privacy Policy, an integral part of these Terms and Conditions.

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

14.2. The Free Plan is provided at no cost for individual users, students, and freelancers, with an issuance quota of one Document per recording transaction (single stamp), without mass issuance features.

14.3. Starter/Pro and Business Plans are aimed at agencies, small and medium enterprises, independent notaries, universities, and local government institutions / mid-scale SOEs, with larger quotas and mass issuance capacities according to the table above.

14.4. The Enterprise Plan is tailored for central government agencies and large corporations with customized document quota, mass issuance capacity, and Admin seat requirements. Prices and service terms for the Enterprise Plan are governed under separate commercial agreements between Baliola and the respective client.

14.5. Baliola reserves the right to modify the structure and pricing of Service Plans from time to time. Price changes will be communicated to affected Users within a reasonable timeframe prior to taking effect, and will not apply retroactively to active billing periods.

14.6. If usage by an account or Organization exceeds the document quota of the chosen Service Plan, Users may upgrade to a higher Service Plan, participate in the Web3 Staking program as regulated in Article 15 if eligible, or contact Baliola for custom adjustments via the channel in Article 24.

15.1. Certive offers a Staking Sweeteners program using Mandala Chain network KPG Tokens, serving as a bridge between Web2 institutional Users and the Web3 ecosystem. Users who link their Crypto Wallet as regulated in Article 12 can lock a specified amount of KPG Tokens via Certive smart contracts to receive service upgrades without additional fiat currency fees.

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

15.3. Web3 Staking program tiers are structured as follows.

15.4. KPG Tokens locked via Certive smart contracts cannot be withdrawn before the minimum lock period expires. Users are fully responsible for token value fluctuation risks during the lock period.

15.5. The Web3 Staking program is optional, providing added value beyond core Service Plans. Users who do not participate in this program still receive all benefits of their selected Service Plan as regulated in Article 14, without any reduction.

15.6. Baliola reserves the right to modify Web3 Staking program terms, including lock requirements and benefits provided, with notice to affected Users within a reasonable timeframe prior to taking effect.

16.1. Service Plans and Billing. Certive Service Plan payments can be processed through several billing model choices based on the Organization's chosen plan, including periodic subscriptions, prepaid Doc Credits, Pay As You Go usage, hosted invoices, special discounts, or custom commercial arrangements for institutional clients.

16.2. Service Plan Upgrades and Downgrades. Service plan upgrades or quota additions take effect immediately upon successful payment confirmation. Service Plan downgrades take effect at the start of the next billing cycle and do not reduce fees paid for the ongoing billing cycle.

16.3. Payment Methods. Payment transactions can be conducted through official channels available during the billing flow, such as Bank Transfer, Credit/Debit Card, E-Wallet, QR Payment, and Retail Outlets. Currency details, invoices, and spending limits are clearly displayed before transactions are confirmed.

16.4. Refund Policy. All paid fees are non-refundable, unless specified otherwise in writing by Baliola or required by applicable law.

16.5. Payment Failure. Repeated payment processing failures may cause the account or Organization to be downgraded to the Free Plan or temporarily suspended until payment is resolved, with prior notice to the relevant User.

17.1. Certive provides document integrity and provenance recording services. Certive proves who issued a Document, when it was issued, and that the file has not changed since that time, ensuring Publishers can be traced and held accountable. Certive does not represent that the contents of the Document are true.

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

• The accuracy or truthfulness of the substance or contents of a Document.
• The legal validity of a Publisher, unless the Publisher has achieved the “Verified Identity” level as regulated in Article 9, which at the time of drafting these Terms and Conditions is not yet activated.
• Misuse by Publishers whose identities are valid but act with bad intentions, including issuing Documents with untrue contents.

17.3. Every verification result displayed by Certive is accompanied by an explicit explanation of what is proven and what is not proven by the result. Verifiers who doubt the substance validity of a Document are advised to confirm directly with the Publisher through the Publisher's official channels outside the Certive system.

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

17.5. To the extent permitted by applicable law, Baliola's liability for losses arising from the use of Certive services is limited to the amount of fees paid by the User to Baliola for the relevant Service Plan in the preceding twelve months. Baliola is not liable for indirect, consequential, or lost profit damages arising from the use or inability to use Certive services.

17.6. Provisions in Article 17.5 do not apply to losses arising from Baliola's gross negligence or willful misconduct, or in other cases that cannot be limited under applicable law.

18.1. Users must provide true and accurate information during account registration and throughout their use of Certive services.

18.2. Users are prohibited from issuing Documents that they know or reasonably ought to suspect contain false, misleading information, or infringe upon the rights of third parties, including intellectual property and privacy rights.

18.3. Users are prohibited from using Certive services for any purpose that violates applicable laws in Indonesia or in the jurisdiction where the User resides.

18.4. Users are prohibited from attempting to access, disrupt, or damage Certive systems, networks, or infrastructure, including unauthorized attempts to access the Digital Fingerprint registry or Certive secret keys.

18.5. Users are prohibited from using accounts belonging to other parties without authorization, or misusing invitation mechanisms to register accounts for unauthorized parties.

18.6. Violations of this Article 18 may result in access suspension or termination as regulated in Article 11 and Article 20, without prejudice to Baliola's right to pursue other available legal remedies.

19.1. All intellectual property rights in the Certive platform, including software code, interfaces, logos, and Certive trademarks, are owned by Baliola or its licensors, and are protected by applicable intellectual property laws.

19.2. These Terms and Conditions do not grant Users any ownership rights in the Certive platform, except for limited, non-exclusive, non-transferable rights to access and use Certive services in accordance with these Terms and Conditions.

19.3. Copyright and intellectual property rights in the contents of any Document issued through Certive remain owned by the lawful Document owner. Certive only records the Digital Fingerprint of the Document and claims no rights over its content.

19.4. Users on the Premium-Boost Plan who unlock white-labeling features as regulated in Article 15.3 still do not acquire ownership rights over underlying Certive technology or infrastructure. Custom domain usage rights apply only while the relevant KPG Token lock period remains active.

20.1. Users can terminate their use of Certive services at any time by closing their account via the account settings menu or by contacting Baliola via the channel in Article 24.

20.2. Baliola reserves the right to suspend or terminate User access to Certive services, at any time with or without prior notice, in the event of violations of these Terms and Conditions, suspected abuse as regulated in Article 11, or legal obligations requiring such action.

20.3. Account termination does not delete issuance, revocation, or verification records permanently recorded on the blockchain prior to termination, due to the permanent and tamper-resistant nature of such records as regulated in Article 3.3.

20.4. Articles 13, 17, 19, and 22 survive service termination to the extent relevant to obligations or rights arising prior to termination.

21.1. Baliola reserves the right to modify, add, or discontinue Certive service features from time to time to enhance service quality and security.

21.2. Baliola reserves the right to update these Terms and Conditions at any time. Material changes will be notified to Users via registered email or in-platform notifications at least seven calendar days prior to taking effect.

21.3. If a User does not agree to modifications to the Terms and Conditions, the User may terminate service usage as regulated in Article 20 before changes take effect. Continued use of the service after the effective date shall constitute acceptance of the changes.

22.1. These Terms and Conditions are governed by and construed in accordance with the laws of the Republic of Indonesia.

22.2. Any dispute arising from or related to these Terms and Conditions shall first be resolved through amicable negotiations to reach mutual agreement.

22.3. If an amicable settlement cannot be reached within a reasonable period, disputes shall be resolved through the competent District Court in Baliola's legal domicile, without prejudice to the parties' rights to pursue other mutually agreed written dispute resolution mechanisms.

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

23.2. Baliola's failure to enforce any right or provision in these Terms and Conditions shall not be construed as a waiver of such right in the future.

23.3. These Terms and Conditions, together with the Certive Privacy Policy and separate commercial agreements applicable to Enterprise Plans, constitute the entire agreement between the User and Baliola regarding the use of Certive services, superseding any prior oral or written agreements regarding the same.

23.4. Users may not transfer or assign their rights and obligations under these Terms and Conditions to third parties without prior written consent from Baliola. Baliola may assign its rights and obligations under these Terms and Conditions in connection with a corporate reorganization, merger, or business transfer, with notice to Users.

24.1. Any questions, complaints, or reports of suspected abuse regarding Certive services, including those regulated in Article 11, may be submitted via email to: support@baliola.io.

24.2. Baliola responds to all received complaints within a reasonable timeframe, and follows up on abuse reports according to review procedures regulated in Article 11.