Labels

My Privacy Policy

Contact Information

If you have any questions about this Privacy Policy, please reach out through my Contact Page. You can also learn more about me and my work on the About Page.

Services and Platforms I Use

I use a number of third-party services to create, host, manage and operate my websites, apps and online projects. These include:

  • ChatGPT: used to help develop ideas, write and troubleshoot code, and assist with projects.
  • GitHub: used to store and manage website, app and project files, including private repositories used for Android app builds.
  • FreeFlarum: used to host and customise my online community.
  • Blogger (owned by Google): used to create, customise and publish my blogs.
  • Firebase: used for authentication, Firestore databases and backend features in some of my apps.
  • Cloudflare: used for domain, DNS and related website services.
  • Zoho: used for email and business-related services.
  • Stripe: used for secure payments, donations and payment processing in supported projects.

Each third-party provider operates under its own privacy policy and terms which you can read by clicking their names above.

Android App Builder

I provide an Android App Builder that can turn an HTTPS website into a signed Android APK and Google Play AAB.

  • If a working service worker is detected, the builder uses Bubblewrap.
  • If no working service worker is detected, the builder uses a WebView Android app instead.
  • If a service worker exists but the manifest is missing or unusable, the builder can create the manifest needed for the Bubblewrap build.

GitHub Token

The Android App Builder requires a fine-grained GitHub Personal Access Token so the browser can start a private GitHub Actions workflow.

  • The token is entered by the user and is used only in the open browser tab.
  • It is not intentionally stored in localStorage by the builder.
  • It is not uploaded to or stored on a Ventsharm server.
  • The token is sent directly from the user's browser to GitHub when the GitHub API is used.
  • Users should restrict the token to their own private builder repository and give it only the minimum permissions required.

Signing Keys and GitHub Secrets

The Android signing keystore and signing passwords are stored by the user as encrypted GitHub Actions repository secrets inside their private GitHub repository.

  • The builder page does not request or upload the user's signing keystore.
  • The private GitHub Actions workflow temporarily restores the keystore during the build so the APK and AAB can be signed.
  • The signing key should never be placed in a public repository or shared publicly.

App Details and Icons

When a build is started, the website address, app name, package name, version details, appearance settings and prepared app icon are sent to the user's private GitHub Actions workflow so the Android app can be built.

The selected app icon is processed in the user's browser before being sent to GitHub as part of the private build request.

Budget Apps

Some of my budget apps use Firebase Authentication and Cloud Firestore so users can sign in and keep their own budget information synced across sessions.

  • Users may create an account using an email address and password through Firebase Authentication.
  • Budget information such as incomes, expenses, bills, subscriptions, dates, categories and related settings may be stored in Firestore under the signed-in user's account.
  • Some app data may also be cached locally on the user's device using browser storage so the app can load faster and reduce unnecessary database reads.
  • Cached local data remains on the user's device unless it is cleared by the browser, app or user.
  • I do not intentionally use budget information for advertising or sell it to third parties.

Monthly Budget App

The Monthly Budget App allows users to add and manage income and expenses, including bills and subscriptions. It can store information such as names, amounts, dates, categories, payment type and whether an item should be included in available income.

Yearly Budget App

The Yearly Budget App is designed to help users track yearly subscriptions and related costs. It may store the subscription name, amount, month and other information entered by the user.

GiftMe

GiftMe is a campaign and donation app that uses Firebase and Stripe.

  • Firebase Authentication is used for user accounts and sign-in.
  • Cloud Firestore is used to store campaign information.
  • Campaign information may include the campaign title, campaign creator name, description, image URL and custom campaign link.
  • Campaigns intended to be public may appear in a public campaign directory so other people can find and open them.
  • Stripe is used to process donations and payments securely.
  • Payment card details are handled by Stripe and are not stored directly by GiftMe.
  • GiftMe may use Stripe Connect and Stripe Checkout as part of the donation process.

Users should not include private or sensitive personal information in campaign text that is intended to be displayed publicly.

Other Apps

My other apps are not listed individually in this Privacy Policy because they do not directly collect or store personal information. Some may use cookies or similar technologies provided by the websites or services they use. The use of cookies is already explained in the Cookies section of this Privacy Policy.

Payments and Stripe

Where Stripe is used, payment information is processed by Stripe under Stripe's own privacy policy and security standards. I do not directly store full payment card details.

Depending on the project, a platform fee may be applied in addition to Stripe's own processing fees. Any applicable fees should be shown to the user as part of the relevant service or payment flow.

Firebase

Firebase services may process account information, authentication data, database records and technical information needed to provide app functionality. Firebase is provided by Google and is subject to Google's privacy terms.

GitHub and GitHub Actions

GitHub is used to host code and project files and, in the Android App Builder, to run private GitHub Actions workflows. Information submitted to a GitHub workflow is processed by GitHub according to GitHub's own privacy policy and account settings.

Cookies

What Are Cookies?

Cookies are small text files stored on your device when you visit a website. They help improve your experience by remembering preferences and collecting basic analytics or advertising information.

How My Sites Use Cookies

  • To analyse traffic and understand visitor interactions.
  • To remember preferences where supported.
  • To display advertisements through Google AdSense and, where applicable, affiliate programs.

Some cookies may be set by third-party services used on this website. The information collected depends on the provider and the user's consent and privacy settings.

If you are not comfortable with cookies, you can change your browser settings, clear stored cookies, or leave this website.

Learn more about cookies here:
Google: How Google uses cookies

Advertising and Google AdSense

This website uses Google AdSense to display advertisements.

  • Google and other advertising partners may use cookies or similar technologies to serve and measure ads.
  • Advertising may be personalised or non-personalised depending on the user's consent, location and Google advertising settings.
  • Google may use information from visits to this and other websites in accordance with its own policies.

Learn more here:
How Google uses information from sites or apps that use our services

You can manage Google advertising preferences here:

Copyright and Content Ownership

  • Images and content used on this site may be:
    • Created by me,
    • Created with the assistance of tools such as ChatGPT,
    • Used under an appropriate licence or with permission,
    • Related to Avon products, campaigns or charities where I am permitted to share them,
    • Or otherwise legally available for use.

If you are unsure about ownership or wish to request permission, please contact me through the Contact Page.

Avon

I am an independent Avon Representative and may share Avon-related links, shops, brochures, campaigns and product information.

I do not own the official Avon websites. I do own and manage my own representative pages, websites and app content where applicable.

Data Retention and Deletion

Data stored in apps is kept for as long as needed to provide the relevant feature or until the user deletes it, deletes their account, or requests deletion where applicable. Some information may remain temporarily in backups or third-party systems according to the provider's own retention policies.

Your Rights

Depending on your location, you may have rights under privacy laws such as the UK GDPR, EU GDPR, CCPA/CPRA or other applicable laws. These rights may include:

  • The right to request access to personal information.
  • The right to request correction or deletion of personal information.
  • The right to withdraw consent where processing is based on consent.
  • The right to manage cookies or personalised advertising.

To exercise any applicable rights relating to services I control, please contact me through the Contact Page.

Third-Party Services

Some information is processed directly by third-party services including Google, GitHub, Firebase, Stripe, Cloudflare, Zoho, Blogger, FreeFlarum and others. Requests relating specifically to data controlled by those providers may need to be made directly to the relevant provider.

Changes to This Privacy Policy

I may update this Privacy Policy when my websites, apps, services or legal requirements change. The latest version published on this website will apply.

Conclusion

This blog, my original apps and my original project content are owned and operated by me unless otherwise stated. Please do not copy or redistribute my original content without permission.

Thank you for visiting and supporting Ventsharm Blogs.

Back to top

Back to top