MakerPing

Privacy

Updated 8 October 2026.

MakerPing is a private dashboard operated by Very Interesting for its account owners. It brings together reports from the services and accounts that the owner chooses to connect.

Accounts and recovery

Member account emails are encrypted in the central account registry, and passwords are stored as salted hashes. Each member has a separate private workspace. When you request account recovery, Cloudflare Email Service processes your registered email address and a single-use link valid for thirty minutes. The delivery queue stores the link encrypted and clears it after sending, use, expiry or permanent delivery failure. Link hashes and delivery metadata are retained for up to thirty-two days to enforce abuse limits. Email content previews are disabled. Resetting a password invalidates the member’s existing sessions and agent access. The personal recovery code remains an alternative.

Signing in with Google or GitHub

If you choose Google or GitHub to sign in or create an account, MakerPing requests only your account identity and email address. Google uses the openid and email permissions; GitHub uses user:email. MakerPing keeps a pseudonymized provider identifier and an encrypted verified email to recognize the linked account. Sign-in tokens are used during verification and are not stored. These permissions are separate from any social reporting connections. You can add or remove a sign-in method in Settings, after confirming your identity. At least one method must remain linked to your account.

Connected social accounts

With your authorization, MakerPing reads your account identity, public publication links and aggregate counters such as views, likes, comments, shares and followers. It uses these reports to show changes over time and associate publications with a project. It does not post, follow people or read private messages. Missing provider data stays unknown.

Storage and access

Social reports, account profiles and provider access tokens are stored encrypted in Cloudflare D1 or an isolated Cloudflare SQLite workspace. Only authenticated access to the private dashboard and authorized agents can read reports. Tokens are used to refresh authorized reports and are not displayed in dashboard responses. Cloudflare also processes connection information to deliver and secure the service. MakerPing does not sell account information or use it for advertising.

Disconnecting and deleting data

You can disconnect a source in the dashboard and revoke authorization in the provider's account settings. Disconnecting stops collection. Existing Instagram and TikTok reports remain available to the account owner until removed by the administrator. YouTube API account data is removed on disconnection; cumulative API snapshots are retained for up to thirty days. Contact the administrator of your MakerPing account to request removal of stored reports.

Other reports

The dashboard also stores the sales, store download and financial reports explicitly connected or imported by the owner. Payment services remain responsible for processing transactions. MakerPing does not handle card payments.

Website statistics

For websites explicitly connected by an account owner, MakerPing stores daily aggregate page views and store link clicks for configured public pages and broad source categories. The measurement script does not use cookies or persistent browser storage. Counters contain no visitor identifier, IP address, full referrer or full browsing URL. The script respects Do Not Track and Global Privacy Control; owners can also configure it to wait for their website’s consent signal. These measures cannot identify an individual download or purchase. Cloudflare processes connection information to deliver and secure collection requests.

Custom events

Account owners can connect their websites, apps and server tools to send named business events and small properties. Properties are encrypted and read only in the private event detail; they do not appear in notifications or daily counters. Event details and deduplication IDs are retained for up to ninety days, with routine cleanup; daily aggregate counts and event definitions remain available. The browser client uses no cookies, persistent storage or visitor identifier, respects Do Not Track and Global Privacy Control, and can wait for the website’s consent signal. Owners should send no personal contacts, secrets or private URLs. Public ingestion identifiers cannot read account data. Cloudflare processes connection information to deliver and secure these requests.

Terms of use

Public website and beta requests

The public MakerPing website offers a beta request form. We store your email in encrypted form, your optional project count, the date of the request and your permission to receive a reply about the beta. Requests are retained for up to 90 days. A private removal link is provided after submission; save it to remove your request at any time. Sending a request does not create a MakerPing account or guarantee access.

The form is hosted on Cloudflare with a separate database in the European Union. We use a keyed hash of the request IP address for abuse prevention, with rate-limit records kept for at most two days. The intake does not store the raw IP address. Cloudflare processes network information to serve and protect the website.

Google Analytics is optional and loads only after you choose “Allow analytics”. It measures visits and successful beta requests on the public homepage. We do not send your email, form contents, account identifiers, project names, revenues or private app activity to Google Analytics. Page addresses sent to analytics exclude query parameters and fragments. Advertising storage, Google signals and advertising personalization are disabled. Analytics is also disabled when your browser sends Do Not Track or Global Privacy Control.

Your choice is saved locally for six months. Use “Analytics preferences” in the homepage footer to change it. Declining disables future measurement and removes the analytics cookies accessible to the website. Google describes its processing at How Google uses information from sites that use its services.