SpudV.AI
Version 1.1 · Effective 15 November 2026 · View version 1.0
We may update this text from time to time. The latest version on this page prevails.
Scope: the SpudV.AI website (merchant registration; AI Q&A is provided in the App); the SpudV AI Q&A service provided only in the App; and the “merchant workspace” after the App is launched. The website registration area has only two entries: “Register now” and “Track status / Update profile”. The “Track status / Update profile” page also serves as a backup “My status” page if the App has a problem.
1.1 SpudV.AI is a company centred on artificial intelligence technology. Its brand slogan is:
Connecting People, Businesses and AI Agents.
1.2 SpudV.AI uses artificial intelligence to connect individuals, businesses, and AI agents, and to provide information search, merchant discovery, and related digital services.
1.3 In plain language, this policy explains what personal information the Platform processes, why, how it is used, with whom it is shared, how long it is kept, how it is protected, and what rights you have — in website merchant registration, agreement signing, review and verification, merchant profiles and AI information retrieval in the App, business notices, and the “merchant workspace” after the App is launched.
1.4 In this policy, “the Platform” and “we” mean XIANGWANG SOLE CO.,LTD (a company registered in the Lao People’s Democratic Republic).
1.5 This service is operated by XIANGWANG SOLE CO.,LTD (a company registered in the Lao People’s Democratic Republic). If local law has special requirements, the Platform may issue a local supplementary privacy notice.
1.6 This policy does not apply to third-party websites, or to a merchant’s own website or social accounts (see Article 14).
We collect only the information needed to provide the service.
Email is **required**, and is used as follows:
1. as a contact method for the merchant;
2. to send a sign-in code so the merchant can open “Track status / Update profile” or change information (the code is valid for 10 minutes; failed attempts and sending frequency are limited);
3. to send business notices such as review results to that email.
Email is **not used to send advertising or promotional messages**, unless a separate consent is given. Phone or WhatsApp is kept as a contact method and is **not used to send sign-in codes**. Sign-in does not use SMS codes.
Verification codes and review results are sent to the registration email. If a code still does not arrive, the merchant may email **ai@spudv.com** and attach the identity document or business registration submitted at registration. After we verify this manually, we may change the information or the linked email on the merchant’s behalf. Each such action is recorded for audit. **Sign-in codes are not sent by WhatsApp at this stage.**
Depending on the signing method the merchant chooses in step 2:
- **Tick to sign online:** the signed-in account and account identifier, the agreement version number, the time of consent, the network location (IP) at the time of the action, the agreement text then displayed, and necessary system logs;
- **Download, sign, then photograph or upload a PDF:** the signed file uploaded (photo or PDF), the uploading account, the time of upload, the file version, and the review record;
- the signatory’s signature, seal, and necessary identity-confirmation information.
The Platform does not offer in-person signing.
| Materials collected | |
|---|---|
| Verified individual | Identity card or passport; a half-length photo of the person holding the document; a screenshot of a query of the device’s own number; other related photos (such as work, tools, or the place of service); a business registration certificate may also be submitted if the person has one |
| Verified business | Business registration certificate; identity card or passport of the legal representative (or person in charge); a half-length photo of that person holding the document; shop photos, and the like |
| Also required by category | An industry licence; a power of attorney if someone is acting as an agent |
**We do not carry out face matching, and we do not extract or store biometric features such as a face from a photograph.** If a passer-by’s face may appear in a public image, it is detected only on the device so we can prompt you to change the image or apply automatic masking. The detection result is not used to identify a person and is not stored separately. The Platform collects verification materials only to the extent needed for verification. How they are processed is set out in Article 5.
IP, browser type and device information, operating system and language settings, time of visit and page-view records, referring page, necessary system logs, and information produced by cookies and similar technologies (see Article 11).
Account information (mobile number or email, and a display name); the content of conversations with SpudV AI and images, audio, and files you upload; location information collected only after you authorise it (to recommend nearby merchants); device information, language settings, records of service use, and necessary running logs. If, after tapping “Contact the business”, you choose to like or unlike, we record that action so we can show a “👍” and a number on the information card and profile, and so we can detect and void bulk fake likes. We do not collect written reviews, and we do not provide a “dislike”. Where authorisation is required, we ask for it separately when you use that feature; we will not ask for every permission at once. If a new feature needs additional information, we will explain separately.
When a user or merchant contacts us through ai@spudv.com, a feedback entry, or another channel, the name, contact details, description of the issue, and attachments they provide. Likes or unlikes you make voluntarily after tapping “Contact the business” are described in clause 2.5 and Article 3.
We do not ask you to provide sensitive information such as religious belief, health information, or biometrics. Please do not provide this information in a registration form, in email, or in an AI conversation.
| Information used | Basis | |
|---|---|---|
| To handle registration applications and to create and manage merchant records | Registration information | The merchant’s consent; preparation for signing the agreement |
| To handle signing by any of the methods and to archive the records | Agreement information | Performance of the Merchant Agreement; retention as required by law |
| Individual and business verification, and the annual review | Verification materials and signing records | Performance of the Merchant Agreement |
| To display merchant profiles and information cards in the App, and for AI retrieval (the website does not provide AI Q&A) | Information the merchant has confirmed as public | Performance of the agreement; the merchant’s authorisation |
| To maintain merchant status and to handle updates, withdrawal, and complaints | Merchant records | Performance of the agreement |
| To tell the merchant the number of contacts, likes, verification status, and expiry date (the “Track status / Update profile” page may show the numbers of contacts and likes after the Platform turns the switch on; after the App is launched, this can be viewed in the “merchant workspace”) | Number of contacts, number of likes, review and verification status, and expiry date | Performance of the agreement |
| Sign-in with a verification code (to check progress, add information, and to view status if the App has a problem) | Registration email, and records of sending and checking codes | The merchant’s request; performance of the agreement |
| To send verification codes and business notices to the registration email | Email address and sending records | The merchant’s request; performance of the agreement |
| Manual verification when a code does not arrive (changing information or the linked email on the merchant’s behalf) | The incoming message, the identity document or business registration submitted at registration, handling records, and the audit trail | The merchant’s request; performance of the agreement; preventing impersonation |
| To reply to enquiries | Email content | The user’s request |
| Security monitoring, and preventing false registration, fraud, and impersonation | Access logs and record files | Legitimate interests; a legal duty |
| To provide and improve the AI Q&A service (after the App is launched) | Conversations and uploaded files | The user’s consent; necessity for providing the service |
| To display the number of likes, and to detect and void bulk fake likes | Records of whether “Contact the business” was tapped, and of likes or unlikes | Necessity for providing the service; preventing abuse |
| To comply with legal requirements | Information required by law | A legal duty |
3.1 We will not use personal information for a purpose unrelated to the original purpose of collection. If a new purpose is needed, we will tell you in advance and, where required, obtain consent again.
3.2 **Direct marketing:** We will not use personal information to send promotional messages without a separate consent. You may unsubscribe at any time.
3.3 In the first stage, the Platform does not provide ordering, trading, or custody of funds. Income at this stage is limited to verification fees and promotion fees, collected on the website. If charges begin, this policy will be updated separately for payment-related information. No other charging items will be opened without a further announcement.
4.1 Where applicable law requires consent, we will explain the purpose, the categories of information, and other necessary matters before collection or processing, and we will obtain consent. Checkboxes are never pre-ticked.
4.2 When the merchant submits at step 3 of registration, the merchant confirms that they have read this policy and agree to the processing of their information under this policy.
4.3 When a merchant submits personal information of a contact person, an employee, or another third party, the merchant must ensure that they have that person’s authorisation or another lawful basis.
4.4 When signing the agreement, the signatory must confirm that they have authority to submit materials and to give the necessary authorisations on behalf of the merchant.
4.5 Consent may be withdrawn to the extent permitted by applicable law. Withdrawal does not affect processing already carried out on the basis of consent before withdrawal. If withdrawal means a service can no longer be provided, the Platform may stop that service or the related display.
5.1 The Platform supports two ways of signing: ticking the boxes and signing online; or downloading the agreement, signing or stamping it, then photographing it or uploading a PDF. Records of both methods are kept in the same merchant file. The Platform does not offer in-person signing.
5.2 Signing records are used to evidence the signing process and include the information listed in clause 2.2.
5.3 **Verification materials are kept at the Platform’s highest classification:**
1. Only staff who carry out review work may view them; every viewing and every change is recorded in the audit trail;
2. They are stored encrypted in access-restricted secure storage, with authorisation separate from other materials;
3. **They are not sent to any external AI model service;**
4. No facial comparison is performed; the half-length photo of the person holding the document is viewed only by review staff, by hand;
5. They are not used as public display materials. They are used only to check identity and eligibility to operate, to administer the agreement, to handle disputes, and for uses required by law.
5.4 The Platform may use text-recognition technology such as OCR to help read verification materials. **OCR is only an aid and does not replace human checking.**
5.5 Without undermining the purpose of the check, the Platform masks or de-identifies personal information that is not needed for the check.
5.6 If, in future, the Platform appoints a third-party verification body to carry out checks, the Platform will announce this in advance and will provide only the materials necessary for the check. The third party must keep them confidential under this policy and must take security measures.
5.7 **Handling of public images and identity-document images:**
1. Public images comprise: one avatar or logo (1:1, required); one cover image (4:3, optional; if none is uploaded, one of the industry’s standard covers is used and marked “Image source: AI-generated”; a user-uploaded cover is marked “Image source: uploaded by the user”); and one service photo (4:3, optional). A profile shows at most these three images. Images are compressed in the browser before upload (the long edge is about 2,560). The back end automatically creates a display image (WebP, long edge 1,600, generally within about 300 KB) and a thumbnail (long edge 400), and removes location information from the image.
2. Original images are filed in the media vault at the applicable classification. Public pages, information cards, and AI answers use only display images or thumbnails that carry a light “SpudV.AI” watermark; originals are not provided. An information card in an AI answer is fixed as: one cover (or the industry standard cover if none was uploaded), a small circular avatar overlaid at the lower left, the name, a one-sentence introduction (optional; if left blank it is hidden and no empty space is reserved), one line of “industry · city · opening hours”, and a “Contact the business” button. A small “👍” and a number appear next to the name; they are not shown when no one has liked yet. All other information is on the profile. The profile shows the avatar or logo, the cover, and at most one service photo; there is no carousel. All else being equal, a cover marked “Image source: uploaded by the user” is placed before a cover marked “Image source: AI-generated”.
3. Links to display images are signed and expire after a set time (for example, 24 hours), and hotlink protection is applied. The page does not allow long-press save, “Save as” from the context menu, or dragging of display images. Screenshots cannot be blocked by technical means; the watermark may help identify the source.
4. Identity documents and other verification materials are **stored separately under encryption**. No public image is generated from them. They are visible only to reviewers and are not displayed publicly. The review page superimposes a watermark of “For review use only”, the reviewer’s name, and the time of viewing; every viewing is recorded in the audit trail.
5. When a merchant uploads public images, the merchant must tick “I confirm that I have the right to use these images and that people appearing in them have agreed.” We retain the tick status, the time, and the account.
6. Information cards and profiles first show a small blurred preview image, then replace it with a clear display image.
7. If a public photo has not been updated for more than one year, we remind the merchant to update it at the annual review.
8. After a merchant withdraws or withdraws public authorisation, display images and thumbnails are deleted within 30 days. Deleted files in secure backups are overwritten in the ordinary course over the eight-week retention period (see clause 10.1). During that period they are not used for any business purpose and will not be restored to the live system.
6.1 The merchant authorises the Platform to use merchant information that the merchant has clearly submitted and agreed to make public, for the merchant profile in the App, for a web profile that may be shared after the App is launched, and for merchant information cards in AI answers in the App. The website does not provide AI Q&A.
6.2 Public information may include the name, category, a short description, a public place of business or service area, opening hours, public contact details, services or skills, photographs (verified merchants only), and other information the merchant has confirmed may be made public. Fee rates are not displayed in the first stage.
6.3 The Platform may classify, organise, translate, convert the format of, index, and otherwise technically process this information as needed so that the AI can retrieve and display it in response to a user’s question.
6.4 **Information about the merchant’s contact person:** the contact name and phone number on the registration form are, by default, used only so that we can contact the merchant, and are **not shown on the merchant information card**. Contact details shown on the card are filled in and confirmed by the merchant separately.
6.5 A contact person’s personal details, signed documents, verification materials, and other non-public information do not become public merely because the merchant has authorised display of the profile.
6.6 **A private conversation between a user and the AI is not opened to a merchant merely because a merchant is mentioned in it.** The merchant cannot see the conversation or the user’s personal information. Review results are sent to the registration email. For the monthly number of contacts, only the number is given, not a list of names. After the merchant opens “Track status / Update profile” and signs in with a verification code, the merchant may view review and verification status and the expiry date; that page also serves as a backup “My status” page if the App has a problem. The number of contacts and the number of likes are hidden by default; the Platform turns the switch on, and turning it on or off is recorded in the audit trail. After the App is launched, the merchant may view the information above in the “merchant workspace” and may purchase promotion. All records are as kept by the Platform; the App only displays them. The website has no merchant back office. Sign-in does not use a mobile SMS code.
6.7 **Display on official channels (separate consent).** A merchant may separately tick consent to have reviewed public information displayed on SpudV official channels (the website, official social accounts, and the like). This item is **not ticked by default**, and the merchant **may withdraw at any time**. Display is limited to information the merchant has confirmed may be made public, and **private contact telephone numbers are not displayed**. Paid promotion must be labelled “Promotion”. After withdrawal or exit, display stops immediately under Article 10.
6.8 **Display after exit, automatic renewal, or lapsed verification** (consistent with Article 6 and clause 18.1 of the Merchant Agreement):
Situation| Whether shown to the public | |
|---|---|
| Not verified (including cases where the agreement has auto-renewed but verification has expired and has not been renewed) | Basic information continues to be shown, labelled “Entered by the merchant, not verified”; no verification mark is shown |
| Verified | Shown, with the verification mark |
| Has exited (the merchant must give active written notice of exit, by email to ai@spudv.com, or by returning to the website registration page, opening “Track status / Update profile”, signing in with a verification code, and submitting an exit request; or the Platform terminates under the agreement) or has withdrawn public authorisation | No longer shown on any page, merchant information card, AI answer, official channel, or partner platform, and is not reduced to “not verified” and continued |
The agreement has a term of one year. If no written notice of exit is given on expiry, it auto-renews for one year, and may be renewed successively; after renewal, display continues. If verification expires and is not renewed, the verification mark is not shown and the listing continues as “not verified”. Display stops only if the merchant gives active written notice of exit (by email to ai@spudv.com, or by returning to the website registration page, opening “Track status / Update profile”, signing in with a verification code, and submitting an exit request), or if the Platform terminates the cooperation under the agreement.
6.9 **Providing public information to partner platforms (building a shared AI ecosystem).** After the merchant ticks consent, we may provide information the merchant has confirmed may be made public to partner AI platforms, for display and answers in a shared AI ecosystem. The scope is limited to: name, industry, services, opening hours, images authorised for public use, and contact details the merchant has agreed to make public. **Identity documents, the mobile number used for registration, and review materials are never disclosed, and are not provided to partner platforms.** Partner platforms must not resell the information. The merchant may at any time return to the website registration page, open “Track status / Update profile”, sign in with a verification code, and turn this authorisation off. After it is turned off or the merchant exits, we stop providing the information at once and require partner platforms to stop display at the same time. This item is optional. It is ticked by default at registration, and the application may still be submitted if it is unticked. Specific interface arrangements with a partner platform will be set out in a separately drafted Interface Cooperation Agreement when a live connection is made. Display after exit or withdrawal of public authorisation is also governed by clause 6.8.
7.1 Verification codes and review results are sent to the registration email. An email address is required.
7.2 Information processed for this purpose includes: the registration email, and records of sending verification codes and notices.
7.3 Notices sent to the registration email are limited to content related to the merchant’s business, such as sign-in codes, review results, reminders of verification expiry and renewal, and notices of changes to the agreement or the rules. Advertising or promotional messages are not sent.
7.4 If a verification code does not arrive, please email ai@spudv.com and attach the identity document or business registration certificate submitted at registration, so that we can check this by hand.
8.1 **We do not sell personal information.**
8.2 To provide the services, we may entrust trusted service providers to process necessary information, including cloud computing and server hosting, network security and system maintenance, file storage, text recognition, AI model services (excluding verification materials), email, customer support, and other necessary technical services. A provider may process information only to the extent necessary for the agreed service, must sign a contract, and must process the information under our instructions and keep it confidential.
8.3 Information a merchant chooses to make public is shown to the public and to users of SpudV AI; that is the purpose of merchant registration. The scope, the way to exit, and prohibited uses of providing public information to partner platforms are set out in clause 6.9.
8.4 Where laws or regulations or a competent authority lawfully require it, we will provide the necessary information as the law requires.
8.5 If a business change such as a merger, reorganisation, or transfer of assets involves a transfer of personal information, the necessary procedures under applicable law will be followed, and the receiving party must continue to comply with this policy.
8.6 After a user contacts a merchant through “Contact the business” or “Visit the store”, communication between the two parties does not go through the Platform and is subject to the merchant’s own privacy rules.
9.1 **The location of servers and backups is as actually published by the Platform at the relevant time.** Cloud computing facilities, AI services, and other technical providers used may also be located outside your place of residence. If applicable law requires personal information to be transferred outside your place of residence, this article will apply.
9.2 Where applicable law requires consent for a cross-border transfer, we will ask you to tick a separate consent at registration. For example, relevant law of Laos requires the consent of the person concerned before personal information is transferred abroad, and requires that the recipient can protect the information.
9.3 Transfers are made with measures such as encrypted transmission and contractual constraints on the recipient, requiring the recipient to provide protection no less than that in this policy.
9.4 If you do not agree to a cross-border transfer, you may be unable to complete registration. If you have questions, please email ai@spudv.com.
We keep personal information only for as long as needed to achieve the purpose, or for as long as the law requires, and then delete it or anonymise it.
Information| How long it is kept | |
|---|---|
| Records of registration where the agreement was not signed | 90 days from registration; after the file is closed, kept read-only for 180 days and then deleted |
| Signing records, agreement versions, and signed documents | During the cooperation and for 5 years after it ends |
| Verification materials (identity documents, a photo of the person holding the document, a screenshot of the device’s own number, a business registration certificate, and the like) | Kept during the verification validity period; deleted within 180 days after the period ends or the merchant exits |
| Public merchant information | Continues to be displayed during the cooperation and during automatic renewal of the agreement. If verification expires and is not renewed, the verification mark is not shown and the listing continues as “not verified”. Only after the merchant gives active written notice of exit or withdraws public authorisation, or the Platform terminates under the agreement, is the information no longer shown on any page, merchant information card, or AI answer, and it is not reduced to “not verified” and continued; **display images and thumbnails are deleted within 30 days** (consistent with clauses 10.6 and 18.1 of the Merchant Agreement); deleted files in secure backups are overwritten in the ordinary course over the eight-week retention period (see clause 10.1). Other public materials are then handled according to the corresponding periods in this table |
| Merchant contact information | Kept with the merchant file, for the period that applies to the registration or signing record; external use stops immediately after exit; the contact telephone number on the registration form is not public by default |
| Email correspondence | After the matter is handled, kept for the period required by applicable law and published on this page |
| Access logs and security records | Kept for the period required by applicable law and published on this page |
| App conversation records (after launch) | As provided in the rules at the time the App is launched; users may delete them themselves |
| Like records | Used to display the count while a like is in effect; removed from the count immediately if the user cancels. Voided fake likes are kept as necessary records to prevent further abuse and are not shown publicly |
| Records of sending and checking sign-in codes | Codes are valid for 10 minutes and are void after they expire; security records such as the number of sends and failed attempts are kept for the same period as access logs and security records |
| Requests for manual verification when a code does not arrive | After the matter is handled, the incoming message is kept for the email-correspondence period; attached identity documents or business registration certificates are handled for the verification-materials period; the operation audit is kept with access logs and security records |
For a complaint, dispute, investigation, or legal requirement that is not yet resolved, related information may be marked as frozen (legal hold). It is not cleared while frozen; after the hold is lifted, it is handled under the original period.
10.1 Information that has already been deleted is overwritten automatically in secure backups according to the backup cycle, for up to about eight weeks (daily snapshots are kept for 14 days; weekly off-site backups are kept for eight weeks). Deleted information in backups is not used for any business purpose during this period and will not be restored to the live system.
11.1 We take reasonable technical and organisational measures according to the nature, use, and risk of the information, including: role and account permission management (least privilege); encryption in transit and encryption of important information at rest; separate permission control for signed documents and verification materials; masking or de-identification of sensitive information; operation logs and access audit records; staff confidentiality and security management; selection of, and contractual constraints on, service providers; and regular review and improvement.
11.2 If an incident occurs that may affect the security of personal information, we will deal with it at once and, as applicable law requires, notify the people affected and the competent authority.
11.3 Transmission over the internet and electronic storage cannot be guaranteed to be absolutely secure. If you find a security problem, please contact ai@spudv.com.
12.1 The website currently uses only **necessary cookies**, so that the site can function, for example to remember a language choice and to prevent abuse of forms.
12.2 Before we use analytics or other non-necessary cookies in future, we will first inform you and offer a choice to accept or refuse.
12.3 You can restrict or delete cookies in your browser settings, but some functions may not work properly.
To the extent applicable law allows, a user or a merchant may:
1. **Access** personal information about you that the Platform holds, or obtain a copy and an explanation of the processing;
2. **Correct** information that is inaccurate or incomplete;
3. **Delete** information that is no longer needed;
4. **Withdraw consent**;
5. **Stop a transfer**, or restrict or object to certain processing where the law so provides;
6. **Refuse direct marketing**;
7. A merchant may change profile information, withdraw authorisation for public display, or leave the Platform;
8. **Complain**: complain to us, or complain to a competent authority where you are;
How to apply: email ai@spudv.com. To prevent impersonation, we will first verify your identity, and we will reply within 30 working days after verification. A request by the person concerned to delete information will be completed within 30 working days after identity is verified, except where a dispute or investigation is in progress or the law requires us to keep the information, in which case we will explain why. In principle no fee is charged, unless applicable law provides otherwise.
14.1 Merchant registration must be completed by an adult operator or an authorised representative.
14.2 The Platform’s services are not directed at children. Anyone who has not reached the age of majority under applicable law should use services that require the submission of personal information only with a guardian’s consent and guidance.
14.3 If we find that a minor’s personal information has been collected without a guardian’s consent, we will delete or restrict the processing as soon as applicable law requires.
The Platform may display a merchant’s website, a Facebook page, WhatsApp, or another third-party service entry. When you visit a third-party website or use a third-party service, that third party’s own privacy policy and rules apply. The Platform is not responsible for a third party’s independent processing of information beyond what applicable law requires.
16.1 The Platform uses AI technology to retrieve merchant information and generate answers to questions users ask. This may use merchant information maintained by the Platform, materials the merchant has authorised for public use, and information the user provides of their own accord.
16.2 Before information is submitted to an AI service for processing, we take minimisation, masking, or de-identification measures as technical conditions allow. **Verification materials are not sent to an external AI model service.**
16.3 **The AI does not automatically make a decision that has a significant effect on you.** Whether a merchant passes verification is decided by the Platform’s review staff, by hand.
16.4 Below every AI answer, the following is always shown: “AI-generated content is for reference only and may be inaccurate. Merchant information is provided by the merchant; please rely on what the business actually offers.” For how the service is used and for the risks, please also read the SpudV.AI AI Use Notice.
17.1 The Platform may update this policy in light of business development, technical change, or legal requirements. Each version has a version number and an effective date, and earlier versions remain available for reference.
17.2 A material change (for example a new purpose, a new party with whom information is shared, or the opening of features such as transactions) will be announced in advance in a prominent place on the website or in the App. Where consent must be obtained again, please confirm again.
This policy will be provided in Chinese, English, and Lao. If the versions differ in meaning, the Lao version prevails.
For requests to access, correct, or delete personal information, to withdraw consent, or for other privacy-related requests, please contact **ai@spudv.com**. Do not send passwords, bank card numbers, or other unnecessary sensitive information in ordinary email.
This document is issued by XIANGWANG SOLE CO.,LTD, which operates the related services. Email: ai@spudv.com.
This document is governed by the law of the Lao People’s Democratic Republic.
Disputes arising from this document shall first be resolved through friendly consultation. If consultation does not resolve the dispute, it shall be submitted to a court with jurisdiction at the company’s location.
This document will be provided in Chinese, English, and Lao. If the versions differ in meaning, the Lao version prevails.