TIPFLOW.SITE
Privacy Policy
What information TipFlow handles, why it is used, and how to contact us.
Last updated:
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 implementation rather than making promises on behalf of those services.
02 Information submitted in a tip
When you submit the creator form, the amount, name, email address, optional message and acknowledgement are sent to the backend to create and administer an order. The server records the creator reference, order ID, timestamp, acknowledgement time and terms version with the submitted details.
Payment references and status information are also used to confirm whether a payment was captured, failed or refunded. Do not include bank credentials, health details, identification documents or other sensitive material in the optional message field.
03 How information is used
Order information is used to create checkout, identify a transaction, show its payment status, investigate problems and respond to relevant support requests. Transaction references help match a support enquiry to the correct order.
The current integration does not include advertising analytics, sellable audience profiles or an automated marketing-email system. Sending a support enquiry is not represented as an automatic subscription to a newsletter.
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
Order records are stored in Netlify Blobs through server-side functions. A hashed access token is stored with the order; the browser uses its random session token to request that order's status. There is no public order-directory page in the current implementation.
The current browser tab uses session storage for the order reference, token, amount, currency and public checkout key. During creation it may store a hash of form details to avoid accidental duplicate requests. The site does not save the actual form contents in browser storage. Closing the tab or clearing storage may remove access to that session's recovery controls.
06 Hosting, fonts and external services
Netlify provides hosting, server functions and order storage. The homepage uses Google Fonts and icon files delivered through Cloudflare cdnjs. Razorpay's checkout script loads when the payment flow needs it.
These services may receive technical information such as your IP address, browser information and request time when your browser or the backend contacts them. Their own policies describe their processing. TipFlow does not currently include a dedicated analytics or advertising-cookie script.
07 Support correspondence and retention
If you email [email protected], the mailbox receives your email address and the contents of your message. Include only the information needed to explain your request. Support may use order references to investigate a payment concern.
The implementation does not currently have an automatic deletion schedule for stored orders or support messages. Records may remain available to administer transactions and resolve issues. Contact support if you would like to ask about information associated with your email or order.
08 Privacy requests and security
You can request information about your submitted details, ask for a correction or request deletion by contacting [email protected]. Provide enough information to identify the request without sending payment credentials. We may ask for reasonable confirmation that the request relates to you.
Security measures include server-side secrets, hashed status tokens and payment verification. No online service can promise absolute security. Protect your device, do not share session tokens and notify support if you believe information has been exposed.
09 Walkthrough previews and updates
The How to Use cards load an animated preview with fictional sample inputs. Preview mode does not create a payment order or submit the form to the live payment API. The animation is separate from the actual checkout experience.
This policy will be updated when information handling changes. The date at the top identifies this version. Review it again when using newly introduced account, creator or payment features.
Creator accounts and dashboard access
Admin-invited creator accounts include a login email, a salted password hash, creator profile, publication settings and uploaded avatar/banner images. Temporary passwords must be changed at first login. Uploaded profile images are publicly accessible; do not upload private documents.
Dashboard sign-in uses an HttpOnly session cookie with a 12-hour expiry. Server-side session records contain the account role, expiry and a hashed session reference. Password resets revoke existing creator sessions. Creators can access their own settings and supporter names, messages, amounts and statuses; administrators manage all creator accounts. These order summaries are not creator payout balances.
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.