RecipeMeter Support

Last updated: 2026-07-25 · Bundle ID: ai.arcanforge.recipemeteraa69

Share product feedback

Tell us what worked, what blocked you, and whether you would miss RecipeMeter if it disappeared.

Open feedback form

First value check

Try the product promise before installing

This no-cost check turns organic visitors into measurable intent without paid traffic. Choose the problem that matches you, then open the tracked product path.

When would this matter?

What should happen first

  • Can the page explain the first action: save one recipe with a visible limit receipt?
  • Can the app produce a concrete result: The user sees remaining quota, expected recipe value, and paid unlock proof before the recipe task starts?
  • Does the problem repeat: before each recipe-saving or cooking session?
  • Would paid value be clear after one session: Frequent cooks pay when unlimited receipts, widgets, and export packs keep paid recipe decisions clear before every cooking session?

Measurement rule

The support page captures only organic intent; it does not synthesize installs, trials, paid users, revenue, retention, or PMF answers.

Organic discovery proof

What RecipeMeter is built to prove

Target user: home cooks who save recipes and compare paid cooking tools before paying or cooking

Core pain: Recipe paywalls, quota limits, and unclear paid upgrades make cooks waste time or money before knowing whether a recipe is worth starting.

Positioning wedge: Own a narrow workflow instead of a broad commodity category.

Aha moment

save one recipe with a visible limit receipt within 7 day(s), 2 time(s). The user sees remaining quota, expected recipe value, and paid unlock proof before the recipe task starts.

Recurring value

before each recipe-saving or cooking session Expected frequency: 8+ / month. Retention metric: D30 repeat recipe value receipt rate

Why someone would pay

Frequent cooks pay when unlimited receipts, widgets, and export packs keep paid recipe decisions clear before every cooking session.

  • unlimited recipe value receipts
  • saved history and widgets
  • export packs for repeated cooking decisions

Search intents and ASO wedge

recipe paywall, recipe limits, cooking subscription value

  • Recipe Meter — one clear next action
  • recipe paywall
  • recipe limits
  • cooking subscription value
  • App Store Food & Drink search wedge
  • recipe paywall complaint
  • Recipe paywalls
  • quota limits
  • and unclear paid upgrades make cooks waste time or money before knowing whether a recipe is worth starting.

Organic channels

  • App Store Food & Drink search wedge
  • recipe paywall complaint pages

Referral loop

Saved recipe value receipts are shareable as decision proof when cooks compare paid recipe tools.

Organic operating system

Core growth loops

  1. App Store search intentOwn narrow pain-led ASO keywords before any paid channel is allowed.
  2. Public proof pagesPublish crawlable static pages that explain the acute problem, Aha action, and proof loop.
  3. Community answer loopAnswer real problem threads and route only relevant traffic through tracked organic links.
  4. Product-led sharingMake the user outcome shareable so referrals come from the product, not ads.

Organic priority stack

  1. 1. crawlable static surfaceShip a static, no-JS-required support/proof page with canonical URL, meta description, semantic HTML, and JSON-LD.
  2. 2. aso keyword wedgeTranslate the acute pain and Aha action into long-tail App Store keywords and metadata tests.
  3. 3. community answer distributionUse public/community answer paths only where the exact problem is already being discussed.
  4. 4. referral share artifactExpose one clear share artifact tied to the Aha result and track referral landings.
  5. 5. pmf review feedback loopCollect PMF, review, paywall-exit, and churn reasons immediately after real use.
  6. 6. organic cc decision loopJudge kill/iterate/scale with organic impressions, installs, activation, trial, paid, retention, and carrying capacity.

Email support

For account, billing, bug, or accessibility help, email support@arcanforge.ai.

Include these details when they apply:

Billing and subscriptions

How do I cancel a subscription?
Open Settings > Apple ID > Subscriptions on your iPhone, choose RecipeMeter, then tap Cancel Subscription. The subscription remains active until the current billing period ends.
How do I request a refund?
Apple handles App Store refunds. Visit reportaproblem.apple.com, sign in with the Apple ID used for purchase, and choose RecipeMeter. We can explain the product behavior by email, but Apple decides refund eligibility.
Why was I charged after cancelling?
Apple renews subscriptions before the period ends. If cancellation happened after renewal processing started, the next charge may still complete and the subscription ends on the following renewal date.

Data and privacy

How do I delete app data?
Delete RecipeMeter from the device to remove local app data. If the app writes to Apple system stores such as Health, Calendar, Reminders, or Files, remove those records from the relevant Apple app or system settings.
Does support need my personal data?
No. Send only the details needed to debug the issue. Avoid passwords, payment card numbers, Apple ID credentials, health records, or other sensitive information.

Product feedback

The feedback form is the fastest path for product decisions because it records structured PMF and churn signals for RecipeMeter.

Open the RecipeMeter feedback form.

Try, share, or explain why you stopped

These links are tracked only as organic product signals. They do not create synthetic installs, revenue, or survey answers.

Legal