Skip to content

Legal

Privacy Policy and KVKK Notice

Personal data, choices and rights requests across Ops and Marketplace.

Last updated: October 23, 2026

Controller and contact

GigNode is operated by Egehan Tütüncü, an individual founder in Türkiye. No company has been incorporated. Contact: support@getgignode.com. Postal/service address: [to be supplied by the founder].

GigNode acts as controller for account, security, Marketplace and support processing. For third-party data a customer enters in a workspace, the customer may determine the purposes and GigNode processes it on their instructions to provide the service. Roles depend on the processing context.

Data and sources

  • Account: email, name, language, password verifier, sessions and two-factor authentication information where enabled; Terms acceptance and notice version/timestamp records.
  • Ops: workspace/team membership, client/contact details, projects, files and links, deliverables, feedback, revisions, approvals and activity; tracking fields such as amount, due date and payment status. GigNode does not collect payments.
  • Marketplace: client/provider profiles, country, phone, time zone, services, capabilities, portfolios, requests and attachments, proposals, acceptance and engagement records, reviews and reports. Published profile and portfolio information may be public.
  • Support and communications: request/message content, recipient, delivery/error and rights-case records. Beta access request email and language; this is not a general marketing subscription.
  • Security and technical data: necessary IP/network, browser/device context, timestamps, access and abuse records. Separately optional analytics/performance and limited referral/campaign measurement.
  • Data comes from you, authorised workspace members, clients/providers you interact with and technical records generated by the service. Do not upload unnecessary sensitive data or data you are not authorised to share.

Purposes and legal grounds

  • Account creation, authentication, recovery, Ops project/portal and Marketplace request/proposal/acceptance flows, file delivery and requested transactional notices: KVKK Article 5(2)(c) and, where GDPR applies, Article 6(1)(b), to the extent necessary for a contract.
  • Security, fraud prevention and reliable operation: necessary legitimate interests balanced against your rights (KVKK Article 5(2)(f); GDPR Article 6(1)(f)). Records necessary to establish, exercise or defend rights may fall under KVKK Article 5(2)(e).
  • Specific legal obligations: KVKK Article 5(2)(ç) and GDPR Article 6(1)(c) only where an actual obligation applies. We do not assume every record has a mandatory legal retention period.
  • Optional analytics and referral/campaign measurement: separate, withdrawable consent per category (KVKK Article 5(1); GDPR Article 6(1)(a)). Refusal does not prevent accounts or essential services. Receiving a notice and accepting Terms are not blanket consent.

Matching and visibility

Marketplace matching uses rules based on profile, service, preference and request fields; it does not use an external AI decision service. Scores and profile review do not guarantee work or quality. Contact support to question results or correct information about you.

Files, portals, proposals and workspace information are shared according to product permissions. Share portal or proposal access links only with authorised recipients.

Recipients and infrastructure

  • Supabase: authentication, the shared Postgres database and file storage.
  • Vercel: app hosting and deployment; Web Analytics and Speed Insights only with the analytics choice.
  • Cloudflare: DNS/network security and Turnstile bot checks on protected forms. Support-email routing is disabled. Turnstile also describes bot-detection improvement purposes in its own notice.
  • Resend: the Supabase Auth SMTP provider for account verification and password recovery. Application transactional email also uses this integration when its delivery configuration is enabled.
  • Google Workspace: the support@getgignode.com support mailbox/alias. The founder reports setup and CDPA acceptance. Historical correspondence may remain in the former personal Gmail account.
  • GitHub Actions: configured backup workflows. Processing of backup content depends on the account and runner arrangement used.
  • Authorised workspace members, clients/providers, recipient email providers and competent authorities where required. There is no feature sending private files to an external model for AI training.

International processing

Infrastructure, email, network and backup providers may process data outside Türkiye. Existing configuration records identify Germany for Supabase, Frankfurt for Vercel functions and Japan for Resend sending; these do not restrict all storage, support, network or subprocessor locations. Resend documents also describe US processing. Google, Cloudflare and GitHub may involve global processing/access.

Verification of the applicable KVKK Article 9 basis for these recurring transfers is incomplete. A service agreement or GDPR standard clauses alone do not cure that gap. Registration is not consent to international transfers. Affected flows must not open to real users until a valid transfer route is established.

Retention by category

  • Account and security: while needed for the account and authorised access; security records as necessary for incident review and protection of rights. There is no single period or anonymisation guarantee for all logs.
  • Ops/Marketplace: during service and engagements, followed by assessment of the applicable legal basis, retention duties and other parties’ rights. Accepted proposal and transaction snapshots may form audit history; a profile correction does not automatically rewrite historical records.
  • Support/rights requests: while needed to resolve the request and evidence the response/action; only necessary identity and authority evidence is retained.
  • Beta access requests: the current flow records a 90-day retention target; this is not guaranteed automatic physical deletion. Review and cleanup are tracked through support.
  • Preference record: 180 days; language choice: one year. See the Cookie Policy for drafts and measurement stores.
  • Backups, previously delivered copies and provider records may follow different cycles. We explain erasure scope, remaining copies and blockers per case; we do not promise instant file removal, destruction of every copy or universal anonymisation.

Rights and request process

KVKK Article 11 provides rights to learn whether data is processed, request information about purposes and recipients, seek correction, erasure/destruction when conditions apply and notification to recipients, object to adverse results from exclusively automated analysis, and seek compensation for unlawful processing. Where GDPR applies, access, correction, erasure, restriction, objection, portability, consent withdrawal and complaints to a competent supervisory authority may also apply.

Email your request to support@getgignode.com. We track it as a case and perform necessary, proportionate identity/authority checks; shared client data may need instructions from the relevant controller. KVKK applications are resolved as soon as possible and within 30 days. Where GDPR applies, we normally respond within one month; if statutory extension conditions apply, we explain the reason and extension within the first month. Technical blockers or verification do not automatically restart these periods.

Account closure requests are not automatic data erasure. Unsupported erasure/restriction actions stay open as cases; we explain scope, blockers, legal assessment and the possible next step. Technical limitations do not remove rights or deadlines; a partial response does not mean the entire request is complete. KVKK complaint routes remain available.

Withdraw optional measurement consent in Cookie settings; withdrawal does not affect prior lawful processing. We do not currently offer a general marketing-email subscription.