Privacy Policy
Last Updated: August 8, 2026
Your data privacy is our absolute priority. This Privacy Policy details the strict technical data minimization frameworks, transient processing loops, and zero-retention security protocols engineered into AI Prescription Reader when you utilize our online medical transcription utility via https://prescriptionreader.net.
1. Transient Data Processing & Image Safety
Our application operates exclusively as a temporary data pipeline wrapper. When you upload an image of a medical prescription or capture a note using your mobile device hardware:
- The raw image file is processed entirely in transient server memory (RAM) and converted instantly into an encrypted Base64 string within your browser wrapper.
- This temporary data payload is transmitted directly via a secure proxy backend interface channel (api.php) straight to our artificial intelligence processing provider (OpenAI API).
- Zero Server Disk Storage: We do not utilize any disk database indexing infrastructure (such as MySQL) to hold medical inputs. Uploaded prescription images are never permanently or temporarily written to our local server disks or file directory caches. All records are completely destroyed in memory the split second your text translation output container completes rendering.
2. Technical Infrastructure Logging
Because our single-purpose utility does not feature user profiles, account registration portals, or client login interfaces, we only handle minimal technical operational values:
- Usage Limit Verification: We log visitor IP addresses solely to enforce our daily quota ceiling of 5 free prescription analyses per user. This transactional data value is recorded inside a highly secure local JSON tracking text file system (usage.json) and is automatically deleted by automated server cleanup routines after exactly 7 days.
- Security Abuse Prevention: We deploy Google reCAPTCHA v2 to safeguard our infrastructure from script injections and malicious automated scraping bots. This background utility checks baseline browser environments and hardware profile metrics to verify human usage.
3. Third-Party Service Providers
To deliver high-accuracy medical abbreviation decoding, our processing loops interface with specific third-party APIs under strict data handling boundaries:
- OpenAI API Framework: Text and image components are evaluated over high-security network nodes. Per OpenAI's explicit data privacy terms for API integrations, information transmitted via secure API tokens is never utilized to train future artificial intelligence models.
- Google Analytics (GA4): We deploy a custom hybrid framework utilizing cookie-less tracking configurations (Google Consent Mode v2) and strict IP address masking markers (anonymize_ip: true). This legal path records operational performance metadata (page views, interface language, country metrics) without building individualized personal profiles or tracking tracking cookies.
4. Communication and Support Data
If you voluntarily submit a message through our digital contact portal, your email address and message contents are handled strictly to respond to your technical support request. This inquiry history data is isolated from any programmatic tracking grids, is never shared with external marketing brokers, and can be purged immediately upon your explicit request.
5. Technical Data Security
We deploy secure transport layer software protocols (HTTPS/SSL encryption) across all active proxy transaction links. While we execute robust technical safeguards to isolate transient data payloads, no network transmission configuration can be guaranteed against unexpected global infrastructure anomalies.
6. International Cloud Processing
Our application programming nodes pass base64 queries asynchronously to decentralized cloud server nodes managed by our technical service providers. These computational clusters may operate outside your specific country or municipal territory of residence.
7. Your Data Protection Rights
Our application data pipelines operate on a strict data minimization model. Because we do not require account sign-ups, visitor logging, or email tracking histories, there are no user profiles, medical archives, or prescription data folders stored on our systems to export, modify, or erase.
8. Children's Data Safeguards
This software is designed as an educational and transcription optimization tool. We do not knowingly record technical or personal details from children under the age of 13. If any child submits temporary information without guardian oversight, the system automatically flushes the string payload from transient memory instantly.
9. Privacy Contact Information
If you have any questions, require formal technical documentation, or want to audit our server data data minimization frameworks, please contact our data safety administration team at:
Email Contact: support@prescriptionreader.net
10. Policy Evolution Updates
We preserve the operational right to update this Privacy Policy statement over time to adapt to evolving technical framework updates, core search engine indexing parameters, or regulatory changes.
11. Related Platform Policies
For a comprehensive understanding of our platform parameters and liability limits, please review our linked legal documentation: