Legal

Privacy policy

PT Teknologi Otomatis Indonesia · Effective 15 November 2026

This policy explains what personal data PT Teknologi Otomatis Indonesia ("Tekomata", "we") processes when you use tekomata.com, why, who we share it with, how long we keep it, and how you can have it corrected or deleted. It is written to comply with Indonesia's Personal Data Protection Law (Law No. 27 of 2022).

1. Who is responsible

For your own account, PT Teknologi Otomatis Indonesia is the data controller. For the data a shop enters about its own buyers, suppliers and contacts, the shop is the controller and Tekomata processes that data on the shop's behalf and only to provide the service.

  • PT Teknologi Otomatis Indonesia
  • Email: halo@tekomata.com

2. What we collect

  • Account data: your name, email address, business name, and a password stored only as a one-way hash.
  • Sign-in data: session tokens (stored hashed), email verification codes and password-reset links, which expire.
  • Business data you enter: products, prices, stock, invoices, payments, purchase records, settings, uploaded import files, and the knowledge you give your AI about your business.
  • Contact data about other people that you enter: names, phone numbers, email addresses, addresses and tax numbers of your buyers and suppliers.
  • Billing data: top-up requests, transfer references, credit balance and plan purchases.
  • Verification documents, only when a shop chooses to verify itself: its NIB, or the owner's KTP and a selfie holding it, the name on them and the NIK's last 4 digits (section 7).
  • Email records: to whom we sent an email, its subject and whether it was delivered.
  • Technical logs: IP address, request path, time and a request identifier, used to operate and secure the service. Some logs contain the email address involved in a sign-in or an email we sent.
  • Cookies: a sign-in cookie, a language preference cookie, and for Tekomata staff a separate dashboard cookie. On Tekomata's own public pages, Google Analytics cookies that count visits, which you can turn off (section 12). We use no advertising cookies.

3. Why we use it

  • To provide the service you signed up for: your catalogue, invoices, stock and billing.
  • To send the emails the service needs: verification codes, password resets, invoices you choose to send, payment reminders and top-up notices.
  • To keep the service secure: preventing abuse, investigating problems and limiting repeated sign-in attempts.
  • To meet legal obligations, including record-keeping required by Indonesian law.

We do not sell personal data, and we do not use it for advertising.

4. Who we share it with

Only the service providers needed to run Tekomata, bound to use the data only for that purpose:

  • Hosting and network providers that store and deliver the service. Their servers may be located outside Indonesia; where that happens we rely on the safeguards Law No. 27 of 2022 requires for transfers abroad.
  • An email delivery provider, to send the emails listed above.
  • Artificial intelligence providers, only when a shop chooses to scan images or a web page into its AI knowledge: those images or that page text are sent to the provider to be read, and Tekomata does not keep the images. What the provider suggests is saved only if the shop reviews and saves it.
  • Artificial intelligence providers, only when a shop turns on an AI agent to answer its customers: for each conversation that agent answers, the recent messages in it, the shop's instructions and the shop's knowledge are sent to the provider so it can write the reply. The provider is one of Anthropic, OpenAI, xAI or Google, chosen by Tekomata. When a shop uploads screenshots of its chats to shape how its agent talks, those images, which can show its customers' names and messages, are sent to the provider to be read and are not kept by Tekomata. A shop that does not turn on an agent or upload chat screenshots sends no customer message to any AI provider.
  • Meta Platforms, when a shop connects its Instagram account: replies the shop writes are sent to Instagram through Meta's API so they reach the customer.
  • Google, when a shop connects its Google Calendar: the meetings the shop schedules are written to its own Google Calendar (section 6).
  • Artificial intelligence providers and Amazon Web Services, when a shop verifies itself (section 7).
  • Google, through Google Analytics, for visitors to Tekomata's own public pages who have not turned it off (section 12).

We disclose data to authorities only when Indonesian law requires it.

5. WhatsApp and Instagram

A shop can connect its Instagram professional account to Tekomata. When it does, we receive from Meta: the direct messages customers send to that account and the account's replies (text, and the attachment links Meta provides), each customer's Instagram-scoped ID for that account, and the customer's name and username. The account's access token is stored encrypted.

A shop can also connect its own WhatsApp Business number, through Meta's sign-up window. When it does, we receive from Meta: the messages customers send to that number and the replies sent from Tekomata, the files customers send (photos, documents, voice notes), which we keep because Meta deletes them after 7 days, each customer's phone number and WhatsApp profile name, and the ids of the number and its WhatsApp Business account. When the shop keeps the number on the WhatsApp Business app on its phone, we also receive the chats already on that phone, the replies typed on the phone from then on, and the names the shop saved for its contacts. The access token, and the verification PIN we register the number with, are stored encrypted. Message templates the shop writes are sent to Meta for review and read back from Meta; we do not keep a copy.

We use this data only to show the shop its conversations and to send the replies the shop writes, or that the shop's AI agent writes when the shop has turned one on (section 4). It is not used for advertising and not sold. Raw notifications from Meta are deleted 7 days after they are processed. Disconnecting the account deletes its token; the conversations stay as the shop's records until the shop or the customer asks for them to be deleted. Connecting a WhatsApp number opens to every shop once Meta approves Tekomata; until then it is available only to accounts Meta lets us test with.

6. Google Calendar

Each person using Tekomata can connect their own Google account's calendar, from Settings, Account. Google asks them to allow exactly these, and Tekomata asks for nothing else:

  • To make a new calendar for each company they work in, called "Tekomata · " and the company's name, and to create, read, change and delete events in those calendars only (the calendar.app.created permission). Tekomata writes there the events the person makes in Tekomata (a title, notes, a place, a start and an end, a colour, a repeat and a reminder), and reads back the events made or changed in those calendars, so they appear in Tekomata too. Each event can be kept out of Google by unticking it. Unless the person switches it off, Tekomata adds their own Google address as the only guest of their events, accepted and with no invitation email, so the events also show in their main Google calendar; no one else is ever added.
  • To see when the person is busy or free (the calendar.freebusy permission). Only the times are received: never the titles, descriptions, locations or guests of their other events. They are fetched when a meeting is scheduled, shown to the person, and not stored.
  • The account's email address (openid and email), stored to show the person which account is connected.

Tekomata does not read, change or delete any other calendar or event, and does not access the shop's email, contacts, files or any other Google data. The access Google gives is stored encrypted. Meetings are also kept in Tekomata as the shop's records, so a meeting is not lost when Google cannot be reached.

Data received from Google is used only to provide this feature to the shop that connected it. It is not used for advertising, not sold, not shared with anyone else, and not used to develop, improve or train artificial intelligence or machine learning models. No person at Tekomata reads it, except with the shop's permission, to investigate abuse or a security problem, or where the law requires.

Tekomata's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.

The person can take the access back at any time: Disconnect under Settings, Account revokes it at Google and deletes the stored access and the account's address from Tekomata at once; removing Tekomata under Third-party connections in the Google account does the same from Google's side. The "Tekomata" calendars stay in the Google account, which the person can delete there.

Signing in with Google: when a person chooses "Sign in with Google", Google sends Tekomata their Google account's id, email address and name (openid, email and profile). The id links the Google account to their Tekomata account; the address and name fill in a new account, which still has its own password. Nothing else in the Google account is received, and the link can be removed at any time under Settings, Account.

7. Business verification (NIB, KTP, selfie)

A shop can verify itself under Business verification, in the menu beside Company: a business with its NIB, or a person with their KTP and a selfie holding it. It is optional, and done only with the consent ticked on that form.

  • Reading: the documents are read by an artificial intelligence provider (one of Anthropic, OpenAI, xAI or Google, the best that reads images), which suggests the name and number it sees and flags what looks wrong. It never decides. A person at Tekomata reviews the documents and approves or refuses.
  • While waiting for that review, the documents are stored privately and seen only by Tekomata's reviewers.
  • At the decision, each document is encrypted where it is stored, with a key of its own, and that key is locked with a key held by Amazon Web Services' key service. The key that unlocks never leaves Amazon, so Tekomata's own server cannot open the documents again: a copy of the server, the database or a backup holds only scrambled files. No document and no NIK is sent to Amazon, only each document's locked key.
  • Opening one again: only when truly needed, for example a dispute or an official request from the authorities. It needs a written reason, and a permission that is closed by default and that only Tekomata's owner opens, for 15 minutes at a time. Every opening, and every refused try, is logged with who, when, which document and why.
  • Kept: the encrypted documents are kept with no end date, as proof of the verification. Outside them, only the name and the NIK's last 4 digits are kept.

8. How long we keep it

Account and business data are kept while your account is active. When you ask us to delete your account, we delete it within 30 days, except records we are legally required to keep, which are retained only for that period and for no other use. Sign-in codes and links expire within hours. Technical logs are kept only as long as needed to operate and secure the service. Encrypted verification documents are kept as section 7 says.

9. Your rights

Under Law No. 27 of 2022 you may ask us to tell you what data we hold about you, give you a copy, correct it, stop processing it, or delete it, and you may withdraw consent. Most account data can be corrected directly in the app. For anything else, email us from the address on your account and we will respond within the time the law requires.

If you are a buyer or supplier of a shop that uses Tekomata, please contact that shop first; it controls your data. You may also contact us and we will pass your request on.

10. Security

Passwords, session tokens and reset links are stored only as hashes. Connections use HTTPS. Access to the internal dashboard is limited to Tekomata staff, and staff actions are logged. Staff enter your own workspace only when you allow it from Bantuan, for at most 24 hours; you can end it at any time, and everything they do is in your audit trail. Verification documents are encrypted at the decision with a key Tekomata's server cannot open them with (section 7). No system is perfectly secure; if a breach affects your personal data we will notify you and the authorities as the law requires.

11. Deleting your data

Email halo@tekomata.com from the address on your account and ask for your account to be deleted. We will reply, and we delete your account, your sessions and your business data within 30 days, except records we are legally required to keep.

If you are a buyer or supplier recorded by a shop that uses Tekomata, tell us which shop. That shop controls your data and we will pass the request to them.

To take back Tekomata's access to a Google account without deleting your Tekomata account, disconnect it under Settings, Account (section 6).

13. Changes

We will update this page when what we collect or how we use it changes, and change the effective date above. Significant changes will be announced by email to account holders before they take effect.