Mauntir
Security, privacy, and terms for Insimen services.
← Back to serviceRead the general and service-specific provisions together. Your statutory rights continue to apply.
Read the privacy policy for Mauntir, including user rights, the parties’ duties and how to contact support. General and service provisions are read together with applicable transaction agreements.
Last updated: October 21, 2026
Supplemental policies updated 24 October 2026. Specific agreements retain the versions shown in their documents.
This policy applies to Insimen's information services, profiles, business accounts, service orders, and workspaces.
The data involved depends on the features you use and the information you choose to provide.
Data may come from you, another member's action connected to your account, an authorized party in a service process, or your browser and device when a feature is used. We seek to explain the need when data is requested and do not request unrelated data without a reasonable purpose.
Data is used only for legitimate purposes connected to the service.
Some visibility choices can be managed in product settings.
Connecting Google Calendar is optional and is available in Calendar on your personal Insimen account. After you grant permission in Google, you can select one calendar you are allowed to manage. Insimen reads your calendar list for this selection and reads events on the selected calendar to display them alongside your Insimen agenda.
You can create, update, and delete events on that calendar through Insimen. Changes are sent to Google. Synchronization reads the displayed date range when Calendar opens, when you return to the page, every five minutes while the page is visible, or when you select Sync now. Recurring events and invitations that cannot be edited are managed in the original calendar application.
Google sends calendar information and event details when this feature is used. Insimen stores connection and selected-calendar identifiers, the calendar name, synchronization time, and copies of loaded events: title, notes, start and end times, time zone, and an all-day indicator. Event identifiers, editability, and change versions are also stored to identify events and prevent changes from overwriting a newer version.
Google also provides access and refresh tokens so the connection can be used without requiring you to sign in to Google each time. These tokens are stored encrypted on Insimen's server and are not sent to the browser as page content. Event copies are held in application storage with access checks tied to the account owner.
Insimen uses Google Calendar data only to display and manage your connected calendar, synchronize changes, and protect the connection. Data and changes are sent to Google to operate this feature. Server storage and backups use infrastructure with restricted access for service operation and recovery.
Google Calendar data is not sold, used for advertising or creditworthiness decisions, provided to data brokers, or used to train general AI models. Staff may read event contents only with your specific consent for a purpose you request, or when necessary to address a security issue or comply with applicable law. These limits also apply to parties that help Insimen process this data.
The use and transfer of information received from Google follows the Google API Services User Data Policy, including the Limited Use requirements. These specific Google Calendar provisions limit the general data-use and sharing provisions on this page.
To stop connecting the calendar, open Calendar in your personal Insimen account, select Disconnect on Google Calendar, and confirm. This removes the connection tokens and related event copies from Insimen's active storage. Changing the selected calendar or reconnecting the account also clears event copies from the previous connection. Original events remain in Google Calendar; originals are changed or deleted only when you perform that action on an event.
Disconnecting in Insimen does not revoke the permission recorded in your Google account. To revoke it, open your Google account's third-party connections page and remove Insimen's access. If you only revoke permission in Google, Insimen can no longer synchronize, but previously loaded copies may remain stored. Use Disconnect in Insimen or ask us to delete those copies.
Event copies remain stored while the connection is active; the application does not automatically delete them just because the event date has passed. Backups may still contain data removed from active storage. The previous daily backup is replaced after a new backup completes and passes validation; if backup creation fails, the last successful copy is retained. Pre-update and manual backups are managed separately and may remain until an administrator removes them. Backup copies are not available as calendar features and access is restricted.
You can request access, correction, or deletion of Google Calendar data through cs@insimen.com. Identify your Insimen account and describe your request without sending passwords or tokens. We verify account ownership before acting and explain any backup copies or legal obligations that affect deletion.
Data may come from information you enter in an account, profile, order form, Chat, email, support call, document upload, or approved update. We also receive technical data generated when a browser accesses the service, such as session, device, time, and security activity information.
We aim to limit collection to data relevant to the feature used. If you provide someone else's data, you must have an appropriate basis and provide any notice required to that person.
Answers and documents in an order may contain personal, legal, financial, or business information. Access is limited to the requester, an authorized business account, Insimen personnel, an appointed partner, or another party needed for the service stage. Private documents should not appear on public pages, public search, or file URLs that can be opened without an access check.
We may create working copies, invoice snapshots, progress notes, or operational metadata so an order can be tracked. Those copies remain subject to the relevant purpose, access controls, and retention.
When an order is made for a business account, data may be associated with the personal requester and the selected business context. Business member access is determined by membership status, role, and server-side permission checks; choosing a business name in a browser does not itself grant access to read or change data.
Business owners and administrators are responsible for reviewing members, removing access that is no longer needed, and ensuring team instructions are authorized. A business-context switch must not be used to access another business's orders.
Necessary cookies and browser storage help maintain sessions, language choices, security, and local navigation. Email, in-app, or Push notifications are sent through available channels and the preferences you choose, subject to important security or order messages.
We may use technical logs, performance measurements, and aggregate monitoring to keep the service reliable. Document contents, tokens, cookies, passwords, and credentials must not be put into ordinary operational logs.
Retention depends on the data type and purpose: active accounts, ongoing orders, supporting documents, invoices, support notes, audit records, backups, and security needs may have different periods. When a purpose ends and there is no valid reason to retain data, we will delete, anonymize, or restrict it under the available process.
Backups or recovery copies may contain data for a limited time and may not be removable item by item immediately. Backup access is restricted and is not a public page.
We do not sell personal data as a commodity. Data may be shared on a limited basis with:
Data is retained only as long as needed to operate the service, protect users, resolve disputes, or meet applicable obligations. It is then deleted, anonymized, or restricted as appropriate.
We use technical and organizational controls proportionate to risk. No digital transmission or storage can be guaranteed 100% secure, so users must also protect their accounts and devices.
Subject to applicable law, you may request access, correction, restriction, or deletion of certain data. Some information may need to be retained for security, audit, service, or legal reasons. We will explain a decision where reasonably possible.
Cookies or similar technologies may be used for sessions, language preferences, security, and product operation. Disabling necessary cookies may prevent parts of the service from working.
This policy may be updated when the product, processing practices, or legal requirements change. The latest version is identified by the update date above; material changes may receive an additional notice through an appropriate channel.
When you use Google Play purchases on Android, Google processes payment under its terms and privacy policy. Insimen sends the product ID and an obfuscated account identifier, and for event tickets an obfuscated reservation identifier, to link the purchase to the correct account and order.
Insimen receives and retains product IDs, purchase history and status, a Google order ID when available, verification times, and a purchase receipt token encrypted on the server. This data is used to verify payment, grant and restore access, prevent abuse or duplicate charges, and process access revocation and refunds. Status checks use the Google Play Developer API and authenticated notifications from Google.
Insimen does not receive your card number or payment instrument details from this flow. Transaction records and necessary evidence may remain after account deletion to resolve transactions or disputes and meet audit, security, or legal requirements; access for a deleted account remains disabled. Privacy requests can be sent to cs@insimen.com.
Data is processed to deliver requested features, perform transactions, protect security, handle support and meet relevant duties. Grounds may include contract performance, legal duties, valid consent, vital interests, legally established public tasks or legitimate interests balanced against individual rights. The ground depends on the purpose and circumstances, rather than blanket consent to every use.
Insimen determines purposes for its own account and operational processing. For business workspaces, healthcare facilities or organisation documents, another party may act as controller and Insimen as processor according to actual roles and agreements. Uploading another person’s data requires authority and a lawful ground; reuse outside original instructions or purposes requires separate assessment.
Data depends on the service: identity and contact details; submitted content and documents; transaction records; and necessary technical, session and audit data. Health, personal financial and children’s data require additional care. Do not upload unnecessary secrets. The service section below explains its specific data context.
Recipients may include people you choose, necessary service providers, authorised support personnel and authorities acting on lawful requests. Sharing is limited by purpose and need; recipients do not receive a blanket right to reuse data for themselves. Authority requests are assessed for legal power, grounds and scope.
Where processing requires a transfer outside Indonesia, applicable cross-border data-protection requirements must be met, including protection-level assessment, adequate binding safeguards or another legally permitted basis. This policy is not unrestricted consent to send all data to any country or recipient.
Subject to law, you may request processing information, access and copies, correction, cessation or restriction, deletion or destruction, withdrawal of consent, objections to certain automated decisions, and other rights including portability where applicable. Withdrawing consent does not invalidate prior lawful processing; some features may stop if a necessary ground is no longer available.
Send requests to cs@insimen.com with your account and service context. Identity or authority verification is proportionate and does not require passwords or one-time codes. Requests are assessed against your rights, others’ rights, retention duties and statutory time limits. Where a request cannot be fully met, the reason and available next steps are explained through an appropriate channel.
Data is kept for as long as justified by purpose, service status, legal duties, transaction evidence or relevant disputes. Removing a view or account does not always immediately erase every archive and backup. Lawfully retained copies must have restricted access and use; deletion or anonymisation follows applicable processes when retention grounds end.
Necessary cookies or device storage may support sessions, security, language and requested functions. Additional processing requiring consent must respect valid choices. Using the service does not authorise every form of tracking.
If a data-protection incident occurs, Insimen assesses impact, restricts risky access and takes response measures. Notifications to individuals and authorities follow applicable statutory requirements and deadlines. This policy does not promise absolute security or shift incident-response duties to users.
Vehicle details, symptoms, images, location, schedule and contacts support inspection and fulfilment. Share location only as needed; remove or obscure unrelated identity documents and third-party information in photos. Providers must not reuse vehicle or address data without a lawful ground.
