Privacy Policy
What information TipFlow handles, why it is used, and how to contact us.
Last updated:
On this page
01 Scope of this policy
This policy covers information handled through tipflow.site, creator tipping pages and authenticated admin and creator dashboards. It also explains the difference between the animated walkthrough, the live form and payment-provider checkout.
Third-party services have their own privacy practices. Links to a provider's policy are provided where relevant; this page describes TipFlow's data practices rather than making promises on behalf of those services.
02 Information submitted in a tip
We collect the amount, name, email address, optional message and acknowledgement you submit, along with transaction references and dates. We use these records to process tips, confirm payment status and help with support requests. Do not include bank credentials, health details or identification documents in your message.
03 How information is used
We use the information you submit to process tips, show payment status, resolve issues and answer support requests. We do not use tip details for advertising profiles or automatically subscribe supporters to marketing emails.
04 Razorpay and payment details
Razorpay checkout receives payment information needed to process your selected payment method. The TipFlow form does not ask you to enter full card numbers, bank passwords, OTPs or UPI PINs.
TipFlow receives provider references and payment status to verify the result. Name and email can be passed to checkout as prefilled contact details. Razorpay's separate privacy policy explains its handling of information through its services.
05 Storage and session recovery
We retain transaction records to administer payments and support requests. Your browser temporarily stores payment session information so you can check the result or recover an interrupted checkout. Closing the tab or clearing browser storage may remove these recovery controls. Actual form contents are not saved in browser storage.
06 Service providers
We use Netlify for hosting and storage, Razorpay for payments, and Google Fonts and Cloudflare cdnjs for website assets. These providers may receive technical data such as IP address and browser information to deliver their services. Waitlist entries are submitted through Google Forms. Their privacy policies also apply.
07 Support correspondence and retention
When you email support, we receive your email address and message. Transaction and support records are retained as needed to administer payments, resolve issues and meet applicable requirements. There is no automatic deletion schedule. Contact us about access, correction or deletion.
08 Privacy requests and security
You can request information, corrections or deletion by contacting [email protected]. We may ask you to confirm that the information relates to you. We use access controls and payment verification to protect records. No online service can promise absolute security; keep private links and account credentials confidential.
09 Previews and updates
Homepage previews use fictional sample information and do not transfer money. We update this policy when our information handling changes.
Creator accounts
We store account contact details, securely protected login information, creator profiles, page settings and uploaded images. Published profile images are public. Creators can review their own supporter names, messages, amounts and payment statuses; authorized administrators manage accounts and support requests. Account sessions use cookies to keep you signed in.
Livestream tip alerts
If a creator enables their overlay, a confirmed paid tip can display your supporter name, message and amount on their livestream. Do not submit private information you would not want shown publicly. The tip acknowledgement explains this possibility before payment.
The creator configures a custom sound, volume and duration. Uploaded sounds are publicly served media. A private, revocable source token authorizes the overlay feed; it does not authorize dashboard access or expose supporter email addresses. Alert records are stored with the payment order for duplicate prevention.