Privacy Policy
Wound360 — Wound Analysis & Management | Effective date: 11 May 2026 | Last updated: 2 Oct 2026
1. Who We Are
Wound360 is developed and operated by FootSecure ("we", "us", "our"), India's phygital ecosystem and centre of excellence for foot, ankle, and wound care. As part of our clinical practice, we build AI-driven tools — including Wound360 — to support clinicians in diagnosing and managing chronic wounds at the bedside, in home care, and in the operating theatre. For questions about this policy or your data, contact us at info@footsecure.com.
2. What This App Does
Wound360 is a clinical decision-support tool for wound assessment. It enables authorised clinicians to:
- Photograph wounds at the bedside and capture clinical measurements
- Measure wound area and characterise the wound bed, peri-wound area, and wound edge, and communicate findings to the clinician
- Capture patient consent for clinical care, cloud storage, and AI-assisted analysis
- Sync clinical records securely to a cloud database accessible to their care centre
The app is a clinical decision-support tool. It is not a medical device and does not provide diagnoses or treatment recommendations.
3. Data We Collect
Patient data — entered by the clinician at the point of care:
- Name, date of birth, sex, diabetic status
- Medical Record Number (MRN)
- Optional phone number (used only for patient identity matching across care episodes — no communications sent to the patient)
- Consent record: what the patient consented to (clinical care, cloud storage, AI-assisted analysis), timestamp, and an audit hash. The audit hash is a SHA-256 token derived from the patient ID and consent timestamp — it is not biometric data or a drawn signature.
Wound assessment data — captured during assessment:
- Wound photographs (2–7 images per session, stored as WebP, resized to 1024 px maximum, watermarked with centre name, date, and time)
- Wound measurements: area, length, breadth, perimeter (derived from AI analysis; the clinician confirms all values)
- Wound characterisation: wound bed type, wound edge shape, wound edge texture, peri-wound condition (AI-assisted; clinician-confirmed)
- AI analysis metadata: model version, session identifier, confidence score (stored separately from clinician-confirmed values and never used to overwrite them)
Copy for manual upload to your organisation's record system. When a wound photograph is captured, the app also saves a copy of it to the device's shared photo storage, in a folder named "Wound360". This copy exists so the clinician can manually upload the photograph to a separate electronic medical record (EMR) system used by your organisation, which has no direct connection to Wound360. The copy is the same resized, watermarked image as the clinical copy. Its file name contains a random session code and no patient identifiers. Unlike the clinical copy, it is not stored in app-private storage and is not protected by Wound360's database encryption.
Clinician account data — managed by your organisation's administrator:
- Email address, display name, assigned role (clinician, centre head)
- Active centre assignment and session timestamps
App diagnostics — collected automatically:
- Crash reports via Firebase Crashlytics. These contain device model, OS version, app version, and crash stack trace. No patient identifiers, MRNs, names, or clinical data are ever included in crash reports.
4. How We Use the Data
| Data | Purpose | Legal basis |
|---|---|---|
| Patient demographics & MRN | Patient identification, deduplication across care episodes | Clinical care mandate of your organisation |
| Consent records | DPDP Act 2023 compliance; audit trail for data use authorisations | Legal obligation (DPDP Act 2023) |
| Wound photographs | Clinical record; AI-assisted wound measurement (where consent given) | Patient consent; clinical care |
| Wound photograph copy in device shared storage | Manual upload to your organisation's EMR system | Clinical care; clinical care mandate of your organisation |
| Wound assessments & scores | Clinical record; longitudinal wound tracking; centre-wide care coordination | Clinical care; patient consent |
| AI analysis metadata | Model performance auditing; training data improvement (only where patient has consented to AI training) | Patient consent (ai_training field on consent record) |
| Crash reports | App stability and quality improvement | Certain legitimate uses under Section 7, DPDP Act 2023 (system integrity and security response) |
5. How Data Is Stored and Protected
On the device:
- All clinical data is stored in an AES-256 encrypted database (SQLCipher). The encryption key is generated at installation and stored in Android EncryptedSharedPreferences — it never leaves the device.
- The clinical copy of each wound image is stored in app-private internal storage, inaccessible to other apps. A second copy is saved to the device's shared photo storage for manual EMR upload (see Section 3). That copy is not protected by app-private storage or database encryption, and other apps on the device that are permitted to read photos — including gallery and photo-backup apps — may be able to access it.
- Session credentials are stored in EncryptedSharedPreferences and cleared automatically after 12 hours (HIPAA session policy) or on sign-out.
- Android cloud backup is explicitly disabled for the app's own data. No clinical data is included in Android cloud backups of the app. The shared-storage photo copies described above are outside the app's control; if a device-level photo backup is enabled (for example, Google Photos backup), those copies may be included in it.
In transit:
- All communication uses TLS 1.3. Cleartext HTTP is disabled in the release app.
In the cloud:
- Clinical data is stored in Supabase (PostgreSQL), hosted on AWS ap-south-1 (India) — satisfying India data localisation requirements under the DPDP Act 2023.
- Wound images are stored in a private Supabase Storage bucket. Images are never publicly accessible; access requires a signed URL generated on demand by authorised centre staff.
- Row-Level Security (RLS) enforces strict data isolation — clinicians access only records belonging to their own centre. Patient data cannot be accessed cross-centre.
- Supabase infrastructure is AES-256 encrypted at rest.
Authentication:
- Login requires email and password verified by Supabase Auth, followed by biometric re-authentication on the device. The biometric gate is fail-closed — it never auto-approves.
- Sessions expire after 12 hours regardless of device activity (HIPAA alignment).
Internal access:
Wound360 personnel do not access clinical data as a matter of course. Support and engineering staff may access clinical data only when necessary to resolve a specific, logged support request, with access scoped to the minimum required and recorded in an access audit log. We do not use clinical data for any purpose outside those described in Section 4.
Lost or stolen devices:
Session credentials expire automatically after 12 hours or on sign-out, and clinical data is not included in device backups. Organisations should report lost or stolen devices to their administrator immediately so the affected clinician's account can be suspended, invalidating any active session on that device. Photograph copies saved to shared storage remain on the device after sign-out and session expiry, and are not removed by the app. Organisations should enforce a device screen lock and device encryption, and should disable automatic photo backup on devices used with Wound360.
6. AI-Assisted Analysis
When a patient has consented to AI-assisted analysis, wound photographs from that session are transmitted to a cloud AI inference server (hosted on AWS EC2, operated by us) for automated wound measurement. This transmission occurs in the background after the assessment is saved. Images are transmitted over TLS with an internal API key. The AI server does not retain images after analysis; results are returned to the app and stored in the clinical record alongside the clinician-confirmed values.
AI-generated measurements are clearly identified as such. Clinician-confirmed values are always authoritative — AI outputs are stored separately and never overwrite clinical data.
Where the patient has not consented to AI-assisted analysis, images are not transmitted to the inference server.
7. Data Sharing and Third Parties
| Third party | Data shared | Purpose | Location |
|---|---|---|---|
| Supabase (infrastructure) | All clinical data and images | Cloud database and storage infrastructure | AWS ap-south-1 (India) |
| AWS EC2 (operated by us) | Wound images (where consent to AI analysis given) | AI wound measurement inference | AWS (India region) |
| Google Firebase / Crashlytics | Crash reports (no PII, no clinical data) | App stability monitoring | Google Firebase — [region TBD — still open]; no clinical or patient data leaves India |
Wound360 does not itself send the shared-storage photograph copies to any third party. Any backup or sync of the device's photo storage is controlled by the device owner and is outside Wound360's control.
We do not sell patient data. We do not share clinical data with advertising networks, marketing platforms, data brokers, or any third party not listed above. Your organisation's administrator controls who within your centre can access patient records.
We will update this table and notify clinician organisations before adding or replacing any subprocessor with access to clinical data.
8. Data Retention
- On-device data: Retained until the app is uninstalled or the clinician signs out. Data for patients from other centres is evicted from the device automatically when the clinician's centre context changes. Data captured while offline is held in the encrypted on-device database until connectivity is restored, then synced to the cloud database. Unsynced data remains subject to the same on-device encryption, eviction, and session-expiry rules described above.
- Shared-storage photograph copies: Kept on the device until deleted by the clinician or your organisation. The app does not currently delete them automatically, including after sign-out or after the clinical record has synced. Organisations should delete these copies once the manual EMR upload is complete.
- Cloud data: Retained for the duration of your organisation's active licence. Retention after licence expiry is governed by your organisation's data management policy and applicable healthcare regulations.
- Crash reports: Retained by Firebase Crashlytics per Google's default retention policy (90 days).
- Export audit logs: Retained indefinitely as an immutable compliance record. Temporary export files are deleted after 15 minutes. Where a patient exercises the right to erasure, the underlying clinical record is deleted, but the export audit log entry (which does not contain clinical content) is retained to preserve the integrity of the compliance trail.
9. Your Rights Under the DPDP Act 2023 (India)
If you are a patient whose data has been collected by a clinician using Wound360, your rights under the Digital Personal Data Protection Act 2023 are exercised through your healthcare provider (the Data Fiduciary). These rights include:
- Right to access — request a summary of your personal data held
- Right to correction — request correction of inaccurate data
- Right to erasure — request deletion of your data (subject to regulatory retention obligations). Where erasure is requested, your organisation must also delete any photograph copies held in the device's shared storage; these are not removed when the clinical record is deleted
- Right to withdraw consent — consent to cloud storage or AI analysis can be withdrawn; your clinician can record the withdrawal in the app, which sets a withdrawal timestamp on your consent record
- Right to grievance redressal — contact our Grievance Officer, [name TBD — still open], at info@footsecure.com. We will acknowledge grievances within 48 hours and resolve or substantively respond within 30 days.
Consent collected in the app carries a purpose code, version number, and optional expiry date, consistent with DPDP Act 2023 requirements.
Consent Manager: Wound360 does not currently route consent through a registered Consent Manager under the DPDP Act 2023 Rules. Consent is collected and recorded directly within the app by the treating clinician.
9A. Data Breach Notification
In the event of a personal data breach, we will notify the Data Protection Board of India and affected Data Fiduciaries (your organisation) without undue delay, in accordance with the Digital Personal Data Protection Act, 2023. Your organisation is responsible for notifying affected patients as required under its own policies and applicable law. We maintain incident-response procedures to detect, contain, and report breaches, and will provide your organisation with the information needed to meet its own notification obligations.
10. HIPAA Alignment
Wound360's technical architecture — encrypted storage, encrypted transmission, automatic session expiry, audit-trail logging of data exports, and database-level access controls — is built to support use in HIPAA-covered clinical environments. This section describes technical safeguards only and is not a representation of certified HIPAA compliance. Clinician organisations using this app as part of a HIPAA-covered workflow are responsible for executing a Business Associate Agreement (BAA) with FootSecure; no BAA template is currently available. Organisations should conduct their own assessment of whether Wound360 meets their compliance obligations.
11. Children's Data
This app is intended exclusively for use by licensed healthcare professionals. It is not directed at children. Paediatric patients may be registered by their clinician as part of clinical care. Where the patient is a child under the DPDP Act 2023, consent for cloud storage and AI-assisted analysis is obtained from the patient's parent or lawful guardian by the treating clinician, and recorded on the consent record in the same manner as adult consent. Such data is handled with the same technical and organisational protections as all patient data described in this policy.
12. Changes to This Policy
We may update this policy when the app's data practices change. Material changes will be reflected in an updated effective date. Clinicians are notified of material changes through the app or by email. Continued use of the app after changes take effect constitutes acceptance of the revised policy.
13. Contact and Complaints
- Email: info@footsecure.com
- Data Fiduciary for clinical records: Your healthcare organisation
- Data Processor (app operator): FootSecure
If you believe your data has been handled in breach of the DPDP Act 2023, you may file a complaint with the Data Protection Board of India.
