Privacy Policy

This policy explains how WebsDocs handles personal information across its website, Directory, Owner and Agency workspaces, hosted business pages, RTD Business Agent and BizDesk, ASG AI Sales Gateway, Studio, dashboards, support and billing. The information involved depends on the feature you use.

WebsDocs is operated by Javed Sarwar, a sole proprietor trading as WebsDocs. Contact hello@websdocs.com for questions about this notice.

WebsDocs handles information for its own account administration, public directory, security, billing and support purposes. When a business uses our tools to handle its customers’ conversations or workflows, that business determines the purpose of those interactions; our role also depends on the applicable service agreement. Its privacy notice applies alongside this one.

Public business profiles and private account records serve different purposes. Publishing a profile makes the selected business information accessible to visitors, search engines and AI services. Signing in, verifying ownership or contacting support does not by itself make your private account records public.

Last updated: November 5, 2026. For privacy questions, email hello@websdocs.com.

What “personal information” means. Personal information means information about an identified or identifiable individual. A company registration number may concern a legal entity rather than an individual, but a named contact, personal business email, sole-trader record or residential business address may identify a person. This distinction matters when we review a public business record.

The business operating an agent. If you speak to an agent on another business’s website, that business may decide what questions to ask, which team receives the enquiry and how to use the result. Check that business’s notice as well as this policy. WebsDocs’ responsibility for its own security and account records remains separate from that business’s customer relationship.

Use the Owner Workspace to manage a claimed business. Use Request a correction for inaccurate listing information or Request removal to ask for a listing review.

You do not need to buy a plan or activate a paid account to contact us about your personal information. Email hello@websdocs.com with the relevant page URL and a short explanation. We may need proportionate evidence of identity or authority before changing a record or disclosing private information.

Commercial conditions are in our Terms and Conditions; payment and refund information is on the Payment Information page. These documents do not remove rights that apply under data protection law.

Directory and hosted pages: business discovery, country and city browsing, website scans, submissions, claims, domain verification, corrections, removal requests, owner controls, public business pages and registry evidence.

RTD and BizDesk: business chat, voice interactions, Human Inbox, configured workflows, approved business knowledge, Studio setup and account dashboards.

ASG and Gateway: business identity and capability information, AI discovery, agent-facing routes, Studio, workspace access and related usage records. The public Agentic Network is available at aig.com.my.

WebsDocs services: website browsing, enquiries, support, billing, service delivery and communications. Independently operated websites and AI services have their own privacy practices.

Directory information can come from business websites and their public pages, owner submissions and edits, public company registries, and registry or data providers used by a particular verification feature. Information can include business names, descriptions, categories, website and page links, logos, social links, business addresses, telephone numbers, email addresses and registry references.

Business contact information can still be personal information, especially for sole traders or contacts whose names, email addresses or home addresses identify them. Its public availability does not remove applicable privacy rights.

Published fields may appear in profiles, search results, country pages, public APIs, structured data and other machine-readable business records. Third parties may index or copy them. We can review information we control, but a change here may not immediately remove an independent search-engine cache or third-party copy.

Automated extraction and registry matching can be incomplete or incorrect. A claimed listing, a domain check, a registry match and a Directory score are different signals. None alone guarantees a business’s conduct. Contact us to challenge a source, match or published field.

Source context and freshness. A website, registry and owner may describe a business differently. A source can change after collection, and a business may change its name, address, domain or operating status. Where a profile displays a source or update time, use that context when evaluating the information. Ask us about the source of a disputed field if the page does not make it clear.

Duplicate and outdated profiles. Similar names, several domains or changed business details can lead to duplicate or mismatched records. When reporting a duplicate, provide the URLs of both profiles and identify the correct business website. A duplicate correction should not require creating another public listing. We review which information relates to the business before changing or combining records.

Public accessibility is a separate decision. Do not assume that information suitable for an internal account is suitable for a public profile. Review personal telephone numbers, home addresses and named contacts carefully. A request to remove an unnecessary personal field can be considered separately from a request to remove the entire business record.

When you submit or claim a business, we receive the contact and business details you enter, your website URL, edits and the information needed to check your authority. Account operations can also generate authentication, session, verification and request-history records.

Your public business contact details are distinct from the email used to access your account or communicate with support. Authentication secrets, verification tokens and private support attachments are not intended for public profiles. Only include information suitable for publication in public listing fields.

Domain verification helps establish control of a website; registry checks concern the available business record. We may ask for further evidence when ownership is disputed. Required access or verification information is needed to complete those functions; without it we may be unable to grant control.

Hosted business pages and Profile Studio use the content you supply to build and publish your business presence. Review the selected public details before publishing and keep them accurate.

Ownership disputes and team access. Having an account does not automatically establish authority over every business you reference. Claim and verification information is used to decide who may manage a listing. If authority changes or a team member leaves, review access and report any account you no longer control. Disputes may require supporting records and a human review.

Account closure and public records. Closing an Owner Workspace account is different from deleting a public listing that also draws from a business website or registry. Tell us whether you want account access closed, a public field corrected, a listing reviewed for removal, or all of these. Applicable privacy rights are assessed for the relevant information and purpose.

Agency account records include the agency name, sign-in email, account identifiers and security records. Optional profile information includes a description, website, contact details, location, links, logo and banner. We use these records to provide the workspace, identify the submitting agency, manage support and protect access. The Agency profile and its uploaded media are available to the agency and authorised WebsDocs administrators; saving them does not create a public business listing.

Public listings and access requests. Agencies may submit public business information without prior owner permission. Selected business fields can become public after review or automatic publication when the agency chooses “Skip admin review” and validation succeeds. We retain the submitting agency, request reference, publication choice and status for operation, attribution and review. This does not verify ownership or grant editing access. For a separate client ownership or management request, the agency supplies an appropriate client contact. That person receives the agency’s name, email, relevant business details and a private review link so they can respond. The agency can see request status, but does not receive the client’s private account-activation credentials.

Website suggestions. A requested lookup retrieves public website information and may suggest business details and an externally hosted logo URL. Suggestions must be reviewed. An external logo preview can contact the image’s host from your browser; it is not the same as uploading an image to the Agency profile. A detected public email is not automatically chosen as an ownership-confirmation recipient.

Images. Agency profile uploads support PNG, JPEG and WebP, up to 2 MB per image and 15 MB total per agency. The Agency media bucket is configured with European Union storage jurisdiction. This describes that storage setting, not every location involved in service delivery or processing. Uploaded media is served through authenticated workspace access. Use the profile’s media controls to remove images you no longer need.

Private messages. WebsDocs announcements appear in Agency workspaces. Private messages and agency replies are available to the agency and authorised WebsDocs administrators, not to other agencies or client businesses. Message content, sender, timestamps and read status support delivery and follow-up. In-app messages are separate from emails required for account verification or client requests.

Agency records follow the retention criteria in How retention is determined, including account operation, outstanding requests, security and dispute handling. Public listings and private Agency records have separate purposes: closing an Agency account does not itself remove a business’s public listing. For access, correction or deletion requests, see Your rights or email hello@websdocs.com.

Requests to our websites and services can generate IP addresses, browser and device information, timestamps, requested routes, referrers, response status, security signals and identifiers associated with a session or account. Features may also record profile views, link actions, API use and business-enquiry activity.

These records support delivery, troubleshooting, abuse prevention, usage limits and reporting. Bot or AI-provider classifications are estimates based on available signals and should not be treated as proof of an individual visitor’s identity.

Public activity cards and analytics present aggregate counts, including scheduled snapshots and reporting windows. These summaries are different from the underlying technical logs. Hashing an identifier does not automatically make it anonymous.

We use information to deliver requested features, maintain public business records, administer accounts and ownership checks, route enquiries, provide support, process billing, measure service use and protect systems from misuse.

Where applicable law requires a lawful basis, providing a requested account or paid service may be necessary to perform a contract or take steps you request before one. Billing and other records may also be needed to meet legal obligations.

Public business discovery, record accuracy, proportionate service measurement and fraud prevention may involve legitimate interests, subject to the applicable balancing of those interests against individual rights. Public availability is not itself a lawful basis. Where consent is required, such as for certain optional tracking or marketing, it must be obtained for that purpose.

Right to object: where applicable, you may object to processing based on legitimate interests, including publication of personal information in a business record. You may object to direct marketing at any time. Contact hello@websdocs.com; consent can also be withdrawn without affecting processing that was lawful before withdrawal.

Information needed for a function. You can read public pages without submitting a business profile. A claim requires enough information to check authority; an enquiry requires a way to send or route the message; a paid service requires the information needed for checkout and administration. Optional content should not be supplied simply because a form allows it.

New purposes. A new feature may need different information or a different use of existing information. Where the proposed use requires a further notice, consent or another lawful basis, publishing a general policy does not replace that requirement. Product-specific notices should be read at the point where the feature is enabled.

Contact forms, business enquiries and support tickets can contain your name, email, message, business URL, account or listing reference, attachments and technical context. An enquiry directed to a listed business may be shared with that business or its authorised workspace users so they can respond.

Support information is used to investigate the request, confirm authority, communicate a resolution and maintain relevant service records. Send only the information needed for the issue. Do not include passwords, access tokens, full payment-card details or unrelated sensitive documents.

The receiving business is responsible for its subsequent handling of an enquiry. For a conversation with one of its agents, you can contact that business directly; we can help identify the appropriate service route.

Attachments and screenshots. Screenshots can contain account names, email addresses, session tokens or third-party conversations beyond the issue being reported. Crop or redact unnecessary content before uploading. If you accidentally submit a secret, replace or revoke the secret through its issuing service as well as asking us to review the attachment.

Enquiry visibility. A message intended for a business should be written with that recipient in mind. An owner or authorised team member may use it to answer, follow up or manage an agreed workflow. Do not include another person’s sensitive information unless you are entitled to do so and it is necessary for the request.

When you request a website scan or use website-assisted submission, the service retrieves publicly accessible website content to identify relevant business information. This may include a name, description, logo, contact details, location and page links. It can create a report or prefill available form fields.

Extracted information may be missing, stale or attributed incorrectly. Review and correct it before submission. A fetched logo is optional; submitting a business does not require you to provide a logo URL. A scan is not proof of ownership or registry verification.

Business knowledge, FAQs, documents and setup instructions supplied to Studio or an agent can be processed to configure the requested service. Only submit material you have authority to use, and separate public information from confidential instructions. Do not place private information into a field intended for public publication.

Scan reports and delivery. If a scan feature offers email delivery or creates a support or administrative record, the submitted URL, extracted information and contact details needed for that delivery may form part of the report or associated record. Requesting a scan does not guarantee that every footer, contact page, location or logo can be extracted.

Correcting extracted information. Review the business name, website, location and contact details before submitting a prefilled form. An automatically detected country or city may describe an office, service area or unrelated page content. Use the owner controls or correction route if an incorrect value has already been published.

RTD, BizDesk and enabled AI features may process prompts, business knowledge, messages, responses, conversation context, workflow results and handoff information. Voice features may process audio and, where configured, transcripts or recordings. The records retained depend on the feature and business configuration.

AI, speech and infrastructure providers may receive the inputs necessary to operate a requested feature. Provider processing, retention and model-improvement rules depend on the provider, account configuration and applicable agreement; this policy does not promise a universal no-retention or no-training setting.

ASG and Gateway can expose approved public business identity, links and capabilities to AI clients. Requests may generate authentication, security and usage records. Public discovery content should not contain account credentials or private customer conversations.

Automated tools can extract, summarise, classify, match and rank business information. Errors can affect what appears in a result or profile. Ask for a review if information or a match is wrong. A Directory score is a discovery signal, not a personal credit assessment; paid placement does not establish registry verification.

When you choose an “Ask AI” link, it opens an external service with the explanatory prompt or public links provided by that feature. That service controls its own account, conversation and privacy settings. Check the prompt before adding confidential information.

Human handoff and workflow actions. A configured agent may pass conversation context to a Human Inbox, an authorised business user or a connected workflow. The information sent depends on the enabled function. Review the destination and content before using a feature to transmit confidential information or act on a customer’s behalf.

Voice notices and permissions. A business enabling voice capture, transcription or recording is responsible for the notices and permissions required for that interaction. Browser microphone permission allows technical access to the microphone; it does not resolve every legal requirement for recording or subsequent use. Ask the business whether a particular conversation will be recorded or retained.

Ranking and discovery. Search results can vary with a query, filters, available business information and the selected sort. Featured placement may prioritise eligible paid profiles, followed by other relevance or quality signals where configured. A paid position is not evidence that the owner is more trustworthy, and it does not replace the separate meaning of a registry or ownership check.

Review of automated results. You can challenge incorrect extracted content, a business match or information used in a profile through the correction and support routes. Include the specific result and the reason you believe it is wrong. An AI-generated response should be checked before it is used as business, legal, financial or other consequential advice.

The WebsDocs ASG Directory is designed for public business discovery. Directory information can come from information a business or profile owner provides, public business websites and contact routes, and supported public registries, government authorities, or authority APIs where WebsDocs is permitted to access and use that information.

Depending on the jurisdiction and source, business-verification processing may involve public business names, legal names, trading names, jurisdiction, registration or company identifiers, public registration status, registered or business addresses where publicly available, website and public contact information, authority/source references, verification-result fields, and timestamps or freshness information used to show when a check occurred or should be refreshed.

The verification process may compare normalized names, legal names, jurisdiction, registry identifiers, and other supported evidence to determine whether a Directory record matches an authority record. The resulting Business Registry Verification status is kept separate from owner claim, profile-control, account, domain, or login verification.

Public Directory responses are intended to expose only public-safe business and verification information. WebsDocs does not intend to publish API credentials, secret keys, internal diagnostics, private dashboard records, private customer conversations, billing records, non-public authority fields, or unrelated personal information as part of the public business-verification result.

Some public business registries can contain personal information connected with a business, particularly for sole proprietors, directors, officers, representatives, or other people whose details form part of a public business record. Where such information is processed for ASG Business Registry Verification, WebsDocs aims to limit that use to the business-identity, registry-evidence, accuracy, security, and public-discovery purposes reasonably connected with the Directory rather than using it for unrelated personal profiling.

The verification system may maintain internal check records needed for matching, retry handling, rate-limit management, auditing, evidence review, scheduled rechecks, source troubleshooting, and correction work. Public profile JSON or Directory cards do not need to expose every raw authority response or internal processing record.

Registry information can change and different sources can conflict. A later authority check may discover a changed legal name, status, registered address, identifier, or other business detail. Verification results may therefore be refreshed, reclassified, suspended, or removed where evidence changes, a source becomes unavailable, or a result no longer meets the current verification policy.

If a business or individual believes a Directory record is inaccurate, misleading, stale, or improperly connected to them, they may contact WebsDocs through the normal support or privacy-request channels. Where the disputed fact comes from an official authority, WebsDocs may need to compare the request with the authority source, perform a new verification check, or ask the requester to correct the underlying official record where WebsDocs cannot lawfully or technically alter the source itself.

Access to registry or authority information may involve requests to external services. Those authorities and providers operate independently and may apply their own privacy notices, access rules, retention practices, rate limits, regional processing, and technical policies. See Terms: ASG Directory and Business Registry Verification and Terms: Third-Party Tools, Platforms, and Providers.

Where a business enables a connected messaging channel, information needed to deliver the interaction may pass between WebsDocs, the business and the channel provider. Depending on the feature, this can include a telephone number or channel identifier, message content, attachments, delivery status and reply context.

Channel providers operate under their own terms and privacy notices. A business that initiates messages is responsible for the permissions and notices required for its use. You can use the channel’s blocking or notification controls and contact the business about its communications.

We use account and contact information to send verification or access messages, respond to support, communicate service changes and handle billing. Payment providers process checkout information; WebsDocs uses relevant transaction references, product or plan details, payment status and billing records for service administration.

Marketing communications are separate from necessary service messages. Where offered, use the unsubscribe instructions or contact us to stop marketing. An opt-out does not prevent essential account-security, transaction or requested support messages.

Do not send full card details through a support form. For a billing enquiry, a transaction reference and account email are usually a better starting point.

Information may be handled by authorised personnel and providers supporting hosting, storage, security, email delivery, payments, registry checks, analytics, AI or voice processing, and technical support. The information involved should relate to the function being provided.

Business owners and authorised team members may receive the enquiries, conversations and account records relevant to their service. Public profile fields are available to the public and may be used by search engines and AI clients.

We may disclose information when required by law or necessary to address fraud, security incidents, legal claims or the protection of rights. A business transfer may involve relevant records, subject to applicable privacy obligations.

WebsDocs is not presented as a personal-data brokerage service. Public directory distribution is different from sharing private account or conversation records; public access is not permission to misuse personal information.

Minimum information for a recipient. A payment provider needs different information from an email-delivery service or a registry source. Information shared for one function should be appropriate to that function. Provider access and processing obligations depend on the relevant agreement and role; an external service used independently may set its own purposes.

Public reuse and external copies. Search engines, AI services and other visitors can access information intentionally published in public profiles or APIs. Their subsequent processing may be outside WebsDocs’ control. If a correction is important, also check where the information originally appeared and any independent services that continue to display an older copy.

Our services use cloud and external providers, and information may be processed in countries different from the country where you live. A selected storage region does not necessarily determine every location used for network delivery, support or provider processing.

For transfers subject to specific data-protection requirements, the applicable transfer mechanism and safeguards depend on the service, recipient and jurisdiction. Contact us for information about the providers, locations and safeguards relevant to your service; a specific residency commitment must be stated in the applicable service agreement.

External websites, registry sources, payment pages, messaging platforms and AI services may act independently for their own processing. Review their notices when you use them. This page does not promise that all processing takes place in a single country or region.

Features may use cookies, browser storage or similar identifiers for sign-in, security, preferences and service operation. Technical request logs and server-side activity measurement can also exist without a browser analytics cookie.

You can manage browser storage through your browser settings and any controls provided by the feature. Blocking essential storage may interrupt sign-in or saved preferences. Where optional tracking requires consent, a privacy-policy link alone is not consent.

Public totals and seven-day summaries do not mean that all underlying records are anonymous. Privacy requests can cover identifiable technical information where applicable, subject to the information needed to locate the relevant records.

Public listings: retention depends on continued business relevance, source freshness, correction or removal decisions and any need to document a disputed change. An account closure and a public-listing removal are separate requests.

Accounts and verification: records are retained according to the active service relationship, access requirements, ownership disputes and security needs. Messages, uploaded materials and agent records depend on the feature, its configuration and any agreed retention terms.

Support, billing and logs: retention takes account of resolving the issue, troubleshooting or investigating misuse, statutory accounting requirements and legal claims. Different record types can require different periods; this policy does not set one universal period for all services.

Deletion from an active system may not immediately remove backup copies, cached responses or records subject to a legal retention requirement. Where information must be retained, its use should be limited to the relevant purpose. Ask us about the retention criteria for a particular record or service.

Legal holds and unresolved matters. A deletion request may need to be balanced against a specific legal obligation, unresolved ownership dispute, fraud investigation or legal claim. Such an exception is not a reason to keep every record indefinitely. The relevant category, purpose and applicable requirement should determine what must remain.

Backups and independent copies. Operational deletion and backup expiry can occur on different schedules. A retained backup is distinct from an active public profile. Independent registries, business websites and search engines determine their own records and correction procedures; removal by WebsDocs does not amend those sources automatically.

Account controls, verification procedures and technical safeguards help protect information, but no internet service can guarantee absolute security. Protect your login links and credentials, restrict workspace access and contact support if you suspect unauthorised use.

Only provide personal information needed for the task. Our general business submission and support flows are not intended for unnecessary health records, government identity documents, financial credentials or other sensitive material. If evidence is requested, use the specified route and redact unrelated information.

WebsDocs products are intended for business use and are not directed at children. If you believe a child’s personal information has been submitted or published inappropriately, contact us so we can investigate.

Depending on applicable law and the circumstances, you may have rights to access your personal information, correct it, request erasure, restrict processing, obtain a portable copy, object to processing or withdraw consent. Rights and exceptions vary by purpose and jurisdiction.

You may object to direct marketing at any time. Where the right applies, you may also object to legitimate-interest processing on grounds relating to your situation. Email hello@websdocs.com and identify the relevant record or service.

We may ask for proportionate information to locate a record and verify your identity or authority. You do not need to purchase a service to exercise a privacy right. Requests are handled under applicable legal time limits and exceptions; if a request cannot be fulfilled in full, the reason should be explained.

You may complain to the data protection authority relevant to your location or the processing. For example, UK residents can contact the Information Commissioner’s Office. Contacting us first can help resolve an issue, but is not a condition of making a regulatory complaint.

Representatives and scope. You may ask an authorised representative to contact us. We may need evidence that they may act for you, while avoiding unnecessary documents. If your request concerns a company record, identify the personal information involved and explain your connection to it; commercial disagreement and a personal-data rights request may require different reviews.

Information relating to other people. A response may need to protect another person’s information, account security or legally protected material. This can affect what can be disclosed, but does not remove the need to consider the request. A listing URL, approximate interaction date or reference number can help locate records without collecting additional sensitive information.

Consent and objection are different. Withdrawing consent concerns processing that relies on consent. An objection concerns processing for which a right to object applies, such as certain legitimate-interest uses or direct marketing. Tell us what activity you want stopped; you do not need to choose the correct legal term before contacting us.

We update this notice when relevant products, processing practices or legal requirements change. The date on this page identifies this version. Material changes may require a further notice or consent where applicable; publication of a revised policy does not itself supply that consent.

A product-specific notice or agreement may provide more detail about an enabled feature. It does not remove statutory privacy rights.

Visit the Directory, Owner Workspace, Profile Studio, RTD Business Agent or ASG AI Sales Gateway for the relevant service.

For commercial information, read the Terms and Conditions, Payment Information and product pricing. For a service issue, use Support.

Email hello@websdocs.com with “Privacy request” in the subject, or use Support. Include the listing URL, relevant service or account email, and what you want us to review. Send only what is needed to identify the issue.

For public business information, you can also use Request a correction or Request removal. A privacy request does not require a paid account. If you are acting for someone else, explain your authority.

Last updated: November 5, 2026.

What to include. Describe whether the issue concerns a public business profile, an Owner Workspace account, a website scan, a hosted page, an RTD or BizDesk conversation, an ASG service, billing or support. Include only the references needed to find the record, and explain the correction, access or deletion you seek.

If your request concerns another business. For an agent conversation or enquiry managed by another business, that business may need to decide the response to a request about its customer records. Contact it directly where possible. If you do not know which business received the information, provide the page and service context so we can help identify the relevant route.