Privacy Policy

We collect information you provide when contacting the studio through forms, WhatsApp, email, or project meetings. This may include your name, phone number, email address, organization or company identity, business needs, content materials, and other information you choose to share.

For certain projects, we may receive technical information such as domain, server, repository, API, or third-party service access. It is requested only when needed for configuration, migration, testing, deployment, or agreed technical support.

When you visit oketa.id, the platform may receive aggregated technical data such as browser type, device, screen resolution, visited routes, traffic source, and performance metrics. This helps us understand site usage and improve experience without seeking excessive identification.

Information is used to answer questions, understand requirements, prepare proposals or quotations, schedule communication, and select an appropriate working approach. We aim to request only information that is relevant to the consultation or service.

During a project, data may be used to manage scope, provide progress updates, process invoices, configure technical environments, validate deliverables, maintain service continuity, and respond to support requests after launch.

Oketa.id Studio does not sell, rent, or trade personal or organizational data to others for marketing purposes. Any use outside the service purpose requires an appropriate basis or relevant consent.

Project communications, invoice records, scope documentation, technical notes, and project materials may be retained as needed for administration, support, maintenance, dispute resolution, and applicable obligations.

Retention periods vary by data type, project status, administrative requirements, backup needs, and active service period. Data that is no longer needed may be deleted, anonymized, or archived according to technical capability and operational requirements.

Clients may request data deletion or return after payment obligations and project work are complete. A request may be limited where the data remains necessary for transaction evidence, security, backups, or legal obligations.

Client internal data, member or user databases, administrative documents, business information, strategies, and non-public materials are treated as confidential information. They are not used for purposes unrelated to the agreed service.

Access to project data is restricted according to work requirements. We aim to separate access, avoid openly storing passwords, and limit credential distribution to people who are assigned to the work.

When technical requirements involve another service provider, data sharing is limited to what is relevant for that purpose. Specific confidentiality requirements or an NDA can be discussed and documented separately when needed.

Projects may use or connect to third-party services such as domain registrars, servers, email providers, analytics, payment providers, communication APIs, repositories, or deployment platforms. Selection is based on project needs, cost, compatibility, and relevant security considerations.

Third-party providers have their own privacy policies, terms, and security practices. We assist with configuration within the agreed scope, but do not control their availability, pricing, policies, or technical changes.

If a client provides access to a third-party service, the client is responsible for ensuring that the access is authorized. Access that is no longer needed should be revoked or rotated after the relevant work is complete.

We apply reasonable technical safeguards based on project scale and requirements, including HTTPS, environment separation, access restrictions, credential handling, input validation, password hashing, and relevant dependency updates during active maintenance.

No system can be guaranteed to be free from every security risk. Security also depends on account management, devices, infrastructure providers, configuration, and user behavior after handover.

Clients must protect their own access, avoid sharing credentials openly, use authorized accounts, and report suspected leaks or unfamiliar activity promptly so the issue can be reviewed.

Clients and users may request information about stored contact data, ask for inaccurate information to be corrected, and request updates or deletion where applicable.

Before completing a request, we may ask for identity or authority verification to prevent data from being changed, deleted, or disclosed to an unauthorized person.

These rights may be limited where a request conflicts with legal obligations, security needs, transaction records, backups that cannot yet be separated, or an ongoing project obligation.

For questions about collection, use, retention, or confidentiality, contact oketadotid@gmail.com or the official Oketa.id Studio WhatsApp channel.

Please provide enough context to help us understand the request, such as your name, relationship to the engagement, relevant data type, and requested action. Do not send passwords or sensitive credentials through ordinary messages.

We may update this policy when services, processes, security requirements, or relevant obligations change. The latest version and update date will remain available on this page so changes can be reviewed clearly.