GitMind

GDPR overview

GitMind makes an explicit GDPR claim: the privacy policy opens by stating that the operations of GitMind are in accordance with the European Union's General Data Protection Regulation, effective May 25, 2018. Section 4 describes technical and organizational measures aligned with the regulation, together with security questionnaires imposed on third parties, and section 5 sets out access, portability, rectification, erasure, account deletion, unsubscribe, consent withdrawal and post-mortem instructions, with requests handled at support@gitmind.com. Footer badges display ISO 27701, GDPR and ISO 27001, but no certificate number or certifying body is published. Three gaps remain: no EU representative is designated under Article 27, no data processing agreement is offered, and no formal subprocessor list exists. The policy carries an effective date of 30 November 2021 and has not been revised since.

Who owns the data?

GitMind states that content belongs to the user. Files created or uploaded are stored and maintained by the publisher, including earlier versions and sharing lists, but each uploaded file can be used by its owner only and no other user can access it. The home page commits to no model training and no advertising use, and to deletion at any time. The privacy policy describes rights of access, export, rectification, per-file erasure and full account deletion. The software itself remains the publisher's property under the end-user license agreement, which separates ownership of the program from ownership of the content, and the AIGC agreement requires users to hold the rights to whatever they upload or enter.

Reuse rights

Users keep free use of their own output: files remain accessible to their owner, can be exported to PDF, JPG, SVG, TXT, Word or Visio and can be shared or deleted without asking the publisher. On the publisher's side, the privacy policy describes the collection of account data (name, email, postal address, telephone), usage data, device data (IP address, system language, browser, identifiers) and uploaded files. That information may be shared with service providers for payment, analytics, anti-fraud, emailing and marketing, and may be transferred outside the European Union to countries whose level of protection is not equivalent. Third-party tracking tools are cited only as examples, among them Google Analytics, Hotjar, Criteo, Facebook, LinkedIn, Firebase and Quora, alongside functional and analytics cookies, page tags and pixels, respect for the Do Not Track signal and AppsFlyer for mobile analytics. The home page states that data is not used for model training or advertising.

Data retention & training

Hosting summary

GitMind does not say where its data is hosted. The privacy policy states only that the publisher may store collected information on servers leased from third-party server service providers, without identifying a provider, a country or a region. Section 2.4 adds that data may be transferred outside the European Union, including to countries whose level of protection is not equivalent, without listing destinations or safeguards. The home page mentions encrypted connections and strictly limited access to data, but gives no infrastructure detail. The site itself is served behind Cloudflare — the resolved address 172.67.198.165 belongs to an anycast node — which reflects content delivery rather than a storage location. The publisher, Wangxu Technology Co., Ltd., is based in Shenzhen and lists offices only in mainland China and Hong Kong. In practice, a buyer with data residency requirements has nothing to work from: no hosting jurisdiction is disclosed, no data processing agreement is published and no formal subprocessor list exists.