Austinomacros Privacy Policy
Effective date: [Insert publication date] Operated by: [Legal operator of Austinomacros — confirm full legal name] Privacy contact: support@austinomacros.com Business address: [Business address], Nigeria
Austinomacros helps you record, edit, and replay browser tasks. This policy explains the information we handle, why we use it, where it is stored, and the choices available to you.
This policy applies to Austinomacros browser extensions that link to it and to the licensing, payment, and support services described below.
1. Information we handle
Macros and automation data
When you record, import, edit, or run a macro, Austinomacros may process:
- Website addresses and navigation steps.
- Clicks, page-element selectors, and text entered into forms.
- Macro commands, filenames, and folder organisation.
- Imported CSV files and their contents.
- Extracted page content, screenshots, and saved pages.
- Playback results and error messages.
This information may contain personal or sensitive data, depending on the websites, files, and tasks you use.
Macros, imported CSV data, and preferences are stored locally in your browser profile. Screenshots, exports, and downloads are saved through your browser.
The current extension does not automatically upload your macro library, CSV files, screenshots, or extracted page content to our licensing service.
Passwords and sensitive information
Recording may capture passwords and other confidential values entered into forms.
The current version can store these values as readable text inside macros. Austinomacros does not provide a separate encrypted password vault. Exported macros may also contain these values.
Review your recordings before saving, exporting, or sharing them. Avoid recording payment-card details, recovery codes, or other information you do not want stored in a macro.
License and device-activation information
When you activate or validate a license, the extension sends our licensing service:
- Your license key.
- A randomly generated browser-profile identifier.
- The requested action, such as license validation or device activation.
We use this information to verify license status, check expiry, associate an activation with a license, and enforce device allowances.
The identifier represents a browser profile, not a hardware serial number. Using another profile or clearing extension storage may generate a new identifier.
Our hosting infrastructure also receives your IP address and standard connection information when you contact the licensing service. Server logs may contain request times, requested addresses, and response or error information.
Payment information
Payments for subscriptions and license renewals are processed through Flutterwave.
Information entered during checkout is handled by Flutterwave under its privacy policy and payment terms. The Austinomacros extension does not collect payment-card details.
Payment confirmations and transaction references received by our purchasing service may be used to fulfil purchases, administer licenses, and resolve payment enquiries.
Support information
If you contact us, we receive the information you provide, such as your email address, description of a problem, and attached screenshots or files.
Remove passwords, license keys, and unrelated personal information before sending material to support.
2. How we use information
We use information to:
- Perform the recording and automation tasks you request.
- Save and organise your macros, files, and settings.
- Validate licenses and enforce activation limits.
- Process purchases and renewals.
- Respond to support requests.
- Investigate security incidents, fraud, or misuse.
- Meet applicable legal obligations.
We limit processing to these disclosed purposes and information reasonably needed to carry them out.
The current extension does not include advertising trackers or automatically transmit product-usage analytics.
We do not sell extension user data, use it for personalised advertising, or use it to determine creditworthiness or lending eligibility.
3. Information sent to websites
A macro may enter or submit information to websites you interact with. For example, it may fill a form with values from an imported CSV file.
Those websites receive information associated with the action and handle it under their own privacy policies. A website may receive typed information before a form is submitted.
Review macros before running them, especially macros obtained from someone else. Only automate access and actions you are authorised to perform.
4. Browser permissions
Austinomacros uses browser permissions to provide its automation features.
| Permission or access | Purpose |
| Website access | Record interactions and execute supported commands on webpages. |
| Tabs and navigation | Select tabs, navigate pages, and follow macro execution. |
| Local storage | Save macros, CSV data, preferences, and license details. |
| Downloads | Save exports, screenshots, and macro-triggered downloads. |
| Web requests | Identify and handle downloads associated with macro execution. |
| Browsing-data removal | Clear cache and cookies when you explicitly request it. |
The permissions requested may differ between browser editions.
Website access supports automation across websites. It is not used to build advertising profiles or send a general browsing-history feed to Austinomacros.
5. License checks and your choices
Choosing Activate license initiates license validation and, where necessary, device activation.
The extension also checks a saved license when its license interface loads, before protected operations, and approximately every 30 seconds while automation is active.
Protected automation features require an internet connection and successful license validation. An invalid, expired, inactive, or unverifiable license prevents those features from operating.
You can:
- Stop recording or playback.
- Edit or remove saved macros.
- Restrict website permissions through your browser.
- Clear the extension’s local storage.
- Disable or uninstall the extension.
- Contact us about information held on our servers.
Restricting permissions may prevent related features from working. Disabling or uninstalling the extension stops its future requests but does not automatically delete server-side activation records.
Where consent is required, we will explain the relevant processing and request consent before it begins. A material change requiring new consent will not be authorised merely by updating this policy.
6. Service providers and sharing
Our service providers include:
- Truehost.com.ng: Hosting and related infrastructure in Nigeria.
- Flutterwave: Payment processing for purchases and renewals.
Information shared with providers is limited to what is necessary for their respective services. Their processing may also be governed by their own privacy policies and legal obligations.
Information may also be disclosed:
- To websites involved in your macro’s actions.
- To support personnel when you explicitly provide information for assistance.
- Where required by law.
- Where necessary to investigate fraud, abuse, or security threats.
We restrict human access to extension user data to your explicit permission for particular information, necessary security investigations, legal requirements, or permitted internal use of aggregated and anonymised information.
Any transfer of extension user data during a merger, acquisition, or sale of assets will follow applicable requirements, including obtaining prior explicit consent where required.
7. Limited use of extension data
Austinomacros’ use and transfer of extension user data will comply with the Chrome Web Store User Data Policy, including its Limited Use requirements.
We use extension data only for the disclosed automation features and related operational purposes. These restrictions also apply to information derived from extension data.
We do not transfer extension user data to advertising platforms, data brokers, or information resellers.
A separate agreement does not authorise processing prohibited by applicable law or browser-store policies.
8. Google accounts
The browser extension does not provide a Google OAuth connection or directly integrate with Google account APIs. The website optionally offers Google sign-in when enabled. It receives your Google account identifier, verified email address, and basic profile name to create or link your website account. Existing accounts link Google after signing in with their password. Google sign-in does not grant access to your macro library or Google files.
If you run a macro on a Google website, it interacts with that website through your browser session. Google credentials are not included in license-validation requests to Austinomacros.
Any future Google API integration will require appropriate disclosure and authorisation before account information is accessed.
9. Storage and security
Our hosting infrastructure is provided by Truehost.com.ng in Nigeria. Macros, imported CSV data, preferences, and saved license details are stored locally in your browser profile unless an action described in this policy transfers them elsewhere.
License-validation requests use HTTPS. Local extension storage does not provide a separate Austinomacros encryption layer for macros, CSV values, or license keys.
The licensing API includes license keys in request addresses. These addresses may appear in hosting or server logs and must be treated as sensitive information.
No storage or transmission method is completely secure. Protect access to your device and review files before sharing them.
Server security measures: [Insert verified access controls, logging protections, backup safeguards, and deletion procedures.]
10. Data retention
We retain information according to the following schedule:
| Information | Retention |
| Server-side license and activation records | One year from [confirm the retention starting point]. |
| Server logs | One year from creation. |
| Local macros, CSV data, and preferences | Until removed or the extension’s local storage is cleared. |
| Local license key and profile identifier | Until replaced or the extension’s local storage is cleared. |
| Exported files and downloads | Until you delete them from their saved location. |
| Support correspondence and attachments | [Specify retention period.] |
| Purchase and transaction records | [Specify retention period and any applicable legal requirements.] |
| Backups containing deleted information | [Specify maximum backup retention.] |
At the end of the applicable period, server-side information is deleted or irreversibly anonymised unless a specific legal obligation requires longer retention.
Uninstalling the extension does not delete exported files, server-side records, or information already submitted to other websites.
11. International processing
Our hosting infrastructure is located in Nigeria.
Flutterwave and its service providers may process payment-related information in other countries, as described in Flutterwave’s privacy policy.
Where international transfers require legal safeguards, we will use the applicable safeguards and provide further information on request.
12. Your privacy rights
Depending on your location and applicable law, you may have rights to:
- Access or obtain a copy of your personal information.
- Correct inaccurate information.
- Request deletion.
- Restrict or object to processing.
- Request data portability.
- Withdraw consent where processing relies on consent.
- Complain to the relevant data-protection authority.
Send requests to support@austinomacros.com.
We may request proportionate information to verify your identity. Do not send passwords or full payment-card details.
Where applicable, our legal bases include providing the service you request, consent for processing that requires it, legitimate interests in securing and administering the service where those interests do not override your rights, and compliance with legal obligations.
Withdrawing consent does not affect processing already carried out lawfully. It may prevent features that depend on the relevant information from working.
13. Children’s privacy
Austinomacros is intended for adults and is not directed to children. We do not knowingly collect children’s personal information through our licensing or support services.
If you believe a child has provided personal information to us, contact support@austinomacros.com so we can investigate and take appropriate action.
14. Changes to this policy
We will update this policy when our practices change and revise its effective date.
Material changes will be clearly disclosed. Where changes require consent, we will request it before the new processing begins.
15. Contact us
For privacy questions or requests:
Austinomacros Legal operator: [Legal operator of Austinomacros — confirm full legal name] Email: support@austinomacros.com Address: [Business address], Nigeria Website: austinomacros.com
Before publication: Complete the bracketed details and confirm that server procedures implement the stated retention and security commitments. The current extension also needs appropriate consent controls, a sensitive-data security review, and safeguards against persisting private-browsing data. Publishing this policy alone does not establish compliance or guarantee store approval.
This draft draws on Chrome’s privacy-policy requirements, Limited Use requirements, disclosure requirements, and Mozilla’s Add-on Policies.