> For the complete documentation index, see [llms.txt](https://autodoc-1.gitbook.io/pp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://autodoc-1.gitbook.io/pp/autodoc-privacy-policy.md). # AUTODOC PRIVACY POLICY Last Updated: May 31, 2026 ## 1. Introduction Welcome to AutoDoc. AutoDoc is a vehicle maintenance, diagnostic, data verification, AI assistance and blockchain-enabled service operated by Digifortune Ltd. ("AutoDoc", "we", "us" or "our"). This Privacy Policy explains: * what information we collect; * how we use, store and protect your information; * how information may be shared; * your privacy rights; * how blockchain-related records are handled; * how AI services process your information; * how international transfers of information occur. By using AutoDoc, you acknowledge that your personal information may be processed as described in this Privacy Policy. *** ## 2. Data Controller The data controller for AutoDoc services is: **Digifortune Ltd.**\ Cayman Islands Website:\ [autodoc.network](https://autodoc.network) *** ## 3. Categories of Information We Collect ### 3.1 Account Information We may collect: * name * nickname * account ID * password hash * email address * mobile phone number * social login identifier * language preference * country * account settings * user role Purpose: * account registration * authentication * security * customer support * service administration *** ### 3.2 Age Verification Information We may collect: * date of birth * age verification information Purpose: * compliance with applicable laws * child protection requirements * eligibility verification Users under the minimum legal age may be required to obtain parental or guardian consent before using certain services. *** ### 3.3 Vehicle Identity Information We may collect: * VIN (Vehicle Identification Number) * vehicle registration information * vehicle plate number * make * model * year * trim * fuel type * mileage * vehicle ownership information * vehicle profile information Purpose: * vehicle profile creation * maintenance tracking * AI diagnostics * repair verification * vehicle history services Vehicle identity information is processed only with user authorization. *** ### 3.4 Vehicle Diagnostic and Repair Information We may collect: * OBD data * diagnostic trouble codes * inspection reports * maintenance records * repair records * service histories * replacement part records * invoices * quotations * service reports Purpose: * AI-assisted diagnostics * maintenance recommendations * repair validation * service history management *** ### 3.5 Location Information #### Precise Location Information We may collect: * GPS coordinates * real-time location information Purpose: * nearby repair shop recommendations * navigation functions * appointment verification * fraud prevention Precise location information is collected only after obtaining your explicit consent. #### Approximate Location Information We may collect approximate location information derived from: * IP address * network information Purpose: * security * service localization * fraud prevention *** ### 3.6 Device Sensor Information Where enabled, we may collect: * gyroscope data * accelerometer data Purpose: * driving behavior analysis * vehicle condition analysis * personalized recommendations Sensor collection is optional and requires explicit consent. *** ### 3.7 Uploaded Content Users may upload: * vehicle photos * damage photos * repair photos * accident photos * documents * reports * feedback * annotations Uploaded content may contain personal information. Users are responsible for ensuring they have authority to upload such content. To protect privacy, AutoDoc may remove metadata such as EXIF location information before processing uploaded images. *** ### 3.8 AI Interaction Information When using AI services, we may collect: * prompts * questions * messages * uploaded files * AI outputs * feedback * ratings * troubleshooting logs Purpose: * providing AI services * quality assurance * safety monitoring * service improvement AI interaction data used for model training is subject to separate consent where required. *** ### 3.9 Blockchain and Wallet Information We may collect: * wallet addresses * public keys * transaction hashes * chain IDs * credential IDs * signature records * blockchain interaction records Purpose: * blockchain services * credential verification * rewards * data authenticity verification *** ### 3.10 Payment and Reward Information We may collect: * transaction records * subscription information * payment status * refund records * reward balances * incentive records Purpose: * payment processing * accounting * reward distribution * legal compliance *** ### 3.11 Device and Technical Information We may collect: * IP address * device identifiers * browser information * operating system * app version * crash logs * security logs * cookies * analytics identifiers Purpose: * security * fraud prevention * product improvement * system maintenance *** ### 3.12 Customer Support Information We may collect: * customer inquiries * complaints * support communications * dispute records Purpose: * resolving requests * legal compliance * customer service *** ## 4. Information Received From Third Parties We may receive information from: * repair shops * diagnostic device providers * payment processors * identity verification providers * analytics providers * business partners * blockchain infrastructure providers We require such parties to have an appropriate legal basis before sharing information with us. *** ## 5. How We Use Information We use information to: * provide services * authenticate users * manage accounts * verify vehicle information * provide AI diagnostics * facilitate repair services * process transactions * provide customer support * improve products * ensure platform security * comply with legal obligations * prevent fraud *** ## 6. Legal Basis for Processing Depending on the circumstances, AutoDoc may process information based on: * performance of a contract * legal obligations * user consent * legitimate interests where permitted by law Certain activities require separate consent, including: * vehicle identity processing * precise location collection * sensor data collection * AI model training * enterprise data licensing * marketing communications * international transfers where required * blockchain-related activities *** ## 7. AI Services and Automated Processing AutoDoc provides AI-powered services. AI outputs: * are informational only; * may contain inaccuracies; * should not be treated as professional mechanical, legal, financial or safety advice. Final decisions remain the responsibility of users, repair professionals and vehicle owners. Where applicable, users may request human review of significant automated decisions. *** ## 8. AI Model Training AutoDoc may use de-identified or pseudonymized information to improve AI systems. Where required by law: * AI training participation is voluntary; * users may opt out; * refusal will not affect access to core services. AutoDoc implements safeguards designed to prevent re-identification. *** ## 9. Enterprise Data Licensing AutoDoc may provide: * aggregated datasets * anonymized analytics * pseudonymized vehicle insights to authorized business customers. We do not sell directly identifiable personal information. Enterprise data licensing activities are subject to separate user authorization where required. *** ## 10. Blockchain Services AutoDoc utilizes blockchain technologies. Users acknowledge that blockchain records may: * be publicly visible; * be immutable; * remain permanently accessible; * be technically impossible to delete. AutoDoc does not intentionally store directly identifiable personal information on public blockchains. Only the following categories may be recorded on-chain: * hashes * credential identifiers * wallet addresses * transaction identifiers AutoDoc prohibits storing: * names * email addresses * phone numbers * VIN numbers in plain text * vehicle plate numbers * government identifiers on public blockchains. *** ## 11. International Transfers Your information may be transferred to and processed in jurisdictions outside your country of residence, including: * Cayman Islands * Republic of Korea * Singapore * United States * Japan * EEA jurisdictions AutoDoc implements contractual, technical and organizational safeguards to protect transferred information. For Korean users, international transfers are conducted in accordance with applicable provisions of PIPA. *** ## 12. Data Retention AutoDoc retains information only as long as necessary. Typical retention periods include: | Data Category | Retention Period | | ------------------- | -------------------------------- | | Account Information | Until account deletion + 30 days | | AI Conversations | Up to 24 months | | Security Logs | Minimum 3 months | | Customer Complaints | 3 years | | Transaction Records | 5 years | | Tax Records | As required by law | | Blockchain Records | May be permanent | After expiration of retention periods, information will be securely deleted or anonymized. *** ## 13. Data Sharing We may share information with: * service providers * payment processors * cloud providers * AI providers * repair shop partners * regulatory authorities * legal advisors We do not sell personal information. *** ## 14. User Rights Subject to applicable law, users may request: * access * correction * deletion * restriction * portability * withdrawal of consent Users may also object to certain forms of automated processing where permitted by law. Requests may be submitted through: *** ## 15. Children's Privacy AutoDoc is not intended for children below the minimum legal age. Where required by law, parental or guardian consent will be obtained before processing children's information. *** ## 16. Security Measures AutoDoc implements: * encryption * access controls * logging * monitoring * authentication mechanisms * security reviews to protect information from unauthorized access, disclosure, alteration or destruction. *** ## 17. Repair Shop Data Processing Repair shops using AutoDoc are responsible for ensuring that they possess a lawful basis to upload vehicle repair information. Where repair records contain vehicle owner information, repair shops must obtain necessary permissions or provide another valid legal basis before submission. AutoDoc may require documentation demonstrating such authorization. *** ## 18. Marketing Communications Users may choose to receive: * promotions * newsletters * product updates * partner offers Marketing communications are optional. Users may withdraw consent at any time through account settings or unsubscribe links. *** ## 19. Changes to this Privacy Policy We may update this Privacy Policy from time to time. Material changes will be communicated through: * website notices * application notices * email notifications where required by law. *** ## 20. Contact Us Official X: Website: [autodoc.network](https://autodoc.network)
*** ## AFFILIATE. CONSENT NOTICE SUMMARY FOR KOREAN USERS The following summary is intended to help present separate consent choices in the AutoDoc user interface and is included as part of this publication version. * Required Terms consent: I agree to the AutoDoc Terms of Use. * Required Privacy Policy acknowledgement: I have read the AutoDoc Privacy Policy. * Required necessary processing consent: I agree that Digifortune may process necessary account, vehicle, security, and service information to provide AutoDoc. * Vehicle data submission consent: I confirm that I have the right or authorization to submit the vehicle data and agree that it may be processed for AutoDoc services. * Repair partner disclosure consent: I agree that AutoDoc may provide the information needed for my request to the repair shop or service partner I choose. * Optional location consent: I agree that AutoDoc may use my location to provide nearby repair, booking, service-area, and fraud-prevention features. * Optional AI training and data improvement consent: I agree that Digifortune may use de-identified, pseudonymized, or aggregated data to train, test, validate, and improve AI systems and automotive data products. * Optional enterprise automotive data products consent: I agree that Digifortune may use de-identified, pseudonymized, aggregated, or separately authorized automotive data for enterprise data services such as insurance analytics, used car valuation, OEM feedback, parts forecasting, and AI training. * On-chain credential consent: I understand that wallet addresses, transaction hashes, data hashes, and credential records may be recorded on blockchain networks and may be difficult or impossible to delete. * Rewards and token consent: I understand that rewards are not investment returns and may have no guaranteed cash value, liquidity, price, listing, or future utility. * Optional marketing consent: I agree to receive promotional messages, events, partner offers, and service recommendations from AutoDoc. * Cross-border transfer consent: I agree that necessary information may be transferred overseas to Digifortune and authorized service providers as described in the Privacy Policy. Operator: Digifortune, registered in the Cayman Islands.Service name: AutoDoc.Website: [www.autodoc.network](http://www.autodoc.network). Effective date: May 31, 2026.User contact channel: official AutoDoc website, application, DApp, account interface, or support channel made available within the Services. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://autodoc-1.gitbook.io/pp/autodoc-privacy-policy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.