Privacy Policy
MAi Cards is your personal second memory: you deliberately save fragments of life as memory cards, AI helps structure them, and you get them back by browsing, searching, or asking in your own words. This policy explains what we collect, why, and the choices you have.
1. Who we are
The Service is operated by Rising Future (Shenzhen) Intelligent Technology Co., Ltd. (RYS AI) under the brand MAi Cards (mai-cards.com). For privacy requests, email support@mai-cards.com or see Support.
We design MAi Cards as deliberate memory — what you choose to save — not ambient “record everything” surveillance.
2. Information we collect
2.1 Account & identity
- Guest use. You may enter without a full sign-in. We still create a server-side guest identity so your cards and chats can sync. Guests are not password accounts; if the device session is lost before you “save” a real sign-in, that guest data may become hard to recover.
- Signed-in use. Email one-time codes, an optional password, Google Sign-In, and Sign in with Apple where available. You can use your email or unique MAi handle for supported sign-in methods, and edit your handle and nickname in Settings. We process email addresses, MAi handles, nicknames, provider subject IDs, and display name/avatar when the provider supplies them. Sign-in methods that share a verified email are linked to one account. When a Google account first uses a third-party email address with MAi Cards, we require a current email code before registration or account linking.
- Account security. Optional passwords are stored as salted cryptographic hashes. We keep short-lived, purpose-bound verification records for sign-in, password recovery and sensitive account changes; stored verification codes are hashed. Email changes require proof of both the current and new mailboxes. We send security notifications for email and password changes. A change to your handle, nickname or email does not change the account that owns your memories.
- Google Sign-In on the web. When the web sign-in page shows Google's sign-in button, your browser loads the Google Identity Services library from Google. Google may receive connection and browser information and use its own cookies under its privacy policy. If you choose Google Sign-In, Google returns a signed identity credential that our server verifies to create or access your MAi Cards account. Your memory cards are not sent to Google for sign-in.
- Sessions. Auth sessions are stored so you stay signed in while active (about 30 days of inactivity ends a session; your data remains until you delete it).
- Interrupted guest account saving. To recover a guest-to-account save whose sign-in response was lost, we keep a content-free handoff record: a hash of a random attempt identifier, source account and session identifiers, the destination account identifier when a transfer committed, and its status and time. It does not contain memory cards or draft text. It cannot sign anyone in; before a browser draft moves, you must sign in again to the exact destination account.
2.2 Memory content you create
- Memory cards — the text you capture (title, body, tags), photos you deliberately attach, selected photo regions, version history (including AI-refined versions), trash state, and related metadata (timestamps, language cues for structuring).
- Chat with your memory — conversation threads, messages you send, assistant replies, and citation links to cards the answer used. When you attach a card to a sent message, we also keep its card and version identifiers and the title saved with that message. The reference does not store another copy of the card's body or photos.
- Voice input. When you use hold-to-speak, chat dictation, or card dictation, the microphone captures audio sent for speech-to-text. See §4 for how that audio is handled.
- Plan / entitlement. Whether you are on Free or VIP, and verified store or Web billing signals needed to unlock paid AI access. When Web checkout is available, we keep account-linked order, customer, transaction and subscription references, purchased plan and billing period, amount and currency, payment status, and refund or dispute records. These records let us verify access, reconcile payments, and handle billing support.
In the mobile app, you can combine text and, when image capture is available, photos in one card, with optional tags. Card dictation becomes editable text in that same draft and does not save a card by itself. Full selected photos are stored with the card; a selected region guides text extraction but does not discard the rest of the photo.
Ask AI from a card. In the mobile and web apps, Ask AI opens Chat with the version you are viewing attached to the draft. Opening it does not send a message, start an AI Chat turn, or use Chat allowance; you choose Send to ask. When you send, Chat reads the selected saved text version and sends the card's attached photos, when present, to the configured multimodal AI provider. Follow-up questions can use the same reference while it remains in the recent conversation context. Photos are processed as transient, resized whole-image inputs; stored originals are unchanged, and chat references do not retain another copy of those images. A card in Trash or missing from your account is unavailable for a new answer about that source.
2.3 Technical & usage data
- Device and app information needed to run the Service (app version, platform, locale/language preference, basic diagnostics).
- Security and reliability signals: rate limits, abuse prevention, failed request patterns, and operational logs.
- Account-linked AI usage records. For metered work such as chat turns, card structuring, and embeddings, we record the time, feature or action, provider and model route, input/output or total token counts when available, and outcome. Counts may be provider-reported, estimated, partial, or unavailable. A restricted internal administration view lets our authorized administrator review each account's usage for quota, cost, reliability, support, and abuse investigations. The view does not show memory cards, chat messages, prompts, search queries, voice transcripts, or AI answers. We do not use these records for advertising profiles.
- On-device aligned card cache. Current cards and opaque synchronization / result-receipt metadata may be kept on the device for fast browsing and word search. They are bound to the exact signed-in identity and session. Logging out, switching account, or linking a guest into a real account clears or replaces the prior local identity’s cache; this does not delete its server data.
- Mobile capture recovery. Ordinary unfinished editing is not automatically saved across app restarts. After you choose Done for a card with photos, we retain the submitted text, tags, prepared photo copies, and save-recovery information in private app storage. This lets the app complete or recover that same save after a restart or uncertain network result. These records belong to the exact local account and session; they do not sync through MAi Cards to another device. Clearing them removes the app's prepared copies, not originals in your photo library. Device backups may retain app data according to your operating system and backup settings.
- Web browser storage. At app.mai-cards.com, an account-bound card cache, Direct Search history, and unsent text or image drafts may be kept in your browser's IndexedDB. We clear the prior identity's local data on sign-out, completed account linking, and account deletion. If guest account saving is interrupted, we keep its unsent drafts and local recovery record while the result is uncertain. You can download a readable copy of those local unsent text and image drafts, keep that guest's browser data, or separately confirm erasing that guest's local drafts, cached data, and recovery record without changing another account. A download contains no saved server cards; permanent account deletion does not restore server memories. These local records do not sync to another device (saved cards still sync through the server). This browser data is not encrypted by the app; someone with access to your browser profile may read it. Sign out on a shared computer. Language and theme preferences use simpler browser storage.
- Web session cookie. The web app uses an authentication cookie marked HttpOnly, Secure, and SameSite=Lax; page JavaScript cannot read it. We do not use advertising or third-party analytics cookies in the web app. Paddle checkout uses its own browser technologies as described in §4.
- Direct Search history. Searches you intentionally submit (or use to open a result) may be kept only on that device, newest-first, deduplicated, and capped at 10. This history is device-bound, excluded from backup / device transfer, and is never synced to our servers. You can clear it in Search; logout, account switch, and guest-to-real linking clear it for the prior identity.
- Content-free Direct Search operations data. We may retain provider cost/attempt status, monotonic Search-session timing and outcome buckets, request disposition, and at most one verified result-open success. These records and their retention contain no query text, selected tags, card/result content, card/version/result identifiers, or result receipts.
2.4 Support
If you email us, we receive the content of your message and any contact details you include.
3. How we use information
- Provide the product — store and sync your cards and chats; show only your data (every query is scoped to your account).
- AI structuring — after you save a card, models may generate a title, tidied body, and tags as a new version, without erasing what you originally wrote.
- Recall & chat — embeddings and search over your cards so you can find memories by meaning; the assistant answers questions about your saved life from your cards and shows citations. Casual conversation may use general knowledge but is not presented as a saved memory.
- Direct Card Search — find and open your current cards without generating an answer. Exact word search can run from the latest aligned device cache; when meaning search is available, the query is sent transiently through our server to the configured embedding provider and used to rank your own current cards. Query text and selected tags are not written to Direct Search history or analytics on our servers.
- Speech recognition — turn spoken words into text so you can talk to your memory.
- Accounts, security, and quotas — authenticate you, prevent abuse, administer Free daily AI budgets and VIP access, and review account-linked AI usage for cost, reliability, and support.
- Payments — process and restore in-app subscriptions via the app stores and our entitlement partner; when Web checkout is available, process and reconcile Web purchases, renewals, cancellations, refunds and disputes through Paddle.
- Support and legal — respond to requests and meet lawful obligations.
We do not sell your personal information. We do not use your memory cards to train public third-party foundation models for the general public. Capture (saving a card) does not wait on AI and is never blocked by the AI quota.
4. Voice, AI, and third-party processors
To run MAi Cards we use infrastructure and model providers. Important ones today include:
- Application hosting & database — Railway hosts the application, and Neon provides managed PostgreSQL for accounts, cards, chats, and entitlements (the authoritative copy of this data is on the server).
- Card photos — when image uploads are available, full photos and derived previews are stored in a private Railway Bucket. The app uses short-lived, individually signed links for uploads and viewing; stored objects are not public. We do not keep an independent backup copy of those photo files. If the Bucket irrecoverably loses them, restoring the database cannot restore the photos.
- Cache / rate limiting — shared Redis-style infrastructure for sessions, quotas, and abuse protection.
-
Speech-to-text: Alibaba Cloud (DashScope). Voice
audio is relayed through our servers to DashScope for transcription
(e.g. Paraformer). Product rules:
- Audio is relayed for recognition, not kept as a permanent voice library in MAi Cards.
- Transcript text is not written to operational logs.
- Before your first voice session, the app shows a consent sheet that names this processor and links here. Consent is remembered on the device. You can stop voice use by turning off the microphone permission in system Settings.
- AI models & embeddings (e.g. via DashScope / Qwen family and config-routed models) — structure cards, embed card text for semantic recall, transiently embed a Direct Search meaning query, refine saved text and attached photos together, and power chat, including attached photos from a card reference when you send a question or a follow-up. Model choice is configuration-driven and may change for quality or cost without changing this policy’s core purposes.
- Sign-in providers — Apple, Google, and email delivery for one-time codes.
- Payments — the Apple App Store and RevenueCat for current iOS subscriptions and restore. When Web checkout is available, Paddle is the authorised reseller and merchant of record for Web subscriptions, handling payment processing, recurring billing, tax, receipts and refunds under its Buyer Terms and Privacy Notice. Opening Web checkout or a payment-method update loads Paddle's library and payment interface. Paddle may receive connection and browser information, checkout references, and contact, billing and payment details you provide. Paddle handles full payment-card details; we do not store them. We send content-free payment references needed to link an order to its MAi Cards account, not your memory cards, photos or chat messages. Changing a receipt email does not transfer that order or subscription to another MAi Cards account. Google Play billing is not part of the current launch path.
These processors receive only what is needed for their function, under their terms and our configuration. They are not a free pass for others to browse your memory: the product’s rule is that memory answers about your life are built from your cards, with citations where applicable.
5. Ownership isolation
Every card and conversation belongs to exactly one account (guest or signed-in). The Service is designed so one user cannot query another user’s memory. That isolation is a core product rule, not a marketing slogan.
6. Where data is stored & international users
We use managed cloud providers. Our launch application database is in Neon’s US East region, and the private Railway card-photo Bucket is in US West. Other providers may process data in other regions where they operate. The product’s launch focus is global (including English and overseas Chinese users); mainland China regulatory filings are a later, deliberate phase. If you are in the EEA, UK, or similar jurisdictions, international transfers may apply; contact us for details about your rights.
7. Retention
- Account, cards, version history, and chats are kept while your account is active so the product can work as long-term memory.
- A former MAi handle is reserved for 90 days after a change. A handle retained during account-deletion recovery is reserved for 90 days after permanent deletion; the reservation then has no account owner. This prevents immediate reuse of a recently used account identifier.
- Verification codes expire after five minutes. Background cleanup removes expired proof records and short-lived mailbox integrity metadata. The latter uses a deterministic mailbox digest and an integrity counter; it can still be linked to a guessed email address and is not treated as anonymous information. A vacant-mailbox record becomes eligible for cleanup after one hour when no unexpired proof needs it. Security-notification delivery records expire after seven days or are removed earlier after delivery. Cleanup failures can delay physical removal. Owner-bound verification and notification records are removed with permanent account deletion; vacant-mailbox integrity metadata follows the one-hour cleanup rule above.
- Cards you delete go to Trash first (recoverable); “Delete forever” is the irreversible step. Stored photo removal may complete through a background cleanup after permanent card or account deletion. Automatic purge of old trash may be added later.
- Permanently deleting a card does not delete existing conversations. A sent card reference keeps its title and card/version identifiers as an unavailable placeholder; previously sent messages and assistant replies remain in the conversation. Permanently deleting your account removes its chats and reference metadata under the account-deletion process below.
- Voice audio is not retained as a permanent archive (see §4).
- Mobile photo-save recovery records and prepared photo copies are retained while a save needs recovery. They are cleared after the app confirms the save outcome, or when the app clears that local account's data on logout, account change, an account-linking attempt, or account deletion. Browser drafts likewise remain until confirmed save or their applicable local-data cleanup. An uncertain photo-save result keeps recovery material available until that cleanup; these rules do not delete source photos from your device library.
- Account-linked AI usage records remain while the account is active and are removed when that account is permanently deleted. Separate security or billing records may be retained where needed for law, fraud prevention, or accounting, as described below.
- A committed guest-account handoff record remains while its destination account exists, so an interrupted browser can verify where its cards went; deleting that account removes the record. A cancelled attempt's record is removed with its source guest.
- Direct Search session / cost / verified-open records are content-free as described in §2.3. An unfinished Search session is automatically finalized as interrupted after 24 hours; retaining its operational record does not add query, tag, card, result, or receipt content.
- Device-only Direct Search history remains until you clear it, the app clears the prior exact identity on logout/account change/link, or the app is removed. It is not backed up or synced.
- You can request account deletion in Settings. A saved account is disabled immediately, with 30 days to sign back in and recover it; after that, permanent erasure is scheduled. Guest data is erased immediately, without a recovery period. Limited records may be retained where needed for law, security, fraud, or accounting (e.g. store transaction references and Web payment, refund, dispute and billing-stop records). Web billing records retain their original purchase owner for reconciliation; a late payment is not transferred to a new account. Deletion requests start a durable Web billing-stop process, which may need retries before Paddle confirms the stop. Recovering an account does not resume Web charges, and deleting a MAi Cards account does not erase records that Paddle must independently keep.
- Earlier prototype accounts, cards, and photos are not imported into the new launch service. Any content still held in those earlier systems remains separate from new accounts; contact support@mai-cards.com to ask about access or deletion of earlier content.
8. Your choices & rights
- Edit cards; move them to Trash; delete forever from Trash.
- Delete individual chat conversations in the app.
- Upgrade a guest by signing in so you can recover the account later.
- Sign out (Settings) if you have a real sign-in method.
- Revoke microphone permission to stop voice features.
- Manage Google / Apple account permissions with those providers.
- Cancel or manage your current iOS VIP subscription in your Apple account settings; use Restore purchases in the iOS app if you reinstall.
- For a Web subscription, use the available management actions on your signed-in VIP page, the subscription link in Paddle's receipt, or Paddle buyer support. Contact MAi Cards support if you cannot access the original purchase account or a management action is unavailable.
- Request access, correction, export, or deletion of personal data by emailing support@mai-cards.com (or use Settings to delete your account or guest data).
Depending on where you live, you may have rights under GDPR, UK GDPR, CCPA/CPRA, or similar laws. Contact us to exercise them. We will not discriminate against you for exercising privacy rights.
9. Children
MAi Cards is not directed to children under 13 (or the minimum digital consent age in your country). We do not knowingly collect personal information from children. If you believe a child has used the Service and provided personal data, contact us and we will take appropriate steps.
10. Security
We use industry-standard measures such as HTTPS, authenticated sessions, and user-scoped data access. No method of transmission or storage is perfect. Protect your device with a passcode and treat email/Apple/Google access as the keys to your memory.
11. No advertising tracking by us for ads
The product’s purpose is your memory, not ad targeting. We do not run a third-party advertising network inside the app for selling your card content. App store platforms may have their own analytics or purchase tooling under their policies.
12. Changes
We may update this policy as features ship (for example image capture or new processors). We will post the new version here and update the “Last updated” date. Material changes may also be highlighted in the app when appropriate.
13. Contact
Privacy questions: support@mai-cards.com · Support · Terms of Use.
This policy is written to match how MAi Cards actually works today (product rules in our internal product-spec). It is provided for transparency and store compliance; it is not formal legal advice. Have counsel review for your entity, fundraising, or regulated markets.