Insimen
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 Insimen, including user rights, the parties’ duties and how to contact support. General and service provisions are read together with applicable transaction agreements.
Last updated: September 28, 2026
Supplemental policies updated 24 October 2026. Specific agreements retain the versions shown in their documents.
This policy applies to the Insimen space for statuses, profiles, conversations, community features, and connected business accounts.
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.
Insimen data comes from your profile, statuses, comments, reactions, follows, reports, Chat, group invitations, audience settings, device, and interactions. Some data is created by other members, such as when they mention your account, invite you, or interact with your status.
We use that information to show spaces and notifications connected to your account, enforce privacy, prevent abuse, and provide the functions you request.
A status may have a public, followers, business-team, or private audience. The server determines access using status state, follow relationship, business membership, and active context; a browser UI or visible URL does not change that decision. We may retain what is needed to apply visibility changes consistently.
When a status is made for a business account, the business identity, acting member, and relationship to the business may be stored so history, notifications, and audits are not confused with a personal account.
Chat content and attachments are processed to deliver messages, show history a user may see, synchronize receipts, unread state, replies, edits, deletions, and security features. Access is limited by session, membership, invitation status, visibility periods, history boundaries, and per-account deletion.
When a message is reported, the minimum snapshot needed for review may be stored with reporter identity, the reported user, time, and security metadata. A moderation snapshot is not sent to the public timeline and is not public data.
If you enable email, web, or Push notifications, we store the subscription or channel preference needed to deliver them to the correct session. Browser permission can be revoked on a device; that does not automatically erase activity records or conversation content.
We may retain technical data about browser, connection time, delivery failures, and session state to prevent cross-account delivery and remove invalid subscriptions. Capability endpoints and tokens are not put in ordinary logs.
Retention differs for public content, Chat history, attachments, moderation reports, audits, and security data. We delete, anonymize, or restrict data when its purpose ends unless there is a valid reason to keep it. Backups and incident snapshots may follow separate cycles.
You can use settings to change status audience, who may start a Chat, notifications, or account context. Access, correction, restriction, and deletion requests may require identity verification and exceptions for other members' data or records that must be retained.
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.
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.
Public information may be read, shared, or saved by others through available service functions. Changing visibility or deleting content in your account does not ensure that copies already received by others are deleted. Messages, attachments, membership lists, and conversation history follow applicable permissions, membership status, and access periods.
Use members’ contact information only for lawful communication. Do not export conversations or collect profiles for spam, surveillance, marketing, or identification without a lawful basis. Handling a report may require limited review of relevant content and metadata.
