Privacy notice
This notice explains how AJAG Labs, part of Ajag Studio Indonesia, handles information in Data Analytics, Media Intelligence, and Conversation.
Information you provide
We store account details, uploaded files, collected records, analysis results, reports, approved knowledge, and workspace settings needed to deliver the application. Conversation also stores messages, staff replies, and booking details. Avoid including sensitive information unless it is necessary and you have authority to share it.
How information is used
Your information supports the actions you request: analysis, monitoring, search, reports, answers, and service workflows. Authorized workspace members can access information according to their roles. Public demo accounts use isolated sample data and cannot read private visitor conversations.
Voice input and spoken replies
The microphone is off until you enable it and grant browser permission. A recording is sent to the AJAG server for transcription. Temporary audio files are removed after processing; the text appears in the message field for you to review before sending. Sent text becomes part of the conversation.
Spoken replies use your browser or operating system’s speech service. Some voices may use that provider’s online processing. They are optional and can be stopped at any time.
Engines and external services
Configured local models process text, embeddings, summaries, and speech on the AJAG server. Collection through Apify sends the selected query, source URLs, and run settings to Apify and the chosen Actor. Workspace administrators control these connections. Follow external links only if you accept the destination’s privacy practices.
The public tourism example uses simulated tickets and payments. It does not collect money. Real payment processing is not enabled in that example.
Storage and retention
Application records are stored on our hosted server. Backups support recovery. Records remain available until an authorized deletion or retention action is performed; there is currently no automatic deletion schedule for workspace content. Removing a record from the active application may not immediately remove it from existing recovery backups.
Server logs may contain IP addresses, request paths, timestamps, and error information used to operate and protect the service. Do not place personal information or secrets in URL query strings.
Cookies and your choices
We use essential account and conversation cookies. We do not load advertising pixels or visitor analytics trackers on the landing page. Read the cookie details or . Microphone access and spoken replies are separate, optional controls inside Conversation.
Requests and concerns
You can ask for access, correction, deletion, or raise a privacy concern through our privacy request form. Requests go to the AJAG administration queue. We may need to verify your identity and the relevant workspace before taking action. Sending a request does not automatically delete records or cancel a booking.
If you use a service operated by another organization through Conversation, also contact that organization about its handling of customer information.