How AurumMise handles information.

AurumMise uses Clover information to answer your questions, remember useful context, and prepare new changes you approve first. Aurumpay does not sell merchant data or Clover data. Do not type card numbers, passwords, bank details, Social Security numbers, or Clover secrets into chat.

• Clover merchant information, such as business profile, address, opening hours, menu, prices, taxes, discounts, stock, labels, printers, devices, and other setup details when Clover shares them with AurumMise.
• Clover employee information, such as names, nicknames, email addresses, custom IDs, broad roles, shifts, and roster or activity context when available.
• Clover customer information, such as customer identifiers, names, marketing preferences, customer-since dates, and purchase or activity context when available.
• Clover order and payment metadata, such as line items, totals, taxes, tips, tenders, status, refunds, and timestamps. AurumMise does not need full card numbers to provide its Clover features.
• Clover connection information, including merchant and app identifiers, granted permissions, subscription status, token expiration information, and encrypted OAuth access and refresh tokens used to access Clover on your behalf.
• Pseudonymous billing information, such as a one-way merchant fingerprint, installation generation and dates, UTC billing period, included allowance, successful-request ordinal and count, billing-policy snapshot, metered delivery status, and Clover receipt identifiers. The billing ledger does not contain prompts, answers, merchant names, OAuth tokens, or Clover snapshots.
• Essential cookie and local-storage information used to maintain and protect the active AurumMise session and remember appearance preferences. AurumMise does not use these technologies for cross-site advertising.
• Chat information, such as your messages, assistant replies, saved chats, preferences, approval cards, pending changes, completed changes, and feedback you send us.
• Uploaded chat files, such as images, PDFs, CSV, TSV, Excel files, processor statements, quotes, and notes saved from those files when you attach them for AurumMise to review.
• Voice information, such as a short recording sent for transcription and the resulting text. AurumMise does not save the raw recording as a chat attachment, but a transcription service processes it and the text becomes chat information if you send it.
• Customization information, such as a custom background image and appearance preferences when you choose to save them.
• Notification contact information, such as the email address you provide so AurumMise can let you know when a longer Clover task is ready.
• Legal acceptance information, such as the connected merchant workspace, Clover employee or merchant-session scope, accepted Terms of Service and Privacy Policy versions, and the time you agreed.
• Rate review information, such as processor statements, quotes, uploaded files, and the email address or phone number you provide for follow-up.
• Support information, such as bug reports, feature requests, reply email, and messages you send to Aurumpay.
• Basic service information needed to run and protect AurumMise, such as app activity, error details, browser or device details, user agent, and security or reliability logs.

• Connect the correct Clover merchant, refresh the connection, and answer questions using the Clover information available to AurumMise.
• Create read-only sales and operating analysis from orders, payments, inventory, customers, employees, and merchant setup where supported.
• Review supported uploads, including menu files, setup documents, employee rosters, images, and statements when you ask AurumMise to use them.
• Prepare new supported inventory, business-setting, employee, and broad-role changes for your review and apply them only after approval; send a selected order print or reprint request only after approval; undo an eligible saved change only when you select Undo this change in Settings → Changes.
• Let longer Clover reviews or approved changes keep going after you start them and notify you when they are ready, if you ask for notification.
• Keep saved chats, preferences, and change history tied to the right business.
• Record which current Terms of Service and Privacy Policy versions an authorized merchant user accepted before assistant requests or Clover changes are available.
• Measure included and additional successful assistant requests, deliver eligible metered events to Clover, reconcile statements, prevent reinstall resets and duplicate charges, review possible churn abuse, and resolve billing disputes.
• Transcribe a voice recording into draft text when you choose voice input on a supported browser.
• Store and deliver a statement or quote to the Aurumpay review team only when you explicitly submit it for rate review and AurumMise confirms the submission.
• Provide support, troubleshoot issues, prevent misuse, protect the service, and meet legal or Clover App Market obligations.

The successful-assistant-request allowance for the active Essentials policy is shown in Clover and in AurumMise usage settings. A successful request is one merchant-initiated run that commits a usable visible response, including a valid response that needs approval. Behind-the-scenes work, attachment review, applying an approved change, and using a supported Undo do not count as separate requests. Failed, cancelled, superseded, and duplicate requests do not count.

Usage resets at 00:00 UTC on the first day of each month. A first or restarted partial month receives a prorated allowance based on the inclusive UTC calendar days remaining. Reconnecting, changing an employee or device, refreshing a token, or reinstalling does not reset the same Clover merchant's usage for that month.

Requests beyond the included allowance are reported to Clover as metered usage and may appear on a later Clover statement. The restricted pseudonymous ledger described below is retained for 24 months for usage continuity, reconciliation, duplicate-charge prevention, fraud review, and billing disputes; it excludes prompts, answers, merchant names, OAuth tokens, and Clover snapshots.

We share information only as needed to provide, protect, or support AurumMise and Aurumpay services. We do not sell merchant data or Clover data.

• Clover, when you connect Clover, approve a change that must be sent to Clover, or use additional successful assistant requests that AurumMise reports as metered events for Clover billing.
• Trusted companies that help AurumMise answer questions, review supported files, prepare draft review cards, or convert voice input to text.
• Trusted companies that provide hosting, storage, security, email, monitoring, and customer support for AurumMise.
• Professional advisors, authorities, or other parties when needed for legal, security, or business reasons.
• A successor or transaction adviser if Aurumpay is involved in a merger, sale, financing, or transfer of the AurumMise business, only as permitted by law, applicable Clover requirements, our contracts, and equivalent data protections.

AurumMise may send your message, relevant Clover information, attachment evidence, and recent chat context to trusted companies that help AurumMise answer questions, review supported files, prepare a review card, or convert voice input to text. They process only the information needed to provide the requested AurumMise feature. Keep sensitive information out of chat and uploads unless it is needed for the request.

Aurumpay does not sell merchant data or Clover data. AurumMise answers can be wrong, so you should review answers and every approval card before relying on them.

A normal chat upload does not by itself submit a rate review. When you explicitly submit a statement or quote and AurumMise confirms the submission, the file is stored in private cloud storage and delivered with your contact information and request details to the Aurumpay review team by email. The submission is used for that requested review and related follow-up, not to process or change a Clover payment.

• You can disconnect AurumMise from Clover through Clover or by contacting Aurumpay.
• You can ask us to review, correct, export, or delete information tied to your business.
• You can ask us to delete saved chats, custom backgrounds, chat files, notes saved from uploaded files, and uploaded statements or quotes tied to your business.
• You can ask us to stop using uploaded statements or quotes for a rate review.
• Some records may need to be kept for security, billing, legal, backup, or completed-change history.

To make a request, email support@aurumpay.com or use the Data Deletion page.

Depending on where you live or do business, you may have the right to ask what personal information we have, request a copy, ask us to correct it, ask us to delete it, or opt out of certain sharing. Aurumpay does not sell merchant data or Clover data. We will not punish you for making a privacy request.

Aurumpay uses reasonable safeguards to protect information, including limiting access to people and trusted companies who need it to operate or support AurumMise, separating business information by merchant, encrypting stored Clover OAuth tokens, and limiting what the assistant is allowed to change in Clover. No online service can promise perfect security.

AurumMise does not receive or store your Clover password. OAuth connection tokens are encrypted at rest and are not displayed in chat.

We keep information for as long as needed to provide AurumMise, support merchants, protect the service, keep change history, meet legal obligations, or resolve disputes. When information is no longer needed, we delete it or remove details that identify it where practical.

When Clover reports that a merchant uninstalled AurumMise, we remove that merchant's active AurumMise workspace, including its workspace-scoped legal acceptance records, and permanently delete its stored attachment and custom-background objects, including noncurrent object versions. Merchants who need a copy should request an export before uninstalling. Limited backup, security-log, legal, fraud-prevention, or dispute records may follow separate restricted retention requirements. We retain the minimal pseudonymous billing ledger for 24 months so usage survives a reinstall, Clover charges can be reconciled, duplicate charges can be prevented, and billing disputes can be reviewed. We also retain a one-way App-event fingerprint and uninstall time so a duplicate Clover delivery cannot erase a later reinstall. Neither record contains the raw merchant ID, workspace content, prompts, answers, OAuth tokens, or Clover snapshots.

Unsent upload drafts are scheduled for deletion after about 24 hours. Once a file is sent in chat, its private raw source and saved extracted details are scheduled for deletion after about 180 days so you can ask AurumMise to use the same saved source later in the conversation. A file is removed sooner when you delete it or its conversation or uninstall AurumMise. Saved review history is also bounded to 180 days. Saved chats may still contain the file name, assistant response, and details included in the conversation. Saved chats, customizations, support records, rate-review files, and completed-change history may remain longer as needed for the service, the requested review, legal or security obligations, or a deletion request review.

AurumMise is not designed to track users across websites for advertising. We do not currently respond to browser Do Not Track signals.

AurumMise is for business users. It is not intended for children under 13.

We may update this policy as AurumMise changes. If the changes are important, we will update the date on this page and may provide additional notice.

Questions: support@aurumpay.com