Privacy Policy

1. About This Policy

This Privacy Policy explains what personal data MySafeCard ("we", "us", "our") collects from users of the MySafeCard mobile application (Android and iOS) and website (mysafecard.in), how that data is used, stored, and protected, and what rights you have over your data.

By using MySafeCard, you agree to the practices described in this policy. If you do not agree, please uninstall the app and discontinue use of the service.

2. Google Play Data Safety Summary

The following table summarises the data types MySafeCard collects, consistent with the Data Safety declaration in the Google Play Store listing.

3. Medical Disclaimer — Not a Medical Device

MySafeCard is a personal information-sharing application. It is not a medical device, diagnostic tool, clinical decision support tool, or medical advice service. It has not been evaluated, cleared, or approved by the Central Drugs Standard Control Organisation (CDSCO), the US Food and Drug Administration (FDA), or any other regulatory body as a medical device.

The health information displayed on your emergency card is entered entirely by you. MySafeCard does not verify, validate, interpret, or endorse any health information you enter. You are solely responsible for ensuring the accuracy and completeness of your card information.

In any medical emergency, always call emergency services first (dial 112 in India). Do not delay calling emergency services because of this app.

4. Information We Collect

Account data: Your email address, used for authentication and transactional emails. If you sign in with Google, we receive your email and display name — no other Google data is accessed.

Emergency card data (entered by you): Name, date of birth, gender, nationality, blood group, allergies, medical conditions, current medications, doctor name and contact, hospital details, emergency contact name(s), phone number(s), and relationship(s). An optional profile photo.

Emergency contact approval data: When you send an emergency contact an approval request, a record is created containing: the contact's name, phone number, and relationship; your name as card owner; a unique approval token; request status (pending / approved / declined); and timestamps. This record expires after 30 days.

Physical card order data: Delivery name, address, phone number, email, Razorpay payment ID, and order amount — used for printing, shipping, payment verification, and GST invoicing. Your medical information is used only to generate the card artwork and is not retained in billing or invoice records. Razorpay additionally collects payment instrument details (card numbers, UPI IDs, etc.) directly from you; MySafeCard never receives or stores these.

Consent record: When you create an account, we record your acceptance of our Terms of Service and Privacy Policy. The record includes: your user ID, email, date and time of acceptance, version of terms accepted, device platform, and sign-in method. See Section 18A for details.

Push notification token: A Firebase Cloud Messaging (FCM) device token, used to send completion reminders after activating a physical card code.

What we do NOT collect: Your location, device identifiers, browsing history, contacts, calendar, or any data not explicitly listed above.

5. How We Handle Sensitive Health Data

Your card contains sensitive personal health information. This data is stored solely on Google Firebase (Firestore) and is used for one purpose: to display your emergency card to people who access it via your card's link, QR code, or NFC tag.

We do not use your health data for advertising, profiling, research, AI/ML training, or any purpose other than displaying your card. No third party ever receives your health data.

By creating a card, you understand that the information you submit is publicly accessible to anyone who has your card URL (including emergency responders and bystanders). You are solely responsible for the accuracy and appropriateness of the information you choose to include.

6. Authentication and Sign-In Methods

MySafeCard supports four sign-in methods:

• Email and password: Managed by Firebase Authentication. Passwords are never stored in plain text by MySafeCard.
• Email OTP (one-time password): A 6-digit code sent to your email via Amazon SES. Codes expire after 10 minutes and are single-use. The code record is deleted from Firestore after successful verification.
• Magic link: A single-use sign-in link sent to your email via Amazon SES. Links expire after 1 hour. The link record is deleted from Firestore after use or expiry.
• Google Sign-In: Handled by Google's OAuth 2.0 service. We receive only your email address and display name. No other Google account data is accessed or stored.

No authentication credentials (passwords, OTP codes, or magic link tokens) are stored by MySafeCard beyond the minimum retention period required for operation.

7. Emergency Contact Approvals

When you add an emergency contact to your card, you may send them an approval request so they can consent to being listed. This feature works as follows:

• A unique, unguessable 32-character token is generated and stored in Firestore as an approval record.
• The record contains: the contact's name, phone number, relationship to you, your name as card owner, the request status, and timestamps.
• An approval link is shared with the contact (via SMS, WhatsApp, or any channel you choose). The contact does not need a MySafeCard account to approve or decline.
• Approval records expire after 30 days and become inactive regardless of action taken.
• The contact's response (approved / declined / no action) is visible only to you as the card owner.

By sending an approval request, you confirm that you have the contact's permission to share their name and phone number with MySafeCard for this purpose, and that the phone number you provide belongs to them.

8. Card Deletion — What Is Removed

When you delete a card, all personal and medical data associated with it — name, photo, blood group, allergies, conditions, medications, emergency contacts, doctor details, and all other fields — is permanently and immediately erased from Firestore. This deletion is irreversible.

What is retained after deletion: the card's unique document ID (a short random identifier that forms the card's URL), containing only status, deletion date, and your user ID — no medical data. This is retained solely to ensure your physical NFC tag continues to point to a valid URL (so a scanner sees "card not found" rather than an error). You may reuse the same physical tag for a new card at any time.

9. Local Device Storage (AsyncStorage)

MySafeCard stores small amounts of data locally on your device using React Native AsyncStorage. This data never leaves your device and is not transmitted to our servers. Local storage is used for:

• Rate limiting: Redemption attempt counts (max 5 per 15 minutes) — prevents code-guessing abuse. Stored locally only, never sent to servers.
• UI preferences: Whether you have seen the NFC setup guide (so we don't show it again).
• Environment preference: Staging vs. production environment selection for testing (developer use only; has no effect on end users).

Uninstalling the app removes all locally stored data.

10. Photos and Camera Access

You may optionally add a photo to your card and profile. Photos are compressed and stored as base64-encoded data directly in Firebase Firestore — they are not uploaded to any external image host or CDN. Card photos are reduced to approximately 400×400 pixels; profile photos to approximately 200×200 pixels before storage.

On Android, camera and photo library permissions are requested only at the moment you tap the photo button — not in the background. Only the specific photo you select is accessed; no bulk gallery scan occurs. You can deny these permissions at any time in device Settings; doing so only disables the photo feature.

11. Device Permissions

• Camera — To take a new photo for your card or profile. Requested only when you tap the photo button. Never used in the background.
• Photo Library / Media Storage — To select an existing photo from your gallery. Requested only when you tap the photo button. Never used in the background.
• NFC — To write your card's URL to a physical NFC sticker or tag. Requested only when you initiate an NFC write operation. No data other than your card URL is written to the NFC chip.

No permission is requested in the background or without a direct action by you. Denying any permission disables only the specific feature it relates to — all other app features continue to work.

12. NFC Usage

When you write your card to an NFC tag, only your card's web address (URL) is written to the physical chip — no personal or medical data is stored on the NFC tag itself. The URL simply directs a scanner's browser to our web page, where your card data is fetched from Firebase. Writing to an NFC tag is entirely optional.

13. Push Notifications

MySafeCard may send push notifications to remind you to complete your emergency card profile after activating a physical card redemption code. To deliver notifications, we store your Firebase Cloud Messaging (FCM) device token and device platform (Android or iOS). No personal or medical data is included in notification payloads. You can disable notifications at any time in device Settings; your FCM token is removed from our servers when you delete your account.

14. Email Communications

MySafeCard sends transactional emails only — no marketing or promotional emails. Transactional emails include: account verification OTP codes, magic link sign-in emails, welcome messages on registration, activation codes for physical card orders, and card completion reminders. All emails are sent via Amazon Simple Email Service (AWS SES). Your email address and name are shared with AWS SES solely for delivery. AWS SES does not receive your medical or health data.

15. Data Storage and Security

All cloud data is stored on Google Firebase (Firestore and Authentication), which encrypts data at rest and in transit using industry-standard TLS. Firebase is certified under ISO 27001, SOC 1, SOC 2, and SOC 3. Account passwords are managed by Firebase Authentication and are never stored in plain text by MySafeCard. Access to Firestore is governed by Firestore Security Rules that allow users to read and write only their own data.

16. Third-Party Services

MySafeCard uses the following third-party services:

• Google Firebase (Firestore, Authentication, Cloud Functions, Hosting) — Core infrastructure. Stores your account and card data. Governed by Google's Terms of Service and Data Processing Addendum.
• Google Sign-In (OAuth 2.0) — Optional authentication. We receive only your email and display name. Governed by Google's Privacy Policy.
• Firebase Cloud Messaging (FCM) — Push notification delivery. Your device token is shared with Google for notification delivery only.
• Google Firebase Analytics — App performance and usage analytics (Android only). Collects: screen views, key in-app actions (login method, signup, card creation/update/deletion, NFC tag write, card sharing, order initiated/completed/cancelled, promo code usage, emergency contact approval sent, physical card code redemption, profile updates), device model, OS version, app version, country-level location, and session data. No health, medical, or personally identifiable data is sent to Firebase Analytics. Your Firebase user ID is linked to analytics events to allow per-user analysis but is not shared with any other third party. You can opt out of analytics collection by uninstalling the app. Governed by Google's Privacy Policy.
• Amazon Web Services — Simple Email Service (SES) — Transactional email delivery. Your email address and name are shared solely for email delivery. AWS does not receive your medical data. Governed by the AWS Data Processing Addendum.
• Razorpay — Payment gateway for physical card orders. Razorpay processes payment instrument data (card numbers, UPI IDs, net banking credentials) directly and securely. MySafeCard receives only: the Razorpay order ID, payment ID, and payment status. Razorpay is PCI-DSS compliant and operates under its own Privacy Policy. Razorpay does not receive your medical or health data.

We do not sell, rent, trade, or share your personal information with any party beyond what is described above. No third-party service receives your health or medical data.

17. Data Retention

Your card data is retained for as long as your account is active. Deleted card data is immediately and permanently erased (only the URL shell is retained — see Section 8). When you delete your account, all cards, photos, profile data, push notification tokens, and approval records are permanently deleted.

Physical card order data (delivery name, address, phone number, email, and order details) is retained for invoicing and legal compliance. GST invoices are kept for a minimum of 7 years as required under Indian tax law. Delivery and shipping details are removed from active systems within 60 days of confirmed delivery.

Emergency contact approval records expire after 30 days. OTP codes expire after 10 minutes. Magic links expire after 1 hour.

18. Your Rights and Account Deletion

You have the right to access, correct, or delete your data at any time. You can edit or delete any card directly within the app.

To permanently delete your account, email us at support@mysafecard.in with the subject line "Account Deletion Request" from your registered email address. We will process the request within 7 business days and confirm once complete. Account deletion is irreversible and removes all cards, profile data, photos, push notification tokens, and approval records. GST invoice records are retained as required by law.

19. Children's Privacy

MySafeCard is not directed at children under the age of 13. We do not knowingly collect personal information from children under 13. Users between the ages of 13 and 18 must have parental or guardian consent before creating an account. If you believe a child under 13 has provided us with information without parental consent, contact support@mysafecard.in and we will delete it promptly.

18A. Consent Recording

When you create a MySafeCard account or sign in for the first time using Google Sign-In, we record your acceptance of our Terms of Service and Privacy Policy. For email registrations, we also record your acceptance of the medical data declaration.

The consent record contains: your Firebase user ID, email address, the date and time of acceptance (UTC), the version of the Terms and Privacy Policy you accepted (identified by their effective date), your device platform (web, Android, or iOS), and your sign-in method (email or Google). We do not record your IP address.

This record is stored securely in Firebase Firestore under your user account and is retained for the lifetime of your account plus a minimum of 7 years after account deletion, as required for legal compliance. You may request a copy of your consent record at any time by emailing support@mysafecard.in. The consent record is not deleted when you delete your MySafeCard account; it is retained solely for legal compliance.

20. Changes to This Policy

We may update this Privacy Policy from time to time. The "Last updated" date at the top reflects the most recent revision. We will notify you of material changes via in-app notification or email. Continued use of the app after changes constitutes acceptance of the updated policy.

21. Contact Us

For privacy-related questions, data deletion requests, or to exercise your data rights:

Email: support@mysafecard.in
Website: mysafecard.in
MySafeCard, Hyderabad, Telangana, India