Who we are
Spikely is made by Prince Ajuzie.
Spikely is an app for iPhone, iPad, Mac and Apple Watch, with a service at www.spikelyapp.com, built by Prince Ajuzie. It reads the numbers in tools you connect, learns what normal looks like, and alerts you when something moves. This policy covers the apps, the website and the service behind them.
Your account
Your sign-in name, email and photo.
You sign in with Apple or Google. We receive an account identifier, your email address and, when the provider shares them, your name and profile photo. With Apple's Hide My Email, we only see the relay address Apple gives us.
Tools you connect
Read-only keys, encrypted with their own key each.
To read a platform such as Stripe, Polar, Paddle, Lemon Squeezy, Dodo Payments, RevenueCat or Vercel, you give Spikely a key from it. Spikely asks for read-only access and checks a key's permissions before saving it.
With cloud watching on, the default, the key is encrypted on our servers so Spikely can check your numbers while the app is closed. Every key is sealed with its own random encryption key that only opens for the connection it belongs to. A copy stays in your device's Keychain. With cloud watching off, keys live only in your Keychain and are removed from our servers.
Instant alerts
One webhook, only if you allow it, removed when you disconnect.
If you give a key permission to manage webhooks, Spikely creates a single webhook named “Spikely (instant alerts)” in that account, so the platform tells Spikely the moment a sale, refund, cancellation or deploy happens. That webhook only sends events to Spikely. It can't change your products, prices, customers or payouts. Disconnecting the source, turning cloud watching off or deleting your account removes it.
Google Analytics
Read-only Analytics reports, used only to show and alert on your numbers.
When you connect Google Analytics, you sign in with Google and allow one permission: “See your Google Analytics data” (analytics.readonly). Spikely uses it to list the properties you can see and to read report totals: users, sessions, views and key events, by hour and by day. It doesn't read your Gmail, Drive, contacts or anything else in your Google account, and it can't change your Analytics settings or reports.
Google gives Spikely a refresh token, which is encrypted on our servers like any other key. You can remove access at any time from your Google Account under Security, Third-party connections, or by disconnecting Google Analytics in Spikely.
Spikely's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use Google data only to provide the features you see in Spikely. We don't sell it, use it for advertising, use it to train AI models, or let people read it, except with your permission, for security, or where the law requires.
What we store
Totals by the hour, plus a 30-day activity feed.
To show your numbers and alert you, Spikely stores:
- Hourly and daily totals for the metrics it watches, such as revenue, MRR, sales, subscriptions, refunds, visitors and users, converted to US dollars where they're money.
- The moves it detects, and short notes about what changed around them.
- An activity feed of individual events for 30 days: the kind of event, its amount, and the product, customer name or commit message the platform includes, so a push can say “New sale · Pastely Pro”. Older events are deleted automatically.
- Your projects, logos, alert settings, rules and widget designs, so they follow you across devices.
- Each device's push token, timezone and app version, so alerts reach it and quiet hours use your local time.
What we never do
No selling, no ads, no tracking you across apps.
We don't sell your data, show ads, build advertising profiles, or share your data with anyone for their own use. We don't store payment card details or full customer lists from the tools you connect.
Services we rely on
Only what's needed to run Spikely.
Spikely runs on cloud hosting with a hosted database. Project logos are stored with Cloudinary. Sign-in uses Apple and Google. Alerts are delivered through Apple Push Notification service. Daily exchange rates come from ExchangeRate-API and involve none of your data. The website uses privacy-friendly Vercel Analytics. These providers process data only to run their part of Spikely.
App analytics
Privacy-first usage counts, with no cookies or personal data.
The apps use Aptabase, a privacy-first analytics service, to count how Spikely is used, such as which screens are opened, when setup is finished or when something goes wrong. Each event carries the app version, the operating system and a rough location, the country and region, worked out from the network address, which itself is never stored. There are no cookies, no device or advertising identifiers and no personal data: never your name, email, account, keys, project names or numbers. Events are grouped only by short sessions, so they can't be tied back to you or followed across apps. We use them only to improve Spikely.
The apps also send the same usage events to TelemetryDeck, a privacy-focused analytics service built for Apple apps. When you're signed in, your internal account id is turned into a one-way hash on your device before it's sent, so TelemetryDeck never sees the id itself, let alone your name or email. It gives us counts like active users, app versions and how many people finish setup.
Product analytics and session replay
PostHog shows us where Spikely works and where it doesn't.
The website and the apps use PostHog to see how Spikely is used and where it goes wrong. It records events such as pages and screens opened and buttons tapped, with the browser or device, app version and a rough location worked out from the network address. In the apps, events are linked to your account by an internal account id only, never your name or email. Website visitors stay anonymous.
Session replay records how a page or screen was used, so we can see a problem the way you saw it. Text fields and secrets such as keys are masked on your device before anything is sent, and the numbers you check in the website's tools aren't recorded. App replays can show Spikely's screens, including numbers from your connected sources. Recordings are visible only to Spikely and used only to fix problems and improve the product. They're never sold or used for ads.
On the website, PostHog keeps a first-party cookie and a little local storage to recognise a returning visit and hold a session together. It isn't used to follow you across other sites.
Security
Encrypted keys, signed webhooks, least access.
Keys and tokens are encrypted at rest with per-secret keys. Traffic is encrypted in transit. Every incoming webhook must carry a valid signature from its platform or it's rejected. Spikely asks each platform for the least access it needs.
Your choices and deleting data
Disconnect anything, or delete it all from Settings.
Disconnecting a source deletes its key from our servers and your device, and removes Spikely's webhook from that account. Deleting your account in Settings deletes everything above from our servers: your account, projects, connections, keys, numbers, events, alerts, rules, widgets and devices. If you signed in with Apple, it also revokes Spikely's access to your Apple ID.
Children
Spikely isn't for children.
Spikely is made for people running a business and isn't directed at children under 13.
Contact
Write to princeajuzie1@gmail.com.
Questions or requests about your data go to princeajuzie1@gmail.com, and you'll hear back from the person who built Spikely. If this policy changes, the date at the top changes with it.


