Who is responsible for your information
Revenue Peek is operated by Josh Mead, who is responsible for personal information handled through this website and support service. This policy covers the Revenue Peek app, its widgets and www.revenuepeek.com. For questions or privacy requests, email support@revenuepeek.com.
Privacy at a glance
You do not need a Revenue Peek account. The app connects directly to Stripe, calculates earnings on your device and stores your restricted API key in Apple Keychain. We do not operate a server that receives your key or earnings data. Website analytics and emails you send to support are separate from the app.
Your Stripe key and payment activity
You supply a restricted Stripe API key with Balance read access. The app and widget use this key to request balance transactions directly from Stripe over HTTPS. Stripe receives the key for authentication, the requested currency and date range, and technical connection information such as your IP address. Stripe handles those requests under its own privacy policy.
The app processes transaction information, including amounts, fees, currency, dates and transaction categories, to calculate your totals. It stores a summary for the widget rather than a copy of your full transaction history. Your key and these financial responses are not sent to us or to the website’s analytics service.
The key is held in a device-only Keychain item shared by the app and its widget. Revenue Peek does not sync it through iCloud or provide a cloud backup. Connecting another device requires a separate setup.
What stays on your device
Revenue Peek saves your account label, settlement currency, selected period, net or gross preference, appearance and latest earnings summary. The summary includes totals, daily amounts, refresh time and whether the data is from Stripe test mode. The app and widget share this information using local storage provided by the operating system. Your API key is stored separately in Keychain.
The app contains no advertising or third-party analytics SDK. Earnings are visible wherever you add a widget, so consider who can see your screen or screenshots.
Disconnecting and deleting information
Choose Disconnect Stripe in the app to remove its saved Keychain credential and cached earnings summary and stop future Stripe refreshes. Preferences such as your account label, currency, period and appearance remain on your device. You can clear your custom label in settings.
Disconnecting does not revoke the key at Stripe or delete records from your Stripe account. To revoke access using that key, delete or revoke it in your Stripe Dashboard.
Do not rely on uninstalling the app to erase the saved key or all preferences. The operating system can retain Keychain items or other app data after an app is removed. Disconnect before uninstalling if you want Revenue Peek to remove its saved credential. We cannot remotely access or delete information stored only on your device.
App Store purchases and diagnostics
Apple processes downloads, payments, refunds and purchase history. We do not receive your payment card details. Apple may make sales reports and app diagnostics available to developers, subject to its services and your sharing settings. See Apple’s privacy policy for how Apple handles that information.
Website analytics
We use analytics services to understand how visitors find and use this website. These services use cookies and process information such as pages visited, referring pages, browser and device information, approximate location and IP address. Website analytics do not receive your Stripe key or the earnings stored by the app.
You can manage or block cookies through your browser settings. Blocking analytics does not affect the Revenue Peek app.
Website delivery
Vercel hosts this website. Hosting and security services process technical request information, such as IP address, requested URL, browser information and request time, to deliver pages, diagnose problems and protect the website. Pages also load an icon library from the UNPKG content delivery service, which receives the information needed to serve that request. See Vercel’s privacy notice.
Following a link to Stripe, Apple or another website opens a service with its own privacy practices. Opening Help, Privacy or Terms from the app opens this website, where the website practices in this policy apply.
Contacting support
If you email us, we receive your email address, message and any attachments you choose to send. We use these to respond, investigate issues and maintain relevant support records. Our email provider processes messages to deliver and store that correspondence.
Please do not send API keys, payment card details or unredacted customer information. Remove sensitive information from screenshots and diagnostic material before sharing them.
Why we use information
Where data protection law requires a legal basis, we rely on providing our contract with you for app support, our legitimate interests for running and securing the website and handling enquiries, and legal obligations for records we must retain. Optional analytics are subject to applicable consent requirements.
We do not sell personal information or use your app’s financial data for advertising. We do not use personal information to make automated decisions that have legal or similarly significant effects on you.
Sharing and international processing
Information is handled by the services described above where needed to provide the app, website and support. We may also disclose information if required by law or necessary to establish or defend legal claims. We do not share your local Stripe credential or earnings with those providers through our own systems.
Website and support providers may process information outside your country. Where applicable, international transfers require safeguards recognised by relevant data protection law. You can contact us for information about the providers and safeguards relevant to your request.
How long information is kept
The app replaces its saved earnings summary as it refreshes. The key and latest summary remain locally until you disconnect; preferences remain until changed or removed. Data retained in backups or by the operating system is subject to your device and backup settings.
Support correspondence is kept for as long as needed to resolve your enquiry, provide follow-up support and meet any legal or record-keeping obligations. Website analytics and technical records are subject to the relevant provider’s retention settings and our need to understand usage, investigate problems and protect the service. We assess retention by the purpose of the record, whether an issue remains open and any applicable legal obligations. Contact us to request deletion of personal information we control.
Your privacy rights
Depending on where you live, you may have rights to access, correct or delete personal information, receive a portable copy, restrict its use or object to processing based on legitimate interests. Where processing relies on consent, you can withdraw it without affecting the lawfulness of earlier processing. You may also complain to your local data protection authority.
Send requests to support@revenuepeek.com. We may ask for enough information to verify and fulfil your request. We cannot retrieve information that remains solely on your device; use the local controls described above. Requests about records held independently by Apple or Stripe should be directed to those services.
Security
Revenue Peek uses HTTPS for Stripe requests, restricted API access and Apple Keychain for credentials. Keeping financial processing on your device limits the information we receive. No system can guarantee absolute security; protect access to your device and revoke a Stripe key if you believe it has been exposed.
Children
Revenue Peek is intended for people managing a business or Stripe account, not children under 13. We do not knowingly collect personal information from children under 13. Contact us if you believe a child has supplied personal information to our support service or website.
Changes to this policy
We will update this page and its revision date when our practices change. Where required, we will provide additional notice of significant changes.