You connect Clover
Clover shares the data covered by the AurumMise app permissions you accept during installation and connection.
Data safeguards
How AurumMise uses Clover information.
AurumMise uses your Clover information to answer questions, remember helpful details, and prepare new changes you approve first.
It reads business details
It can use menu, price, tax, order, payment, customer, team, printer, and setup details when Clover shares them.
It keeps useful history
Saved chats, preferences, pending changes, and completed changes stay connected to the right business.
It reviews supported uploads
Images, PDFs, CSV, TSV, and Excel files can be used as evidence for menu, setup, or roster requests when you attach them.
It supports voice input
On supported browsers, a short recording can be converted to text so you can review it before sending it in chat.
Separate statement submissions
If AurumMise confirms that you explicitly submitted a statement or quote and contact information for rate review, Aurumpay uses that submission for the requested follow-up. This is separate from Clover payment processing.
Approval first
New Clover changes stay review-first.
AurumMise can explain a new forward change, but it waits for you before changing Clover.
- 01
You ask for a change.
- 02
AurumMise shows what would change.
- 03
You approve only if it looks right.
- 04
AurumMise applies the change and keeps a record.
Protection details
How AurumMise limits data and actions.
AurumMise synchronizes the permitted Clover information needed to operate the service, selects relevant context for each request, and keeps supported forward Clover changes inside the approval-card workflow.
Clover access is tied to the connected merchant account and the permissions Clover grants. AurumMise never asks for your Clover password and stores OAuth connection tokens encrypted.
Sensitive connection details and internal credentials are not shown in chat. Essential cookies protect the active AurumMise session.
Supported chat uploads are limited to 5 files, 15 MB each, and 75 MB total. Unsent drafts are scheduled for deletion after about 24 hours. Sent private source files and saved extracted details are scheduled for deletion after about 180 days so a merchant can use the same saved source later; deletion or uninstall removes a source sooner. Saved review history remains limited to 180 days.
Trusted companies process only selected relevant information to answer questions, review supported files, prepare draft review cards, or convert voice input to text.
Longer work can continue after you start it without widening what AurumMise is allowed to change.
Boundaries
What merchants should know.
New changes do not run in Clover unless you approve them first. Eligible saved changes can be undone directly from Settings → Changes.
AurumMise synchronizes permitted Clover data needed to operate the service, then selects relevant chat, Clover, and uploaded-file context for each assistant request.
Instructions inside an uploaded file cannot authorize Clover changes or bypass safeguards. Do not upload sensitive personal or financial information unless it is required for an explicitly requested statement review.
AurumMise does not create or edit customers, orders, payments, refunds, captures, voids, surcharges, service charges, ecommerce transactions, or employee shifts, and it does not move money.
Supported employee information and broad employee roles can change only after you approve a review card and the connected Clover business allows it.
You should not type card numbers, passwords, bank details, Social Security numbers, or Clover secrets into chat.
One business's information stays separate from another business.
Legal and privacy
Simple pages for the details.
Last updated
July 10, 2026