1. App identity and business model
Public resources
Marketplace model
Bid Swipe facilitates live auctions and fixed-price purchases of physical goods. Transactions concern goods consumed outside the app. Payments are processed through a third-party payment provider; purchasing a physical item does not unlock digital app content.
Support contact: info@bidswipe.com. App review credentials, test phone numbers, one-time codes, and other secrets must be supplied privately in the applicable review console—not on this public page.
2. Apple App Store review mapping
| Review area | Bid Swipe implementation / evidence | Status |
|---|---|---|
| Privacy policy | Public policy identifies collected data, uses, service providers, retention, consent, deletion, and contact information. The same URL must appear in App Store Connect and inside the app. | Site ready |
| Account deletion | The account area must expose an in-app Delete Account action. This public page documents the path and support fallback. Deletion includes associated user-generated content except records lawfully retained. | Verify in build |
| User-generated content | Live video, listings, chat, messages, and profiles require filtering, reporting, blocking, published support contact, and timely moderation. Public standards describe the rule set. | Test all platforms |
| Physical-goods payments | Review notes should explain that Bid Swipe sells physical goods used outside the app and uses a traditional payment processor, consistent with Apple’s physical-goods exception. | Narrative ready |
| Review access | Provide a fully functional demo account, seller path, sample live show, review instructions, and any necessary verification bypass privately in App Store Connect. | Owner action |
| Brand/IP rights | Final app icon, screenshots, and listings must avoid unlicensed third-party trademarks, products, photos, and athlete likenesses. The received app icon contains recognizable brand-like imagery and should be replaced or cleared before submission. | Required |
| Data disclosures | App Privacy answers must exactly match the production SDKs and actual data flows, including payments, verification, analytics, messaging, camera, microphone, photos, contacts (if any), and location (if any). | Audit build |
Suggested App Review note: “Bid Swipe is a live marketplace for physical goods. Users browse or host live product shows, place bids, purchase physical items, and manage fulfillment. Payments relate only to physical goods consumed outside the app. Review account credentials and a preconfigured sample show are supplied in the Notes field. Reporting, blocking, moderation, privacy, and in-app account deletion are available as described in the linked reviewer resources.”
3. SMS consent and disclosures
The production app should place this disclosure directly beside the phone field and “Send code” action during sign-up, security changes, or seller verification. The user must see the disclosure before requesting the message, and Bid Swipe should store the timestamp, phone number, app version, purpose, and disclosure version as evidence of consent.
4. Twilio registration packet
Use case / campaign description
Bid Swipe sends one-time verification codes to registered users who request phone verification during account signup, account-security changes, or seller verification. These are user-initiated transactional authentication messages. No marketing content is sent under this campaign.
Message flow: how users consent
Users encounter a mobile phone field inside Bid Swipe's account signup, security, or seller-verification flow. Immediately beside the Send code action, users see: “By selecting ‘Send code,’ you agree to receive a one-time automated SMS from Bid Swipe for phone verification. Message and data rates may apply. Reply HELP for help or STOP to opt out. Consent is not a condition of purchase. See SMS Terms and Privacy Policy.” The user enters a number and affirmatively selects Send code. Bid Swipe records the consent timestamp, phone number, app version, purpose, and disclosure version, then sends one OTP. Bid Swipe does not use purchased lists, third-party leads, or unsolicited messages.
Sample message 1
Bid Swipe: Your verification code is [123456]. It expires in 10 minutes. Do not share this code. Reply STOP to opt out.
Sample message 2
Bid Swipe: Use [123456] to verify your phone for seller onboarding. Code expires in 10 minutes. Reply HELP for help or STOP to opt out.
HELP response
Bid Swipe Help: Verification texts are sent only when requested. Help at info@bidswipe.com. Message and data rates may apply. Reply STOP to opt out.
STOP response
Bid Swipe: You have opted out and will receive no further messages from this program. Reply START to opt in again or email info@bidswipe.com for help.
Campaign fields
- Use case: Authentication / 2FA
- Message frequency: On request; varies
- Embedded links: No
- Embedded phone numbers: No
- Direct lending: No
- Age-gated content: No
Consent evidence
- Store UTC timestamp and phone number
- Store screen/purpose and disclosure version
- Retain evidence until opt-out plus required legal period
- Honor Twilio’s standard STOP and HELP handling
- Never transfer, rent, sell, or share consent
5. Submission gates that still require owner or engineering verification
- Legal identity: confirm the exact legal operator name, business address, entity type, tax ID/EIN, and authorized representative. Twilio Brand Registration must match official records exactly. This site intentionally does not invent those details.
- Production URLs: move or publish these policies on the final Bid Swipe business domain before submission and use those exact URLs in App Store Connect and Twilio.
- App behavior: verify account deletion, reporting, blocking, content filtering, seller verification, payment, shipping, and support flows in the submitted iOS build.
- SDK/data audit: reconcile the Privacy Policy and App Privacy questionnaire with the exact production SDK list and data collection.
- Brand clearance: replace or obtain written rights for app icons and screenshots containing third-party trademarks or recognizable products.
- Twilio consent logs: implement the displayed disclosure verbatim or update this packet to match the final UI. Registration language and actual flow must stay consistent.
- Legal review: have qualified counsel review marketplace, auction, returns, tax, privacy, consumer, messaging, and jurisdiction-specific provisions before production launch.
6. Official platform references
This implementation summary was prepared against current public platform requirements. Reviewers and the Bid Swipe team can consult Apple’s App Review Guidelines, Apple’s account-deletion guidance, Twilio’s Messaging Policy, Twilio’s A2P registration fields, and Twilio Verify consent guidance.