Skip to main content

JobsBuild Privacy Policy

How Jobs Ventures, Inc. handles personal information when people visit, create an account, publish a site, or submit a response through JobsBuild.

Version 2026.08.26 · Effective date 2026-08-26

1. Controller, scope, and contact

Jobs Ventures, Inc. operates JobsBuild and is the controller for account, platform-operation, security, and support information described here. This Policy applies to JobsBuild at jobsbuild.kr and its platform-hosted pages. Privacy questions and requests may be submitted through the public, non-payment contact path at https://jobsventures.com/contact. Select or state that the message is a JobsBuild privacy or data-rights request so it can be handled separately from a sales inquiry.

2. Platform and site-owner roles

For JobsBuild account and platform data, Jobs Ventures, Inc. determines the purposes described in this Policy. For personal information that a visitor submits to a user's published site, the site owner determines the offer, form, purpose, and follow-up and is normally the primary controller for that customer relationship; JobsBuild processes the information to provide the form, inbox, security, and response functions. The published site must identify its owner and present any additional notice required for that owner's use.

3. Information and sources

We receive account details such as name, email, preferred language, birth date used for the adult eligibility check, authentication state, and account settings; offers, sites, files, content, links, drafts, approvals, and support messages submitted by users; inquiry details and consent records submitted by site visitors; and service data such as timestamps, route and feature events, device and browser information, coarse network and security signals, rate-limit keys, audit records, and error diagnostics. We receive information directly from users and visitors, from their use of the service, and from service providers used to operate requested functions.

4. Purposes and legal bases

We use information to create and secure accounts; provide editing, publication, inquiry, export, deletion, and response tools; preserve user-approved state; prevent abuse and investigate incidents; communicate necessary service or authentication information; comply with law; and improve reliability and accessibility. Depending on the context, processing is necessary to perform the service contract, comply with law, protect legitimate security and operational interests, or act on consent where consent is required. We do not use private customer content for unrelated advertising.

5. Public pages, inquiries, cookies, and analytics

Published site content is public by the user's choice. Inquiry forms collect only the fields shown with the form and record consent and delivery state so duplicate submissions and responses can be handled safely. JobsBuild uses essential cookies or similar storage for authentication, security, locale preference, recovery, and user-requested state. We do not sell personal information or share it for cross-context behavioral advertising. Any optional analytics or marketing cookie will require a separate disclosed control before use where required.

6. Service providers and disclosures

JobsBuild uses Vercel for application hosting and delivery; Supabase for authentication, PostgreSQL database, and storage in the configured AWS ap-northeast-2 project region; Upstash for distributed rate limiting; hCaptcha for signup and abuse protection when hosted protections apply; and Resend or the configured authentication-email channel for required service email. Error monitoring may use Sentry only when configured. These providers process only the data needed for their function under their applicable service terms. We may also disclose limited information when required by law, to protect rights and safety, or in a properly governed corporate transaction.

7. Cross-border and international processing

Jobs Ventures, Inc. is a United States company. Vercel, Supabase support and infrastructure, Upstash, hCaptcha, Resend, and Sentry may process or support service data in the United States, Korea, and other locations used by their controlled infrastructure and subprocessors. The Supabase production database project is configured in AWS ap-northeast-2 (Seoul). Transfers occur electronically when a requested service or security function runs and are limited to the categories described above. We use contractual, access-control, encryption, minimization, and provider-governance measures appropriate to the transfer. Provider and location details will be updated before a materially different transfer is enabled.

8. AI processing is currently disabled

JobsBuild does not currently send account or customer content to an AI model provider because AI capabilities and provider selectors are disabled. If optional AI is activated later, the service will identify the provider path, data categories, purpose, location, retention boundary, user control, and applicable terms before the first transfer. A child result, draft, or UI label cannot by itself enable an AI transfer.

9. Payment processing is currently disabled

JobsBuild native subscription checkout, native customer checkout, settlement, and AI-credit purchases are currently disabled. An external payment link is controlled by the site owner and the external provider; JobsBuild records only the link and permitted response event and does not receive raw card details. Before native payment processing is activated, this Policy and the applicable payment notices will identify the provider, data, purpose, retention, and user choices.

10. Retention and deletion

We keep account and user-controlled content while the account is active and as needed to provide the requested service. The account-deletion workflow permanently deletes authentication and user-controlled site content and anonymizes personal fields in records that must remain. Security, audit, dispute, transaction, and legal records are retained only for the period necessary for the stated purpose or applicable law, then deleted or de-identified. Backups and provider caches expire on their controlled cycles and are not restored to reactivate a deleted account. Legal holds pause deletion only for the affected records.

11. Rights and choices

Users can access and correct profile information, select a product language, export structured account data, and delete an account from Settings. Depending on applicable law, a person may request access, correction, deletion, restriction, objection, portability, or withdrawal of consent and may complain to the relevant privacy authority. Submit a request through the contact path in section 1. We may verify identity and authority, respond within the applicable period, explain any lawful refusal, and avoid exposing another person's information.

12. Security and incident handling

We use encrypted transport, scoped service roles, row-level access controls, authentication controls, secret separation, rate limits, audit trails, release gates, backups, and values-free operational receipts appropriate to the service. No system is perfectly secure. We investigate suspected incidents, contain affected paths, preserve necessary evidence, and provide notices required by applicable law without exposing unrelated personal information.

13. Adults only

JobsBuild public business accounts are for people 18 years or older. We do not knowingly open a public account for a child. If we learn that a child created an account contrary to this rule, we will restrict the account and delete or otherwise handle the information as required by law. A visitor may contact a site owner through a published form only with the permission and supervision required by applicable law.

14. Policy changes

We publish the policy version and effective date. Material changes will be announced in advance when required. A policy change cannot silently activate AI, payment, customer communication, or another external data path; those paths remain subject to their technical and operational approval controls. English and Korean policies are intended to describe equivalent platform practices for their signup locales.