AuraLab keeps privacy information centralized where possible so product behavior stays easier to review and maintain. This page covers AuraColor Picker, Aura Image Toolkit, Vanguard OMNI, RightLive Translate, and AuraLab website and tool pages. AuraDesk keeps a separate product privacy page because its Chrome review and feature scope are handled separately.
Jump to a product
How AuraLab handles data
AuraLab tries to keep product data local when the workflow allows it. We do not sell personal information, and we do not ask for unrelated data just to provide small browser or web utilities.
Depending on the product, AuraLab may store extension preferences, local workflow settings, saved vocabulary, palette data, or lightweight license state required to enable a paid feature. When a product needs third-party services, we aim to send only the minimum information required for the requested function.
AuraColor Picker
AuraColor Picker is designed as a local-first color workflow. It helps users pick colors from webpages, save palettes in the browser, and export local files such as HEX, CSS, JSON, SVG, and PNG.
What AuraColor may store
- Saved color palettes
- Palette organization preferences
- Export-related local settings
- Interface preferences needed for the color workflow
What AuraColor does not require
- No account signup
- No cloud profile to use the core workflow
- No payment information for the free version
Aura Image Toolkit
Aura Image Toolkit is designed as a lightweight image workflow utility for cleanup, enhancement, resizing, conversion, and export. The goal is to keep common image preparation work faster and easier without introducing account-heavy product friction.
What Aura Image Toolkit may store
- Local workflow preferences such as export settings or recent tool choices
- Temporary in-browser image processing state while you use the tool
- Minimal local settings needed to keep the interface usable between sessions
- Purchase email, license key, or license status metadata only when Pro validation is required
What Aura Image Toolkit is expected not to require
- No account for core lightweight workflows
- No unrelated personal profile data for basic image utilities
- No persistent cloud storage requirement for simple exports
- No image upload just for license validation
Pro activation and Pro Lifetime scope
Aura Image Toolkit Pro uses email and license-based activation. When Pro validation is required, AuraLab and our payment and license provider Creem may process only the information needed to confirm paid access, such as the purchase email, license key, local installation identifier, activation identifier, and limited device status metadata.
Images are processed locally whenever possible. They are not uploaded just for Pro license validation. Pro Lifetime includes permanent access to the current Pro feature set, plus future fixes, improvements, and compatible local feature updates. Major new features or cloud-powered services may be offered separately.
Vanguard OMNI
Vanguard OMNI reads visible Amazon product page information and combines it with user-entered cost assumptions to estimate profitability, margin, ROI, and related seller analysis.
What Vanguard OMNI may process locally
- Visible Amazon product page information required for calculations
- User-entered cost assumptions and comparison values
- Local workflow settings used to keep analysis usable between sessions
Paid activation and license verification
Vanguard OMNI Pro uses license-based activation. For license validation, AuraLab and our payment and license provider Creem may process only the information needed to confirm paid access, such as the license key, a local device identifier, and an activation identifier.
Amazon credentials, browser cookies, seller account credentials, and product margin inputs are not sent as part of license activation.
RightLive Translate
RightLive Translate helps users read webpages with side-by-side translation and related language support tools.
What RightLive Translate may process
- Visible webpage text selected for translation or reading support
- Saved words, reading preferences, and related local study settings
- Local translation workflow state required for side panel or hover features
Third-party translation services
If translation features rely on third-party providers, only the text necessary for the requested translation feature should be transmitted. AuraLab does not use that product flow to request unrelated personal information.
AuraDesk
AuraDesk keeps a dedicated privacy page because its feature scope and Chrome review path are maintained separately from the other AuraLab products.
Read the dedicated AuraDesk privacy page here: AuraDesk Privacy Policy
AuraLab Website / Tools
AuraLab website pages and lightweight tools may collect basic technical information needed to render pages, deliver assets, review support requests, or understand whether a tool page is working properly.
Examples
- Basic browser or device information
- Form submissions you choose to send, such as feedback
- Minimal logs needed for security, uptime, or debugging
Feedback forms and third-party processing
If you choose to send product feedback through a linked form, AuraLab may use a third-party form service such as Tally to collect and review the information you submit. This may include your answers and any optional contact information you decide to share.
What this does not mean
- No promise of broad cross-site tracking
- No sale of personal information
- No unrelated data collection beyond what the page or tool needs
Data Security, Changes, and Contact
AuraLab applies reasonable technical and organizational measures to help protect stored information. No method of electronic storage or transmission can be guaranteed absolutely secure.
We may update this policy when product behavior changes. When we do, the date at the top of this page will be revised.
If you have privacy questions, please contact: hi@byauralab.com