ConnectVault — Closed Beta Tester Guide

You're testing ConnectVault — an AI-powered networking app where ARIA, your AI agent, helps you scan business cards, remember who you met, and follow up like a pro.

You're seeing this build before everyone else. We expect rough edges. Your feedback directly shapes the launch.

Looking for the full feature manual? Email us and we'll send the long-form one. This page is the short, ruthless version for testers.

You received an invitation from Google Play with the subject "You've been invited to test ConnectVault.ai".

1. Open the email on your Android phone (not laptop).
2. Tap Accept invitation.
3. You'll be redirected to the Play Store. Tap Install.

If the install link doesn't work: sign into the Play Store with the same Google account the invite was sent to, wait 5–10 minutes, then try play.google.com/apps/testing/ai.connectvault.app. Still stuck? Reply to the invitation email.

iOS isn't in this beta. Android only.

1. Open the app — splash screen then login.
2. Sign up with email, Google, or LinkedIn.
3. Complete ARIA onboarding (5–7 questions).
4. Tap the camera button and scan any business card.
5. Wait 5–10 seconds for OCR, then tap Save contact.
6. Open Settings → Send Feedback — confirm the form opens.

If any step fails, stop and report it before continuing. That's a P0 bug.

This is the release candidate. Five recent areas need focused attention:

3.1 Plus plan billing

Settings → Upgrade → tap Plus card → Subscribe.
Expected: Razorpay payment sheet opens with payment methods visible.
Don't enter real payment unless you're ready to subscribe — see §6.

3.2 INR / UPI (India testers)

On Upgrade screen, look for the ₹ INR · UPI toggle next to $ USD.
Expected on Indian devices: INR pre-selected, prices show ₹499 / ₹1499.
Expected when subscribing with INR: Razorpay sheet shows UPI as a payment method.
If UPI doesn't appear when INR is selected → that's a P1 bug.

3.3 Delete Account

Settings → Account → Delete Account.
Expected: a full-page screen with retention disclosure + DELETE confirmation input.
Don't actually tap delete unless you want your test account gone. Tap Cancel.

3.4 Card scanning — email accuracy

Scan 5+ cards, especially ones with first.last@company.com-style emails.
Expected: extracted email is valid and saveable.
If the extracted email has a space inside the @-local part, that's a P1 bug.

3.5 Quota — fresh account first contact

Sign up a brand new account, immediately scan + save a contact.
Expected: contact saves cleanly the first time.
If you get "Quota exceeded" on a brand new account's first contact, that's a P0 bug.

Beyond v1.0.2-specific items, use the app like you'd use a networking app. Real cards, real conversations with ARIA, real follow-ups. Synthetic tests miss bugs.

High-priority scenarios:

• Scan a card at a real event — camera focus, OCR accuracy, dedup with existing contacts
• Talk to ARIA — "Who did I meet at <event>?", "Draft a follow-up to <name>"
• Trigger morning briefing — reflects your recent activity?
• Record a 2–3 min meeting — transcription completes in 30–60s
• Import contacts (Settings → Integrations → LinkedIn)
• Edit a contact — tags, notes, company — verify it persists
• Log out + log back in — data intact?
• Use on slow Wi-Fi or 2G — reveals UX bugs
• Try airplane mode briefly — polite errors or crash?

Edge cases worth specifically trying:

• Card with handwritten annotations
• Card with text in a non-English language
• Damaged or crumpled card
• Save a contact with only a phone number (no name, no email)
• Subscribe twice to the same plan (idempotency)
• Cancel a sub, then resubscribe (state recovery)
• Send ARIA a 1000+ char message

Don't report these as bugs (we know):

• iOS — not in this beta
• Teams plan "coming soon" toast — intentional
• "Restore Purchases" toast — stubbed
• "Save QR to Gallery" toast — stubbed
• Razorpay direct (not Play Billing) — intentional during beta

We've made this fast so you'll actually do it.

Path A — In-app (preferred)

1. Shake your phone anywhere → opens Feedback pre-filled with screen context, or Settings → Send Feedback
2. Pick a type — Bug, Crash, Feature, General
3. Pick a severity:
   • Sev-1 Critical — data loss, can't use the app, payment broken
   • Sev-2 Major — important feature broken
   • Sev-3 Minor — annoying but workable
   • Sev-4 Suggestion — polish, not a real bug
4. Short title like "Scan crashes on Pixel 7"
5. Description, steps to reproduce, expected vs actual
6. Tap Send

Device info (OS, model, app version, locale) is captured automatically. You don't need to type it.

Path B — Email

Email hello@connectvault.ai with subject [Beta v1.0.2] <short summary>. Include device model, Android version, what you were doing, screenshots if possible.

When in doubt about severity, err on the side of higher — we'd rather triage Sev-2 down to Sev-3 than miss a real bug.

This build talks to live Razorpay. If you subscribe, you will actually be billed.

To test without paying:

• Stop at the Razorpay sheet (don't submit payment)
• Or subscribe + immediately cancel from Settings → Manage Subscription
• Refunds for unintended beta-testing charges processed within 5 business days — email us

If you intentionally subscribe to test the full flow end-to-end, save your invoice and email us so we can verify state.

Same guarantees as production.

• Your data is yours. Export anytime: Settings → Export My Data
• Delete anytime: Settings → Account → Delete Account. 30-day grace, then permanent.
• We don't sell your data, ever.
• Card scans encrypted in S3. OCR via Mistral + OpenAI.
• During beta, engineering may inspect anonymised error logs. We do not access your contacts/scans/messages unless you attach them to a feedback report.

Full policy: connectvault.ai/privacy.

Closed testing is where we want your most rigorous feedback. Once we promote to open testing the bar shifts to polish.