Updated October 21, 2026 · AI integrations and public listing search
Privacy Policy
AZNO is operated by ALEVA TECHNOLOGIES INC. This policy explains how we handle information when you use the AZNO website, mobile apps and marketplace services.
Information we collect
The current mobile release collects your first and last name, email address, phone number, country, region or state, city, account role, and account identifier when you create an account. If your selected role requires it, the release also collects an organization name and buyer type. It records the agreements and consent choices you submit. If you use seller or sourcing tools, it also collects the equipment details, requirements and notes you submit. Reports and blocked-seller choices are stored when you use those safety controls. AZNO does not collect identity documents, equipment-photo uploads or in-app messages in this release.
Website early-access and seller requests
When you submit the website launch form, we store your name, email address, organization if provided, requested access type, professional role, platform preference and the date and version of your contact consent. We also store the source and campaign labels attached to the form link so we can measure launch interest. These requests are separate from mobile-app accounts and do not verify a seller. With your consent, ALEVA TECHNOLOGIES INC. may contact you about your request, seller onboarding and launch availability. No automatic confirmation email is sent.
If you receive a directly addressed AZNO invitation, its link may contain a random invitation identifier. We record when that link is resolved, whether the linked website form is completed, and whether the App Store button is selected so we can measure the invitation campaign. The identifier does not contain your email address or name. Link resolutions can include automated email-security scans and are not treated as proof that a person viewed the page.
Requests are stored with our hosting and database service providers and are not publicly displayed. We use a short-lived, hashed network identifier to limit automated submissions; the hourly record is removed on subsequent form activity after it expires. You may withdraw consent or request access, correction or deletion by contacting support@aznoapp.com. We retain a request only while needed to manage the launch or follow up on it, unless a legal obligation requires otherwise.
Public campaign links
Public AZNO campaign links (/go/) record daily aggregate request counts by post and request category to measure advertising-link use. Known automated previews and our test checks are separated from other requests; these counts do not establish unique people or purchases. This feature does not store IP addresses, raw browser identifiers, account identifiers or tracking cookies. Aggregates older than 365 days are removed on subsequent campaign-link activity. Hosting providers may separately process technical security logs.
On public website pages, AZNO records visit counts by broad source, such as a named social platform, search, or direct/unattributed. Attribution uses a campaign source label or the referring website's domain; the database does not store the full referring URL. Cloudflare derives a two-letter country code from the network connection. AZNO stores that country code with the visit time, broad source and landing-page path for up to 90 days, but does not store the raw IP address, browser user-agent or an account identifier for this measurement. A temporary browser-tab session marker prevents repeat counts within the same UTC day and is not transmitted to AZNO. These counts are not unique people. Visits may be missed when scripts or storage are blocked.
Registration journey measurement
To understand whether our own campaign links lead to account creation, we use a random first-party journey identifier for up to 30 days. It is carried from aznoapp.com to our AZNO web app and stored in a first-party cookie or browser-tab session storage. We record the campaign source, steps viewed, broad error categories, and time of activity, but never passwords, verification codes, form contents or raw IP addresses. A completed registration is counted only after our server confirms a new verified account, profile and required agreements. A one-way account fingerprint prevents duplicate conversion counts. These minimised records are retained for up to 90 days and are available only in our restricted operations console. We respect browser Do Not Track and Global Privacy Control signals for this measurement. You may request removal through support@aznoapp.com. Inactivity indicates only that no further step was observed, not why someone stopped. Forwarded or manually labelled campaign links can affect attribution; we do not identify visitors across unrelated sites.
Payments
AZNO does not collect or store full payment-card numbers or card security codes. Where checkout is available, payment information is entered directly on a Stripe-hosted checkout page and is handled by Stripe under its privacy policy. AZNO keeps only the order and transaction records needed to operate the marketplace, such as payment status, amount, currency and processor transaction identifiers. We do not use payment information for advertising or tracking.
How we use information
We use information to create and secure accounts, review seller drafts, respond to sourcing and support requests, review reported content, prevent fraud and abuse, comply with law, and maintain reliability. The current mobile release does not enroll account holders in marketing messages.
Sharing
A seller draft is not public unless AZNO separately reviews and approves it. Approved listing information may then be visible to marketplace users. We use service providers for hosting, authentication, email, storage and security under appropriate contractual controls. The current release does not include an analytics or advertising SDK, and we do not sell personal information.
Retention and deletion
We keep information only as long as needed for the purposes above. In-app account deletion revokes sessions and deletes the Firebase Authentication account, profile, consent records, seller drafts, sourcing requests, reports and blocked-seller records linked to that account. Service-provider security logs or records required by law may remain for their documented retention period. See Account Deletion.
ChatGPT integration
When you use the AZNO plugin in ChatGPT or Codex, OpenAI may use relevant conversation or memory context to select and populate a tool call. Depending on the requested function, the AZNO MCP service processes schema-defined values such as language, request type, equipment brand, host system, catalog search, model, device format, intended application, equipment condition or issue notes, and limited photo metadata consisting of file name, media type, and file size. The current AZNO tools do not request a raw conversation transcript or memory history, and the service does not receive or upload photo bytes. Do not include patient records, patient images, credentials, payment information, government identifiers, or other sensitive personal data.
The current plugin uses a packaged equipment catalog and prepares an unsent equipment brief. It does not connect to an AZNO customer account or database, submit a request to AZNO, publish a listing, accept payment, upload photos, verify stock or prices, guarantee compatibility, or produce a valuation or purchase offer.
The current AZNO MCP service does not save tool arguments or generated briefs in an AZNO customer database. It processes each request to return a result to ChatGPT or Codex. The MCP application code does not log request bodies or authentication tokens. Google Cloud hosts the service and may process operational and security records such as network and request metadata, timestamps, status codes, and service logs under its configured retention controls. These provider records may remain until the applicable retention periods expire.
ChatGPT or Codex may retain the conversation and plugin results according to the user's OpenAI account, workspace, and data-control settings. Those platform records are separate from the current AZNO MCP service. Users can manage applicable OpenAI conversation controls through their OpenAI account and can contact info@aznoapp.com about AZNO privacy questions.
Claude integration and public listing search
When a user asks the AZNO connector in Claude to search public listings, the AZNO MCP service sends only the equipment search terms and requested page number to AZNO's existing anonymous public-listings service. Results are limited to public marketplace fields such as the listing identifier and link, equipment brand and model, category, condition, connector and compatibility text, seller-provided price and currency, broad location, lead time, warranty, included items, public seller name or badge, and whether the image is marked as a reference image.
The connector does not return listing-owner account identifiers, customer contact details, messages, orders, private notes, moderation records, serial numbers, temporary image URLs, hidden drafts, or patient information. It does not use the public listing search to submit an inquiry, reserve equipment, place an order, upload a photo, or access an AZNO customer account. Do not put patient information, customer records, credentials or payment details in a listing-search query.
Public listing details are seller-provided and may change. A search result is not confirmation of current stock, final price, tax, shipping, authenticity, connector fit, compatibility, lead time or warranty. Users should review the linked listing and confirm important details with AZNO. The connector requests current results without a persistent catalog cache. Hosting providers may still process ordinary operational and security logs, and Claude may retain the conversation and connector results according to the user's Anthropic account and data-control settings.
Security and international use
We use administrative and technical safeguards appropriate to the information involved, but no online service can guarantee absolute security. Information may be processed in the United States, Canada or other countries where our providers operate, subject to applicable safeguards.
Your choices
You may delete your account in Settings or contact us to request access, correction or deletion where local law provides those rights. AZNO is intended for business and professional users and is not directed to children under 13.
Contact
Privacy questions may be sent to support@aznoapp.com. Include the email used for your AZNO account and do not send passwords, one-time codes, payment details or identity documents.