Collect only what the workflow needs.

Inquiry forms may collect your name, work email, organization, inquiry type, asset class, jurisdiction, project stage, requested service, and a short project summary. When you explicitly submit a procurement brief for review, the stored record may also include a project label, investor segment, accountable decision-owner role, timeline, budget range, integration categories, public provider IDs, and the generated requirements packet. Generating or exporting a brief without submitting it does not store that project with TaaS.

Provider evidence submissions may also collect provider identity and website, job title, submitter relationship, a scoped claim, accountable layer, public source URL and title, source date and type, market coverage, conflict disclosure, and review notes. We record the required attestations and consent to contact you about the submission.

Please do not submit private keys, passwords, wallet credentials, government identifiers, identity documents, investor lists, securities orders, bank details, non-public offering documents, health data, or other highly sensitive information.

The site may record a permitted event name and page path to understand page use and calls to action. The TaaS analytics endpoint does not set an analytics cookie and does not intentionally store IP addresses, device fingerprints, full referrer URLs, or cross-site identifiers.

Infrastructure providers may process technical request data needed to secure and operate the service under their own contractual and legal obligations.

When you ask the concierge a question, the current page, your question, and up to six recent messages from that open conversation are processed to produce the response. TaaS does not intentionally persist the chat transcript as an application record. A short-lived pseudonymous request bucket may be created for abuse prevention and rate limiting without storing the raw network identifier in that bucket.

Supported questions are matched to an approved source set. When an external AI model is configured, that limited question and approved context may be sent to the AI service provider for transient processing with application-level response storage disabled. Infrastructure and model providers may still process technical or abuse-monitoring data under their applicable terms. Do not enter confidential information, personal investor information, transaction instructions, credentials, private keys, wallet recovery information, or non-public documents.

• Respond to the inquiry and assess service or design-partner fit
• Review opt-in procurement requirements, evidence gaps, and fixed-fee service fit
• Build or correct provider evidence profiles
• Operate, secure, debug, and improve the site
• Maintain records of consent, evidence origin, and correction requests
• Meet legal obligations and protect rights

TaaS does not sell personal information or investor access. Information may be shared with service providers supporting hosting, storage, security, and communications, or when required by law. Project information is not sent to tokenization providers unless you authorize that step in a separate workflow.

Inquiry records are retained only as long as reasonably needed for the stated workflow, evidence history, security, dispute resolution, and legal obligations. You may request access, correction, or deletion by emailing privacy@taas.solutions; some records may need to be retained where legally required or necessary to preserve an evidence trail.

This is an operational policy for the initial product. Before broad public launch or paid engagements, TaaS should complete counsel review, confirm applicable jurisdiction-specific notices, vendor terms, retention controls, and a data-subject request process.