Skip to content

Legal document

Layarva Terms of Service

The Indonesian version governs where the two versions differ in interpretation.

Effective Date: 20 August 2026
Last Updated: 10 November 2026

These Terms of Service ("Terms") govern access to and use of the Layarva website, web application, device applications, digital signage player, Studio, cloud services, offline services, Queue Management, Public API, third-party integrations, and all other products and services provided under the Layarva brand.

Layarva is operated by Layarva, having its registered address at Jl. Cepit Raya RT 003/RW 002 Jatimulya Cilodong Depok - Jawa Barat 16413, Indonesia ("Layarva", "we", "us", or "our").

By creating an account, purchasing a subscription, accessing, or using the Services, you acknowledge that you have read, understood, and agreed to these Terms.

If you use Layarva on behalf of a company, organization, school, hospital, place of worship, business, institution, or other entity, you represent that you have the authority required to accept these Terms on behalf of that entity.


1. Definitions

For purposes of these Terms:

"Account" means an account used to access Layarva.

"Customer" means an individual or organization that owns an Account, purchases a Subscription, or uses the Services.

"User" means an individual who is granted access to a Customer Account or Workspace.

"Workspace" means an organizational environment or workspace used by a Customer to manage Screens, Content, devices, Users, Queue Management, and other resources.

"Services" means all products and functionality provided through Layarva.

"Screen" means a digital signage screen, display, television, monitor, kiosk display, or other display endpoint managed through Layarva.

"Device" means a player, Android device, computer, kiosk, printer, signage hardware, or other device connected to the Services.

"Customer Content" means images, videos, audio, animations, fonts, text, designs, documents, data, API payloads, playlists, templates, or other materials uploaded, created, stored, transmitted, or displayed by a Customer through Layarva.

"Subscription" means a Free, Flex, Starter, Business, Premium, Enterprise, Queue, add-on, or other service plan made available from time to time.

"Post-Subscription Retention Period" means the period following the last paid billing expiration, with a four-calendar-month deadline for reducing Customer storage to the applicable Free allowance and a 365-day deadline for permanently deleting a Dormant Account.

"Dormant Account" means a Free Account that satisfies the inactivity criteria described in these Terms.


2. Eligibility and Authority

Users must have the legal capacity and authority required to use the Services.

The Workspace owner or administrator is responsible for managing who may access the Workspace and the permissions granted to each User.

The Customer is responsible for activities performed by Users to whom the Customer grants access, except to the extent an activity results directly from a security breach for which Layarva is responsible.


3. Account Registration and Security

Customers must provide accurate information and keep account information up to date.

Customers are responsible for protecting the confidentiality of:

  • passwords;
  • API keys;
  • access tokens;
  • refresh tokens;
  • pairing credentials;
  • authentication secrets; and
  • other credentials associated with the Account or Services.

Credentials must not be provided to unauthorized parties.

Customers must promptly contact Layarva if they know or suspect that unauthorized access, credential misuse, or a security incident has occurred.

Layarva may implement security measures such as multi-factor authentication, session expiration, device authentication, access controls, rate limiting, credential rotation, or token revocation.

Users may enable MFA in Settings using Email OTP or a TOTP Authenticator. Method changes require a recent sign-in and confirmation through the verified account email; TOTP activation also requires an Authenticator code. If an Authenticator is lost, an authorized Layarva Admin may switch TOTP to Email OTP at the existing verified account email after verifying the request. Existing sign-in sessions are revoked and the administrative action is recorded.

At the request of the original owner or an authorized organization representative, Layarva Admin may transfer ownership of an organization and all its Workspaces to another active User account with a verified email. The previous owner becomes an Admin in the affected Workspaces, both parties must sign in again, and the transfer is recorded. Content and billing history remain with the organization.


4. Layarva Services

Layarva is a platform that may provide, among other things:

  • digital signage management;
  • Studio and content creation;
  • media and content management;
  • playlists and scheduling;
  • cloud screen management;
  • offline and cached content;
  • device management;
  • device monitoring;
  • Queue Management;
  • kiosk functionality;
  • Public API;
  • third-party integrations;
  • templates and widgets;
  • reporting; and
  • additional features introduced from time to time.

Feature availability may vary by Subscription, platform, device type, region, configuration, or third-party service.

Layarva may improve, develop, add, replace, or discontinue specific features to improve security, stability, performance, compliance, or continuity of the Services.

If a change materially reduces a core function of an active paid Subscription, Layarva will use reasonable efforts to provide appropriate notice.


5. Cloud, Edge, Offline, and Technical Infrastructure

Layarva may use a combination of:

  • cloud infrastructure;
  • edge processing;
  • local caching;
  • Content Delivery Networks;
  • databases;
  • object storage;
  • backups;
  • processing nodes; and
  • other infrastructure services.

Certain features may continue operating through cached or offline modes after a successful prior synchronization, while other functions may require an internet connection.

Layarva does not guarantee that all features will be available offline.


6. Server Location and Cloud Infrastructure

Layarva uses cloud and technology service providers whose infrastructure may be located in Indonesia or in other countries or regions.

Data may be stored, processed, transmitted, replicated, cached, or backed up across one or more technical locations.

Server locations, data centers, storage regions, processing nodes, CDNs, backup facilities, or infrastructure providers may change from time to time based on factors including:

  • availability;
  • security;
  • reliability;
  • performance;
  • scalability;
  • disaster recovery;
  • operational efficiency;
  • changes in infrastructure providers; or
  • other technical requirements.

Unless expressly agreed in a written agreement with a Customer, Layarva does not guarantee that data will always remain in a particular data center, region, city, or country.

Changes to technical locations that do not materially change the purpose or nature of processing may be made without individual prior notice.

If a change materially changes our Personal Data processing practices, or if notice is required by applicable law, Layarva will provide appropriate notice.

Cross-border processing and transfers of Personal Data will be handled in accordance with applicable data protection laws.


7. Screen Location Information

Layarva allows authorized Users to enter location information for a Screen.

This information may include:

  • location name;
  • latitude;
  • longitude;
  • address or location label; and
  • other supporting location information.

Screen coordinates are provided and entered by the User.

Layarva does not automatically obtain GPS coordinates, background location, or the real-time location of a Screen merely because a Device is connected to Layarva.

Location information may be used to:

  • identify where a Screen is installed;
  • display Screens on a map or dashboard;
  • assist with managing Screens across multiple locations;
  • search for or group Screens;
  • support troubleshooting;
  • provide support; and
  • provide other functions directly related to Screen management.

The Customer is responsible for ensuring that information entered is accurate and that the Customer has the necessary right or lawful basis to provide it.

Layarva does not use Screen coordinates for continuous tracking of an individual's movements.


8. Plans and Usage Limits

Each Subscription may include different limits, including:

  • number of Screens;
  • number of Queue Units;
  • storage capacity;
  • bandwidth or traffic;
  • offline exports;
  • API usage;
  • number of Users;
  • Studio features;
  • integration features; and
  • other resources.

Applicable limits are those shown on the pricing page, at checkout, in a quotation, invoice, Order Form, or Customer agreement.

Customers must not intentionally bypass or circumvent Subscription limits.


9. Pricing, Billing, and Taxes

Pricing is based on the price shown when the Customer completes a transaction or the price agreed in an Order Form.

Taxes or other governmental charges may be added where applicable.

Layarva may change Subscription pricing for future billing periods.

Pricing changes will not apply retroactively to periods already paid for unless required by law or agreed with the Customer.

If a Subscription is recurring or automatically renews, the applicable renewal mechanism must be disclosed to the Customer at purchase or before renewal.


9.1 Storage Add-ons and Plan Changes

Free includes one Cloud or Edge Screen, one offline Screen, and 200 MB of media storage.

Flex includes Starter features, two Cloud Screens, two included offline Screens, and 500 MB of media storage at IDR 55,000 or USD 7 per month. Starter includes six Cloud Screens, three included offline Screens, and 5 GB. Business includes 20 Cloud Screens, 10 included offline Screens, and 25 GB. Premium includes 45 Cloud Screens, 20 included offline Screens, and 80 GB before add-ons. With a maximum total capacity of 1 TB (1,024 GB), Premium permits up to 944 GB of storage add-ons.

Queue Only includes one Queue Unit, one Cloud or Edge Screen, one offline Screen, and 500 MB of media storage at IDR 99,000 or USD 8 per month. Queue displays use the Queue Unit allowance separately.

Additional Cloud Screens are billed at IDR 35,000 or USD 4 per Screen per month where available. Additional Queue Units cost IDR 89,000 or USD 7 per unit per month.

Customers with an active paid Subscription may purchase additional storage in 1 GB units at IDR 2,000 or USD 0.15 per GB per month, in the Account's billing currency.

Customers may choose any whole-GB quantity up to the plan's maximum total capacity, including the plan allocation and all add-ons: Flex and Starter 50 GB each, Business 500 GB, Premium 1 TB (1,024 GB). For example, Starter's included 5 GB permits up to 45 GB of storage add-ons. The same maximum applies to the destination plan on downgrade; add-ons cannot preserve capacity above that maximum. Customers must choose a larger plan or manually delete unused files and select the destination plan's included allowance. New purchases must also fit any already scheduled plan.

The add-on follows the active plan's monthly or annual billing interval. Storage renews and is invoiced together with the Subscription on the same date. Annual billing multiplies the monthly rate by the months in the period, subject to the annual discount shown at checkout. A purchase during a paid period is prorated over the remaining paid period and does not change the renewal date.

A storage upgrade adds to the existing total capacity, comprising the plan's included storage and all active add-ons. An upgrade must not reduce that total capacity.

For a plan downgrade, the Customer chooses either to delete unused files until usage fits the target plan's included capacity, or to retain existing storage capacity by paying recurring storage add-ons for the capacity difference. These add-ons renew with the Subscription. For example, moving from Business 25 GB to Starter 5 GB while retaining 25 GB requires a 20 GB add-on at IDR 40,000 or USD 3.00 per month, in addition to the plan fee. Existing storage add-ons are included in the capacity retained. Plan downgrades take effect at the next paid-period boundary.

Users cannot delete files still used by a Channel or Playlist, including published versions. All usage must first be removed; only unused files may be deleted.

9.2 Subscription Renewals and Late Payments

Standard paid subscriptions are prepaid. When a renewal payment is outstanding, the existing plan remains available for a grace period of 7 (seven) calendar days after the paid period ends. If payment is not confirmed by the end of that period, paid access is suspended and the unpaid renewal invoice is closed to payment and retained for accounting. The grace period is provided without a separate charge, and fees for the period after suspension do not accumulate as debt.

To reactivate, the Customer requests a new invoice. The new monthly or annual billing period begins when payment for reactivation is confirmed, and the next billing date is calculated from that date. Verified funds received against an expired renewal reference may be applied as payment credit toward reactivation. Accounting and payment records are retained, and adjustments are documented where required. Enterprise or other specially negotiated contracts may provide different payment terms, including postpaid billing.

Suspension of access does not itself delete content, Playlists, device configuration, or queue data. Any deletion is governed by the applicable data retention provisions in these Terms and the Privacy Policy.


10. Payment

Customers are responsible for making payment using the required method and by the applicable due date.

Payments may be processed by third-party payment providers.

10.1 IDR Payments and iPaymu Administration Fees

Payments in Indonesian Rupiah (IDR) are processed through iPaymu. Payments in US Dollars (USD) are processed through PayPal. Available iPaymu payment methods are shown on its official payment page, subject to merchant account activation and provider terms.

For new iPaymu checkouts, applicable gateway administration or transaction fees are charged to the Customer and shown on the official iPaymu payment page before payment confirmation. The fee depends on the selected payment method and provider terms. Review the final payable total, including applicable fees and taxes, before paying. An existing payment session keeps the amount already issued for that session. The Customer's bank, card issuer or payment provider may charge fees directly under its own terms; Layarva does not set or receive those fees.

For reference, these are examples of iPaymu's published service rates as of 23 October 2026. The actual Customer fee and final total are shown on the payment page:

Payment methodReference merchant service fee
Virtual accountRp3,500–Rp4,500, depending on bank and settlement timing
Credit card2.5% + Rp2,000
Dynamic QRIS0.5% up to Rp100,000; 0.7% above Rp100,000; H+0 settlement adds 1.8%
E-wallet3.5%
Retail outletsRp4,000; H+0 settlement adds 1.8%

Rates may change and are subject to merchant category, payment method and iPaymu terms. This list does not guarantee that every method is available for every transaction. See [official iPaymu pricing](https://ipaymu.com/id/pricing/) for current terms. Merchant withdrawal fees are not added to the Customer's invoice.

A plan or add-on is activated after Layarva verifies payment confirmation. Returning from iPaymu or closing the payment page is not proof of payment or cancellation. If the status is uncertain, check the invoice in Billing or contact Support before paying again.

10.2 PayPal Transaction Fees

For a PayPal merchant account registered in Indonesia, PayPal's published standard rates as of 30 August 2026 are:

Commercial transaction typeFee charged by PayPal to Layarva
Domestic payment3.4% + fixed fee
International payment4.4% + fixed fee
Fixed fee for payments received in USDUSD 0.30

These commercial processing fees are charged by PayPal to Layarva as the payment recipient and are not separately added to the Customer as a surcharge for selecting PayPal. The PayPal User Agreement prohibits merchants from imposing a surcharge or another fee solely for accepting PayPal. Layarva may only apply a general handling fee if it also applies to comparable non-PayPal payment methods and is not higher than the handling fee charged for those methods.

The Customer remains responsible for fees imposed directly on the Customer by PayPal, the Customer's bank, card issuer, or payment provider, including currency-conversion or card fees where applicable. Layarva does not set or receive those fees.

PayPal may change its rates based on the Customer's country or region, currency, PayPal product, transaction volume, or merchant-account status. PayPal's actual rate at the time of the transaction applies. Current information is available on the [PayPal Indonesia merchant fees page](https://www.paypal.com/id/business/paypal-business-fees) and in the [PayPal User Agreement](https://www.paypal.com/id/legalhub/paypal/useragreement-full?country.x=ID&locale.x=en_ID).

Subject to the renewal grace period and any special payment terms in Section 9.2, Layarva may restrict or suspend Services where payment:

  • fails;
  • is declined;
  • is reversed;
  • has not been received; or
  • is overdue.

11. Subscription Cancellation

Customers may cancel Subscription renewal through the available mechanism or by contacting Layarva if a self-service mechanism is not available.

Cancellation does not automatically end a period that has already been paid for.

Customers may continue to receive Services until the end of the applicable paid period, unless the Subscription is terminated for a violation of these Terms or another specifically stated circumstance applies.


12. Refund Policy

Cancelling a Subscription does not automatically entitle the Customer to a refund for a period that has already begun.

If the Services have been activated, made available in accordance with the purchased plan, or used, payment is generally not eligible for a refund merely because:

  • the Customer changes their mind;
  • the Customer no longer needs the Services;
  • the Customer stops using the Services;
  • the Customer does not use all features;
  • the Customer does not use the remaining Subscription period;
  • the Customer selected the wrong plan;
  • the Customer's business requirements change;
  • the Customer's hardware is unsuitable;
  • the Customer experiences internet connectivity issues;
  • a Customer-controlled system or third-party service is incompatible; or
  • the desired feature is not included in the purchased plan and the plan information was accurately disclosed.

12.1 Circumstances That May Be Considered for a Refund

Layarva may consider a refund where:

  1. a duplicate payment occurs;
  2. an incorrect billing amount results from an error by Layarva;
  3. payment succeeds but the Subscription cannot be activated and Layarva cannot resolve the issue within a reasonable period;
  4. the Services materially fail to conform to the Services agreed to and Layarva is unable to remedy the non-conformity;
  5. a special circumstance is approved by Layarva in writing; or
  6. a refund is required by applicable law.

12.2 Service Disruptions

For a service disruption attributable to Layarva, a remedy may include:

  • repair;
  • service restoration;
  • an extension of the Subscription term;
  • service credit;
  • a partial refund; or
  • a full refund where appropriate in light of the nature and impact of the incident.

Not every outage or disruption automatically creates a right to a refund.

12.3 Circumstances Outside Layarva's Control

Issues caused by circumstances outside Layarva's reasonable control, including Customer devices, electricity, internet connectivity, operating systems, local configuration, or third-party service failures, do not automatically qualify for a refund.

12.4 Violations of These Terms

Suspension or termination resulting from a violation of these Terms does not automatically entitle the Customer to a refund.

12.5 Consumer Rights

This Refund Policy is not intended to restrict any consumer rights that cannot lawfully be excluded or limited.


13. Free Plans, Trials, Beta, and Preview Features

Layarva may provide Free, Trial, Beta, Experimental, Early Access, or Preview offerings.

Such offerings may:

  • have usage limits;
  • change over time;
  • not include all functionality; and
  • be changed or discontinued.

Unless otherwise stated, Beta or Preview features are not subject to a specific service level commitment.


14. Expiration of a Paid Subscription

If a paid Subscription expires and is not renewed:

  • access to paid features may be stopped or restricted;
  • new content publishing may be stopped;
  • new synchronization may be stopped;
  • Public API or Queue Management may be restricted;
  • Devices may stop receiving new updates; and
  • entitlements to paid-plan resources may end.

Customer data is not immediately deleted on the Subscription expiration date.

The Account enters the Post-Subscription Retention Period measured from the last paid billing expiration date, with Customer storage reduced to the applicable Free allowance at the end of four calendar months and permanent deletion of the Dormant Account after 365 days as described below.


15. Post-Subscription Retention Period

If a paid Subscription is not renewed, the storage reduction deadline is the last paid billing expiration date + four calendar months. Logging in or using the dashboard does not move that reference date. Successful paid renewal establishes a new last billing expiration date.

At that deadline, data in Customer storage is reduced to the Free allowance that applies to the Workspace. The standard Free allowance is 200 MB. Unused files are deleted from oldest to newest. Files still used by a Channel or Playlist are protected; the Customer must first remove those usages. If protected files leave usage above the applicable Free allowance, the Account remains over quota until those usages are removed or the paid Subscription is reactivated; deletion does not forcibly break usages.

Storage deletion notices are sent three times: one month, two weeks, and three days before the four-month deadline. A billing reminder is sent each month during the four months following the last billing expiration. A reminder is not a new charge or authorization for an automatic debit.

Paid reactivation before deletion stops retention processing for that expiration episode. Recovery of already deleted data is not guaranteed. Retention does not entitle the Customer to paid features without an active Subscription.


16. Automatic Downgrade to a Free Plan

Four calendar months after the last paid billing expiration without renewal, the Account automatically becomes a Free Account with the applicable storage allowance, one eligible Cloud or Edge Screen, and one eligible offline Screen. All Screen records, device identities, and pairings are retained; additional Screens are locked until a paid plan is reactivated. Each slot is assigned to the oldest retained signage Screen of its type. Paid reactivation unlocks Screens within the purchased plan's capacity.

Expiration may still stop paid services after the applicable payment grace period, before automatic Free conversion. Free conversion does not extend paid service.

Storage reduction follows Section 15 and does not forcibly delete in-use files. An offline device receives changes on its next synchronization; offline packages remain subject to their license expiration.


17. Inactive Free Accounts

A Free Account may be classified as a Dormant Account after at least 365 consecutive days without qualifying activity.

Qualifying activity may include:

  • login;
  • content management;
  • Screen activity;
  • Device activity;
  • API usage;
  • publishing; or
  • other activity that demonstrates actual use of the Services.

For a Free Account that has never been paid, qualifying activity updates the last-activity date. Permanent deletion follows 365 days without activity, with three notices: two months, one month, and three days before deletion. The 365-day deletion rule applies to Free Accounts as well as paid Customers.

This rule is separate from the fixed retention period applied to expired paid Subscriptions.


18. Deletion of Dormant and Expired Accounts

A formerly paid Account that is not renewed is permanently deleted after 365 days from its last paid billing expiration date. Logging in does not restart this clock. Free Accounts that have never been paid remain subject to Section 17.

Account deletion notices for formerly paid Customers are sent three times: two months, one month, and three days before permanent deletion. Notices go to the registered email address or authorized billing recipient.

Permanent deletion removes all associated Account and Workspace data, including the remaining media storage, Content, Channels, Playlists, Device configuration, and pairing, except billing history. Invoices, payment records, and the minimum relationships required to interpret billing history are retained. This is closure of the entire Account/Workspace; protection of in-use files applies to individual/bulk file deletion and storage reduction before permanent Account deletion.

Once deletion is completed, data may be unrecoverable. Backups follow Section 20, and mandatory legal preservation obligations continue to apply.


19. Data That May Be Retained After Account Deletion

Deleting an Account does not necessarily mean that every record historically associated with the Customer must be deleted at the same time.

Layarva may retain certain records that have a separate lifecycle, particularly to the extent necessary for:

  • invoices;
  • accounting;
  • tax compliance;
  • payment records;
  • obligations to competent authorities; or
  • other legal obligations that specifically apply to those records.

Such records will not be used to operate the Customer's Workspace after Account deletion except where necessary for the applicable lawful purpose.

Technical and Operational Logs

Technical and operational logs follow the standard retention periods described in the Layarva Privacy Policy. Logs may be automatically deleted after the applicable retention period as part of normal system lifecycle, housekeeping, and storage management.

Layarva does not guarantee the availability of historical logs after the applicable retention period has expired.

If Layarva receives a security incident report, investigation request, audit request, dispute, claim, or valid legal request while relevant logs are still available, authorized personnel may search for and export records reasonably necessary for that purpose into a separate file for documentation or evidence.

The exported file may be retained separately for a maximum of 365 days from the date the export is created and may be deleted earlier when it is no longer required for the related purpose. If applicable law or a valid and binding order specifically requires a longer period, the file may be retained to the extent required by that obligation.

Creating such an export does not suspend, extend, or otherwise change the retention lifecycle of the source logs. Source logs continue to follow their normal retention periods.

If, before a request is received, relevant logs or data have already been deleted, anonymized, overwritten, or otherwise become unavailable through the normal system lifecycle, Layarva is not required to recover, reconstruct, recreate, or provide those records, to the extent permitted by applicable law.

Layarva can only provide records that remain available when the request is processed or records that were previously exported and retained separately.

Layarva is not required to preserve logs specifically for a possible future investigation, dispute, claim, or legal proceeding before Layarva receives a valid and sufficiently specific request, notice, or binding order concerning the relevant data.

The unavailability of data that has aged out of the system in accordance with the applicable retention lifecycle does not by itself constitute a Service failure or breach by Layarva.

Nothing in this section limits obligations that mandatorily apply under applicable law or under a valid and binding order received by Layarva.

20. Backups

Layarva creates and verifies a secure backup before deleting technical logs, including during retention cleanup and Account deletion. If a backup cannot be verified, deletion is deferred until the logs can be safely preserved.

Technical-log backups are retained for 180 days from backup creation and are then automatically deleted. This period is separate from the 14/30/90/180-day log retention periods and may continue after Account deletion. Backup access is restricted to authorized personnel for administration and recovery. These backups do not count toward Customer storage quotas and are not a Customer-facing historical-log service. Other system backups follow their applicable retention periods. A separately prepared evidence export follows its own 365-day maximum, unless a binding legal obligation requires otherwise.

21. Customer Content

Customers retain their rights in Customer Content that they own or lawfully license.

Layarva does not acquire ownership of Customer Content merely because the Content is uploaded to the Services.

Customers grant Layarva a limited, non-exclusive license to perform technical actions required to provide the Services, including:

  • storing;
  • making technical copies;
  • transcoding;
  • rendering;
  • caching;
  • transmitting;
  • distributing;
  • synchronizing;
  • backing up; and
  • displaying Customer Content.

This license applies only to the extent necessary to provide the Services.


22. Rights in Content

Customers are responsible for ensuring that they possess the rights, permissions, or licenses necessary for Content they use.

This includes:

  • images;
  • videos;
  • music;
  • audio;
  • fonts;
  • logos;
  • templates;
  • animations;
  • feeds;
  • data; and
  • other third-party materials.

Layarva is not responsible for intellectual-property violations resulting from Customer Content uploaded without the necessary rights.


23. Prohibited Use

Users must not use Layarva to:

  • violate applicable law;
  • infringe the rights of others;
  • distribute malware;
  • access systems without authorization;
  • disrupt systems or other users;
  • attempt to bypass authentication or authorization;
  • exploit vulnerabilities;
  • abuse the API;
  • circumvent rate limits;
  • use another party's credentials without authorization;
  • upload content whose use violates applicable law; or
  • engage in activities that materially endanger the platform.

Layarva may take appropriate action in response to such violations.


24. Digital Signage Player and Devices

Customers are responsible for providing:

  • compatible hardware;
  • displays;
  • electrical power;
  • local storage;
  • networking;
  • internet connectivity where required; and
  • appropriate Device configuration.

Offline or cached playback depends on prior successful synchronization and the condition of the Device.

Layarva does not guarantee the operation of hardware outside Layarva's control.

Hardware sold or provided separately may be subject to separate warranty terms.


25. Queue Management

Where included in a Subscription, Queue Management may provide functions such as:

  • ticket issuing;
  • call;
  • recall;
  • service start;
  • completion;
  • no-show;
  • operator management;
  • counter management;
  • display;
  • audio; and
  • printing.

Customers are responsible for the configuration and operating procedures of Queue Management.

Queue Management is not an emergency dispatch system, medical decision system, or safety-critical system.


26. Public API

The Public API may be subject to:

  • API keys;
  • authentication;
  • quotas;
  • rate limits;
  • payload limits;
  • endpoint restrictions; and
  • technical documentation.

Customers are responsible for protecting API keys and tokens.

Layarva may restrict or revoke credentials where there is evidence of:

  • credential leakage;
  • abuse;
  • fraud;
  • security attacks;
  • excessive use; or
  • disruption of the Services.

27. Third-Party Integrations

Layarva may integrate with third-party providers such as:

  • identity providers;
  • Google;
  • cloud storage providers;
  • data providers;
  • analytics providers;
  • email providers;
  • payment providers;
  • mapping providers; or
  • other services.

Third-party services are subject to the applicable provider's own terms and policies.

Layarva does not control:

  • third-party downtime;
  • API changes;
  • price changes;
  • policy changes;
  • product discontinuation; or
  • third-party compatibility changes.

Layarva may change or discontinue an integration that is no longer available, safe, or legally usable.


28. Google Services

Layarva may provide Google Sign-In and other Google integrations as optional features.

When a User chooses Google Sign-In, Layarva may receive basic Google account information authorized through the applicable authentication scopes, such as the User's name, email address, profile information, and Google user identifier. This information may be used to authenticate the User, create or link a Layarva account, and prefill identity information during registration.

Google Sign-In does not by itself authorize Layarva to access content stored in Google Drive, Google Sheets, Google Slides, Google Calendar, Gmail, or another Google service.

If a User separately enables a Google integration, the User authorizes Layarva to access only the Google data and permissions shown in the applicable Google OAuth flow and required for the selected Layarva feature.

Layarva will use Google user data only for the User-facing functionality for which access was granted, together with limited security, legal, or operational uses permitted by applicable Google policies.

Layarva does not request permissions for Google services solely for possible future functionality and seeks to use the minimum permissions required for features that are actually available.

Layarva does not sell Google user data or use Google user data for personalized advertising, retargeting, creditworthiness decisions, or training a general-purpose AI or machine-learning model using Google Workspace API user data.

The detailed categories of Google data accessed, purposes of use, storage practices, sharing restrictions, human-access rules, revocation controls, and retention practices are described in the Layarva Privacy Policy.

Users may revoke Google access through available Layarva functionality or through their Google Account settings. Revoking access may cause the corresponding Google-connected Layarva feature to stop functioning until access is authorized again.

Google services are provided by Google and remain subject to Google's own terms, policies, availability, and technical requirements.

29. Privacy and Data Protection

Processing of Personal Data is described in the Layarva Privacy Policy.

Depending on the context, Layarva may act as:

  • a Personal Data Controller; or
  • a Personal Data Processor acting on behalf of a Customer.

For certain relationships, particularly Business or Enterprise arrangements, data-processing terms may be supplemented by a Data Processing Addendum.


30. Layarva Intellectual Property

Unless otherwise stated, Layarva and its licensors retain all rights in:

  • source code;
  • software;
  • system architecture;
  • user interfaces;
  • designs;
  • trademarks;
  • logos;
  • documentation;
  • proprietary templates; and
  • Layarva technology.

These Terms do not transfer ownership of Layarva intellectual property to the Customer.


31. Feedback

Customers may provide feedback, suggestions, or reports about Layarva.

Layarva may use such feedback to improve or develop the Services without an obligation to compensate the person providing the feedback.

This provision does not grant Layarva ownership of Customer Content.


32. Availability, Maintenance, Data Recovery, and Service Changes

Layarva seeks to provide secure and stable Services and applies reasonable technical and operational measures to support availability, integrity, backup, and recovery appropriate to the characteristics of the Services.

However, the Services and data may be affected by:

  • maintenance;
  • cloud outages;
  • internet outages;
  • hardware failures;
  • software failures;
  • database or storage corruption;
  • backup or recovery process failures;
  • third-party service failures;
  • security incidents;
  • force majeure; and
  • other technical circumstances.

Maintenance may be scheduled or emergency maintenance.

If data becomes lost or unavailable outside the normal retention lifecycle, Layarva will use reasonable recovery efforts based on backups, replicas, caches, or other recovery mechanisms that remain available. Recovery is not guaranteed where no usable copy of the relevant data remains available.

An inability to recover data does not by itself constitute a breach of these Terms where Layarva has complied with applicable law and the technical and operational measures applicable to the relevant Services.

No specific Service Level Agreement applies unless expressly stated in a plan, Order Form, SLA, or separate agreement.

33. Security

Layarva may use technical and organizational security measures such as:

  • access controls;
  • authentication;
  • authorization;
  • encryption for appropriate data in transit or storage contexts;
  • logging;
  • monitoring;
  • backups;
  • rate limiting;
  • credential protection;
  • security reviews; and
  • incident response.

No electronic system can be guaranteed to be completely risk-free.

Customers remain responsible for credentials, endpoints, Devices, and configurations under their control.


34. Suspension

Layarva may suspend some or all access where there is:

  • a security threat;
  • unlawful use;
  • a violation of these Terms;
  • overdue payment;
  • fraud;
  • abuse;
  • use that materially disrupts other customers; or
  • an order from a competent authority.

Where reasonably possible, Layarva will provide notice and an opportunity to remedy a breach before permanent termination.


35. Termination

Customers may terminate an Account or Subscription using the available mechanism.

Layarva may terminate Services for a material violation of these Terms or where required by law.

Following termination, data will be handled in accordance with the applicable retention and deletion policies.


36. Disclaimer

To the extent permitted by law, the Services are provided based on their then-current condition and availability.

Layarva does not guarantee that:

  • the Services will always be uninterrupted;
  • all bugs can be eliminated;
  • all hardware will always be compatible;
  • all third-party services will always remain available; or
  • all networks will always function.

Nothing in these Terms excludes rights that cannot lawfully be excluded.


37. Limitation of Liability

For business Customers and to the extent permitted by law, Layarva is not liable for indirect losses, loss of profit, loss of opportunity, or consequential losses that are not directly caused by Layarva's breach of its obligations.

For paid Services, Layarva's aggregate liability may be limited to the amount of fees paid by the Customer to Layarva for the relevant Services during the 12 months preceding the event giving rise to the claim, to the extent such limitation is permitted by law.

The limitation does not apply where applicable law prohibits the limitation.


38. Business Customer Responsibility

To the extent permitted by law, a business Customer is responsible for third-party claims directly arising from:

  • unlawful Customer Content;
  • infringement of third-party rights; or
  • use of the Services in material violation of these Terms.

39. Force Majeure

Layarva will not be considered in breach to the extent a delay or failure is caused by an event outside its reasonable control that qualifies as force majeure under applicable law.

Depending on the circumstances, such events may include:

  • natural disasters;
  • fire or facility damage outside Layarva's reasonable control;
  • flooding;
  • war;
  • civil unrest;
  • government action;
  • widespread electricity or telecommunications disruptions;
  • material failure of a third-party infrastructure provider outside Layarva's reasonable control; or
  • other extraordinary events outside Layarva's reasonable control.

Application bugs, configuration errors, backup errors, or internal failures are not automatically treated as force majeure merely because they cause disruption or data loss.

This provision does not exclude obligations that cannot lawfully be excluded.

40. Consumer Rights

Nothing in these Terms is intended to restrict or remove consumer rights that cannot lawfully be excluded or limited.

If any provision conflicts with a mandatory provision of applicable law, the mandatory legal provision will apply.


41. Changes to These Terms

Layarva may update these Terms to reflect changes in:

  • products;
  • technology;
  • security;
  • pricing;
  • operations;
  • infrastructure; or
  • law.

Material changes that significantly affect User rights or obligations will be communicated using a reasonable notice mechanism.

The "Last Updated" date identifies the current version.


42. Electronic Communications

Customers agree that notices concerning:

  • Accounts;
  • security;
  • Subscriptions;
  • payments;
  • expiration;
  • deletion;
  • changes to these Terms; and
  • service administration

may be provided electronically by email, dashboard, application notification, or another communication method.


43. Order Forms, SLAs, and Additional Agreements

Certain Customers may have:

  • quotations;
  • Order Forms;
  • Service Level Agreements;
  • Data Processing Addenda;
  • Enterprise Agreements; or
  • other specific agreements.

Where there is a conflict, the document that specifically governs the relevant matter will control for that scope to the extent permitted by law.


44. Governing Law and Dispute Resolution

These Terms are governed by the laws of the Republic of Indonesia.

If a dispute arises, the parties will first seek to resolve the dispute through good-faith consultation.

If no resolution is reached, the dispute may be submitted to a competent court or another dispute-resolution mechanism available under applicable law.

This provision does not restrict a consumer's right to use a dispute-resolution forum that is mandatorily available under applicable law.


45. Language Versions

These Terms may be made available in Indonesian and English.

Both versions are intended to communicate the same substance. If there is an inconsistency or difference in interpretation between the Indonesian and English versions, the Indonesian version will be used as the reference to the extent permitted by applicable law.


46. Severability

If any provision of these Terms is found invalid or unenforceable, the remaining provisions will continue to apply to the extent permitted by law.

A failure by Layarva to enforce a provision does not constitute a waiver of the right to enforce it later.


47. Contact

For questions about these Terms:

Layarva
Operated by: Layarva

Address: Jl. Cepit Raya RT 003/RW 002 Jatimulya Cilodong Depok - Jawa Barat 16413

Email: halo@layarva.com

WhatsApp: [+62 81908640386](https://wa.me/6281908640386)