Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
Your Privacy Choices
Control how AWRA handles privacy preferences and rights requests.
AWRA gives public visitors, prospects, customers, vendor users, and account contacts clear ways to manage cookies, communication preferences, and personal data rights.
Manage cookies and browser storage
Use the Cookie Preference Manager to choose optional functional, analytics, and engagement storage where available. Required security cookies remain active for sessions and form protection.
Open Cookie PreferencesRequest access or correction
Ask AWRA to help identify, access, correct, or explain personal information processed through public forms, support, account records, or product workflows.
Contact Privacy DeskRequest deletion or restriction
Request deletion, restriction, anonymization, or retention review where applicable. Some operational, accounting, security, or legal records may need to be retained.
Start RequestRequest types
Common privacy requests AWRA can help route.
Access
Ask what personal data AWRA processes about you and why.
Correction
Ask AWRA to correct inaccurate account, contact, or support details.
Deletion
Ask for deletion or anonymization, subject to legal, security, billing, and operational retention needs.
Restriction
Ask AWRA to limit processing where a dispute, review, or regulatory right applies.
Portability
Ask for a practical export path for relevant personal data where legally available.
Objection or opt-out
Ask AWRA to stop certain optional processing or communication where applicable.
How to submit a rights request
A little detail helps protect the account and speed up review.
Identify yourself
Provide your name, email, organization, account role, and the request type so AWRA can verify and route it.
Describe the data
Mention whether the request involves public forms, app account data, vendor portal use, support messages, billing, or marketing.
Complete verification
AWRA may request reasonable verification before sharing, changing, deleting, or restricting personal data.
Receive response
AWRA reviews the request, explains what can be done, and identifies any legal or operational retention limits.
Important context
Customer organizations may control certain account records, roles, operational workflows, and user access. AWRA may need to coordinate with the organization administrator for workspace data.
Security, audit, accounting, billing, fraud prevention, and legal records may be retained when required or when deletion would compromise operational integrity.
For more detail, review the Privacy Policy, Data Processing Addendum, Data Processing Agreement, and Cookie Policy.
Where privacy data may appear
Your request route depends on the context where the data was created.
AWRA supports public website visitors, customer workspaces, vendor users, field users, and account administrators. Each context may have different controller, processor, verification, and retention considerations.
Public website visitors
Search terms, form submissions, demo requests, cookie preferences, engagement prompts, analytics signals, and contact messages.
Customer account users
Profile details, organization membership, role assignments, login events, support activity, and workflow audit records.
Vendor portal users
Supplier contacts, quotation activity, purchase-order acknowledgements, messages, documents, and authentication records.
Mobile and field users
Scan activity, offline sync records, device metadata, GPS-backed evidence where enabled, and field approval actions.
Billing and admin contacts
Plan records, invoices, subscription details, payment provider references, billing messages, and account administration notes.
Support and security contacts
Troubleshooting details, attachments, incident notes, device trust signals, and security review communication.
Choice matrix
Pick the control that matches your privacy goal.
This matrix turns abstract rights into practical AWRA actions. Some requests may require identity verification or customer administrator coordination.
Retention limits
Some data cannot be removed the same way as a public-form message.
Security and abuse prevention
Login events, device trust records, audit logs, rate-limit evidence, and fraud signals may need to remain available for security review.
Accounting and billing
Invoices, subscription records, payment references, and tax-related records may be retained for legal and accounting obligations.
Operational integrity
Inventory movements, approvals, purchase orders, asset custody, and finance records may require retention to preserve customer audit trails.
Legal holds and disputes
Records may be retained when necessary to investigate claims, comply with lawful requests, enforce terms, or defend legal rights.
Privacy questions
What people usually ask before submitting a request.
Can AWRA delete all of my data immediately?
Not always. AWRA reviews the request against security, accounting, contractual, operational, and legal retention needs before deletion or anonymization.
Can I use a browser privacy signal?
Browser-level signals and blocked storage can reduce optional tracking. The AWRA Cookie Manager also provides explicit public website choices where available.
Who controls data in my employer workspace?
The customer organization often controls user membership, operational records, role access, and business data. AWRA may need to coordinate with that administrator.
Will opting out stop service emails?
No. Opting out of marketing does not stop security alerts, billing notices, account messages, implementation updates, or transactional service communication.
Help Center
Need a quick answer while you read?
Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.