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.

About This Privacy Policy

This Privacy Policy explains how information may be handled across my websites, apps and online projects, including Ventsharm Blogs and supported Ventsharm services. Different services use different features, so not every section will apply to every website or app.

I do not sell personal information.

Services and Platforms I Use

I use 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 and to provide GitHub Actions for Android App Builder builds.
• FreeFlarum: used to host and customise my online community.
• Blogger: a Google service used to create, customise and publish my blogs.
• Firebase: used for authentication, Firestore databases and backend features in some 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.
• Google AdSense: used to display advertising where applicable.

These providers operate under their own privacy policies and terms. You can read their privacy information by clicking their names above.

Information I May Process

The information processed depends on the service you use. It may include information you provide directly, such as an email address, app or campaign information, budget information or other details required to provide a feature. Technical information may also be processed by the third-party platforms used to operate my websites and apps.

Android App Builder

The Android App Builder allows users to create signed Android APK and Google Play AAB files from HTTPS websites. Builds are performed through the user's own private GitHub repository and GitHub Actions account.

To use the builder, the user provides a fine-grained GitHub Personal Access Token. The token is used within the current browser session to communicate directly with GitHub and access the private builder repository selected by the user. The GitHub token is not stored by the App Builder, in localStorage, or on a Ventsharm server.

The user's Android signing keystore and signing passwords are managed through secrets in the user's own private GitHub repository. If the keystore-to-Base64 tool is used, the selected keystore is processed locally in the user's browser. The keystore and generated Base64 text are not uploaded to or stored by Ventsharm.

Information needed to create the app, such as the website address, app name, package name, version information, appearance settings and prepared app icon, is sent directly to GitHub as part of the user's private build request. GitHub processes the build and stores workflow information and build artifacts according to the user's GitHub account, repository settings and GitHub's own policies.

The user's private repository and the apps produced through it remain under the user's control. Ventsharm does not automatically publish, submit or distribute apps created with the builder to Google Play or another app store.

Users are responsible for the websites, content and branding they choose to use with the builder and for ensuring that apps they create comply with applicable laws, permissions and the requirements of any platform where they choose to distribute them.

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 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 may 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 helps 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 content that is intended to be displayed publicly.

Other Apps

My other apps are not listed individually in this Privacy Policy where they do not directly collect or store personal information. Some apps may display or interact with websites and third-party services that use cookies or similar technologies. Those services may process information under their own privacy policies.

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 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. For the Android App Builder, users use their own GitHub account and private builder repository. Android builds run through GitHub Actions in that repository. Information sent to GitHub is processed according to GitHub's privacy policy and the user's GitHub account and repository settings.

Cookies

What Are Cookies?

Cookies are small text files stored on your device when you visit a website. They may be used to provide website functionality, remember preferences, measure usage and support advertising.

How My Sites May Use Cookies

• To provide and maintain website features.
• To analyse traffic and understand visitor interactions where analytics are used.
• To remember preferences where supported.
• To display advertisements through Google AdSense and, where applicable, support affiliate services.

Some cookies and similar technologies may be provided directly by third-party services. Their use depends on the service, your location, consent choices and browser or account settings.

You can manage or delete cookies through your browser settings.

Learn more about Google's use of cookies here:
Google: How Google uses cookies

Advertising and Google AdSense

Some of my websites may use Google AdSense to display advertisements.

• Google and advertising partners may use cookies or similar technologies to serve and measure ads.
• Advertising may be personalised or non-personalised depending on consent, location and Google advertising settings.
• Google may process information from visits to websites or apps that use its services 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:
Google Ad Settings

Copyright and Content Ownership

Images and content used across my projects 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

Information stored in services I control is kept for as long as reasonably needed to provide the relevant feature, meet applicable requirements, or until the user deletes the information or their account where those options are available. Information processed by third-party providers may be retained according to those providers' own policies.

For Android App Builder builds, GitHub controls the retention of workflow runs, logs and build artifacts created in the user's own repository. Users can manage these through their own GitHub account and repository.

Security

I use appropriate services and security features to help protect information used by my websites and apps. Users are also responsible for keeping their passwords, GitHub tokens, signing keys and other account credentials private. No internet-based service can guarantee absolute security.

Your Rights

Depending on your location and the circumstances, applicable privacy laws may give you rights relating to your personal information. These may include rights to request access, correction or deletion, object to or restrict certain processing, withdraw consent where processing is based on consent, and manage cookies or personalised advertising.

To make a privacy request relating to information or services I control, please use my Contact Page. Requests relating to information controlled directly by a third-party provider may need to be made to that provider.

Third-Party Links and Services

My websites and apps may contain links to or use services provided by third parties. I do not control the privacy practices of those third parties. Services including Google, GitHub, Firebase, Stripe, Cloudflare, Zoho, Blogger and FreeFlarum process information according to their own policies where applicable.

Changes to This Privacy Policy

I may update this Privacy Policy when my websites, apps, services, third-party providers 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.