Privacy Policy

Last updated: 4 November 2026

This policy explains what personal data Worg collects, why, who else handles it, and what you can ask of us. It covers getworg.com and its subdomains, including the console and the API.

This policy is made in Indonesian and English. If the two versions differ, the Indonesian version prevails.

1. Who we are

Worg is run by PT Matrix Studi Karir, Jl. Palagan Tentara Pelajar, Gg. Teratai II, Jongkang, Sariharjo, Ngaglik, Sleman, Daerah Istimewa Yogyakarta 55581, Indonesia. PT Matrix Studi Karir is the data controller for the personal data described here, under Law No. 27 of 2022 on Personal Data Protection (UU PDP).

Our contact for personal data protection is team@getworg.com. Send any question or request about your data there.

2. What we collect

Account

• Your email address, your name if you add one, the name of your organization, and your role in it.
• When you accepted the terms, when you last signed in, and whether two-step verification is on. The two-step secret is stored encrypted. Recovery codes, sign-in links, and session tokens are stored only as hashes. Your sign-in password is stored only as a hash made with scrypt, never as plain text, and is never logged.

Billing

• The billing details you fill in for your organization: billed-to name, billing email, address, and tax ID (NPWP).
• Each top-up: invoice number, amount in rupiah and US dollars, exchange rate, status, and time. Your payment details (card, bank account, or e-wallet) are entered with the payment partner and are not stored by Worg.

API requests

• Metadata for each request: time, organization, workspace, key, model, status, error code, token counts, rate, cost, and timing. Usage and Billing in the console are built from it.
• For API keys, a hash and the first characters (the prefix). The full key is shown once and never stored.

Console activity

• A log of sensitive actions, such as creating or resuming a key or changing a role: who did it, what, and when. It holds no IP address.

Referrals

• If your organization signed up through another organization's referral link, we record which organization invited you, the date of your first paid top-up, and the referral credit your usage earned for them. If your organization invites others, we record its referral code and the credit it earns.
• To check that two organizations are not the same one, we compare the email addresses of their members, their email domains (public email services aside), and the tax IDs (NPWP) in their billing details; a match found later is reviewed by our team. This uses data we already hold; we collect nothing new for it.

Contact and support

• Your WhatsApp number, if you add one in the console for setup help. It is optional, and we keep the time you gave consent.
• Details of your organization's main contact that you or that person give us, for example by email or in a meeting: name, job title, email, and WhatsApp number.
• Notes our team writes about your organization's account, such as what we agreed in a call or which setup step you are on. Notes do not contain your prompts or outputs.
• If you ask for a meeting in the console: the topic, whether you want to meet online or in person, the times you suggest, your WhatsApp number, and any note you add.

Messages

• Emails you send to team@getworg.com or our other getworg.com addresses, and WhatsApp messages you send to our number.
• What you send through the contact form on getworg.com: the topic, your name, work email, company or project name, expected monthly spend if you choose a volume or data topic, and your message. It reaches us as an email and is not stored in our database.

3. What we do not store

• Prompts and outputs. The content of your requests passes through our servers in memory on its way to the model and back to you. It is not written to a database or a log. Cloudflare also sees it in transit (section 5). Playground conversations are saved only in your browser, on that device, and you can delete them with Clear history.
• Your IP address. Our servers do not write it to a database or a log. A few limits, such as how many sign-in emails an address can request, the free try on the website demo, or how many messages it can send through the contact form, keep a salted hash of it in memory only. That memory is cleared when the server restarts. Cloudflare, which sits in front of our sites, does see it (section 5).
• Website demo. What you type in the demo on getworg.com goes to a model and back, and is not stored.

Worg does not use your prompts or outputs to train models.

4. Why we use it

• To run your account and the API, charge each request, and show your usage and billing. This is needed to perform our agreement with you.
• To run the referral program: credit the organization that invited you, and show it how far your organization is (the first two letters of its name, the date it signed up, and whether the program's conditions are met, never your top-up or usage amounts). This is needed to perform our agreement with the inviting organization. We compare members' email addresses and domains and tax IDs to prevent abuse of the program, on the basis of our legitimate interest in preventing fraud.
• To send service emails: sign-in links, top-up receipts, budget and low-balance warnings, key suspension notices, and a reminder to turn on two-step verification. These emails have open and click tracking turned off.
• To help you set up Worg and answer support questions on WhatsApp, if you added your number for this. This is based on your consent. You can withdraw it by removing the number in the console.
• To look after your organization's account: keep its main contact and our notes, and see when a top-up failed, requests keep returning errors, or no one has signed in for a while, so we can offer help. We do this on the basis of our legitimate interest in supporting the organizations we have an agreement with.
• To arrange a meeting you ask for and contact you about it on WhatsApp. This is needed to act on your request, before or under our agreement.
• To answer messages you send us, including complaints and requests about your data. We do this on the basis of our legitimate interest in replying to you, or to take steps you ask for before entering into an agreement.
• To run and monitor the service: our team receives notices about payments, balances, keys, and incidents in a private group chat, and uses an AI assistant to look up account information (section 5). We do this on the basis of our legitimate interest in operating the service and responding to problems quickly.
• To keep the service safe: rate limits, spending limits, automatic suspension of keys with unusual spend, and the action log. We do this on the basis of our legitimate interest in protecting the service and your account.
• To keep the financial records that tax law requires. This is a legal obligation.

We do not send marketing email or marketing messages on WhatsApp, and we do not sell personal data.

5. Who else handles your data

We use these service providers to run Worg. Each handles only what its job needs.

• Inference partners. Our models run on GPUs operated by inference partners in Indonesia. We share partner names with customers under a signed contract or NDA. Partners receive the content of each request (your prompts and the settings you send, including an end-user identifier if you put one in the user field) and return the output. They do not receive your email, your key, or your IP address, and they receive account details only in requests from our team's assistant (below). Their terms bar them from using request content to train models.
  • To speed up repeated requests, partners keep parts of recent requests in memory, not on disk, for a limited time. At one partner this cache lasts up to 7 days and is shared between its customers.
  • Some models run an automated misuse check at the partner. It records a flag with the time, the category of the problem, and the end-user identifier if you sent one, but not the text.
  • Partners use their own service providers, for example for network delivery, which may carry request content in transit.
  • When its own servers cannot take a request, a partner may pass it to another provider, which may be outside Indonesia.
  • Our team uses an AI assistant that runs on these same models through the Worg API to help operate the service. When our team asks it about an account, its requests can include your organization's name, balance, top-ups, usage figures, and API key names, but not email addresses or the keys themselves. Partners handle these requests like any other request.
  The cache times above come from the partners' published terms. Until each partner confirms in writing where it processes every request, we make no commitment that every request is processed in Indonesia.
• DOKU, our payment partner for rupiah top-ups. It receives the invoice number and amount, and you enter your payment details with DOKU or in your bank or e-wallet app. For now the payment page and your bank app show TokenomixAI, another service run by PT Matrix Studi Karir, whose merchant account we use. TokenomixAI is not a separate party.
• Resend, which sends our emails. It receives your email address and the content of the email, including what you send through the contact form.
• Cloudflare, which provides DNS and sits in front of all our sites to protect and deliver them. It sees your IP address and the content of the requests passing through, including API prompts and outputs, because it decrypts and re-encrypts traffic on its network. Cloudflare also runs the bot check (Turnstile) on the website demo and the contact form, receives mail sent to our getworg.com addresses and keeps it in our mailbox, and stores our encrypted backup copies (section 7).
• Our server provider, a cloud server provider whose data centre in Jakarta, Indonesia hosts our servers and database.
• Google (Google Meet and Google Calendar), where we hold online meetings you ask for. For a meeting it receives your name and email address in the invitation, and the audio and video of the call. We do not record meetings unless everyone agrees at the start.
• Telegram, where our team receives notices about the service in a private group. A notice can name your organization and show its balance, its top-ups, or the names of its API keys. If our team resets or disables your console login, the notice includes your email address. Notices never contain prompts, outputs, IP addresses, or the keys themselves, and they stay in the group until our team deletes them.
• WhatsApp, run by Meta, where our team uses the WhatsApp Business app to talk with you if you gave us your WhatsApp number, asked for a meeting, or message us there. Each message is written and sent by a person on our team. WhatsApp receives your number and the messages.
• The organization that invited you, if you signed up through a referral link. On its referral page in the console it sees the first two letters of your organization's name, the date it signed up, and whether the program's conditions are met. It does not see your top-up or usage amounts.

We may also share data when Indonesian law requires it, for example on a lawful request from an authority.

6. Data outside Indonesia

Some of the providers above, including Cloudflare, Resend, Google, Telegram, and WhatsApp, process data outside Indonesia, and so may the provider an inference partner falls back to (section 5). They do it so that our sites can be delivered and protected, our emails sent, mail to us received and kept in our mailbox, our team notified about the service, and so that we can message you and meet with you online. The risks are that authorities in those countries may request the data and that Indonesian law may not apply there. We reduce them by sending each provider only what its job needs, by keeping our database on our servers in Indonesia, and by encrypting backups before they leave our server.

7. How long we keep it

• Account, billing, and request records are kept while your organization's account is open. When an account closes, we keep billing and payment records for 10 years on our servers in Indonesia, as Indonesian tax law requires, and delete other account data when you ask.
• If you remove your WhatsApp number or withdraw consent, we delete it within 3 x 24 hours. When an account closes, we delete WhatsApp numbers given in the console within 30 days, and contact details and notes 12 months later, unless they are needed for a billing record or an open dispute.
• Meeting requests are deleted 90 days after the meeting date, or 90 days after the request if no meeting takes place.
• Messages sent to team@getworg.com or our other getworg.com addresses, or through the contact form, and our replies, are deleted 12 months after the last message in the conversation, unless the conversation led to an account or an agreement, or concerns billing or a dispute. Those we keep as long as the records they relate to.
• Referral records (who invited whom, and the credit earned) are billing records: we keep them as long as the billing records they relate to.
• Sign-in links expire after 15 minutes and work once. A console session lasts 7 days.
• We back up the database every day. Backups on our server are kept for 14 days. Each backup is also encrypted before it leaves the server and copied to Cloudflare R2, where it is kept for up to 90 days. The key that opens these copies is not on the server or at Cloudflare. Deleted data can stay in a backup until that backup expires.

8. How we protect it

• All traffic to our sites is encrypted (HTTPS), and our servers accept connections only through Cloudflare.
• API keys, sign-in links, sessions, and recovery codes are stored as hashes. Two-step secrets are encrypted.
• The console session cookie cannot be read by scripts and is sent only to the console.
• Access to our internal admin tools needs a separate sign-in with two-step verification, and every change made through them is logged.

If a breach affects your personal data, we tell you and the authority in writing within 72 hours of becoming aware of it, with what data was affected, when and how, and what we are doing about it.

9. Your rights

Under UU PDP you can ask us to:

• tell you what personal data we hold about you and give you a copy;
• correct data that is wrong or incomplete;
• delete your data, or stop or limit how we process it;
• withdraw consent where we rely on it;
• object to a decision made only by automated processing. Worg makes no such decisions about you.

We answer requests to access, correct, withdraw consent, or limit processing within 3 x 24 hours after we confirm your identity. When we delete data at your request, we tell you within 3 x 24 hours.

You can change your name, your organization's billing details, and your WhatsApp number in the console yourself. For anything else, email team@getworg.com from the address on your account. We may need to confirm your identity first. If you are not satisfied with our answer, you can complain to the authority that oversees personal data protection in Indonesia.

If you are a member of an organization, the organization's owners and admins manage your membership. If you are a user of a product built on Worg, that product's company decides what it sends to us. Contact them first.

10. Cookies and browser storage

• The console sets one cookie of its own, a session cookie that keeps you signed in. It is needed for the console to work.
• All our sites (getworg.com and its subdomains) share one preference cookie, worg-theme, which holds only your theme choice: light, dark, or system. It lets the choice follow you from one of our sites to another. It holds nothing about you, and our servers do not read or keep it.
• The console also saves, in your browser, which organization you last chose, whether it already offered you two-step verification in this tab, and display preferences such as theme, currency, and sidebar layout. Our website and docs save your theme choice and the language you picked for code examples, and the website also saves when you used the free demo answer. None of this is sent to us.
• The Playground saves your recent chats in your browser (up to 50) so you can reopen them from History. They are not sent to us for storage. Clear history in the Playground deletes them, and so does clearing site data in your browser.
• We use no analytics or advertising cookies.
• Cloudflare sets no cookies on our sites. The bot check on the website demo and contact form runs in a frame from Cloudflare's own domain (challenges.cloudflare.com), not ours.

11. Changes to this policy

When we change this policy, we update the date at the top. For changes that affect how we use your data, we email organization owners at least 14 days before the change takes effect.

12. Contact

PT Matrix Studi Karir, Jl. Palagan Tentara Pelajar, Gg. Teratai II, Jongkang, Sariharjo, Ngaglik, Sleman, Daerah Istimewa Yogyakarta 55581, Indonesia. Email team@getworg.com.