Privacy Policy

1. Overview

AuraLinter is operated by Maker Portal LLC. This policy describes the information handled by the AuraLinter iOS app, the managed AuraLinter service at https://auralinter.fly.dev, and this website. It does not govern a third-party or self-hosted backend.

2. Information We Process

• Audio and sampled video stills: recordings and imported audio are uploaded for quality analysis and enhancement. If you attach a video in Ask, the App uploads its extracted audio and up to three compact JPEG stills sampled on device for visual scene context. It does not upload the original video file.
• User content: prompts, questions, selected recording intent, optional context, feedback, and generated outputs such as answers, diagnostics, and enhancement settings.
• Service activity: run identifiers, request route, status, timestamps, model/token usage, sources, tool results, and error information needed to operate, secure, troubleshoot, and control use of the service.
• Identity and Billing: anonymous per-install identity credentials, App Attest verification data, subscription purchase state, and a usage ledger to manage allowances.
• Contact information: your name, email address, topic, and message when you use the website contact form.
• Network and device metadata: hosting providers may process IP address, user agent, request time, response status, and similar connection metadata in ordinary server and security logs.

AuraLinter does not include third-party advertising SDKs or behavioral advertising trackers, and we do not use App data for cross-app tracking.

3. How We Use Information

We use this information to provide audio diagnosis, AI-assisted recommendations, enhancement, export support, and grounded DSP answers; maintain run history and continuity; authenticate and rate-limit requests; prevent abuse; diagnose failures; respond to support requests; and improve service reliability. We do not sell personal information or use your content for advertising.

4. Storage on Your Device

The App stores project metadata and saved original, imported, and enhanced media in its private app container so projects can be reopened and exported. These files remain until you delete the project or remove the App. App preferences are stored with Apple system storage. Credentials are stored in the iOS Keychain and sent only when authenticating requests to the managed backend.

5. Managed Backend Storage and Retention

Uploaded audio is written to temporary files while it is decoded, measured, enhanced, or queued. Synchronous-session files normally expire after approximately 30 minutes; long-job files may remain for up to approximately four hours; a finished full-episode enhancement is kept for up to approximately 24 hours so the App can download it, after which it expires. Cleanup may occur later if a process is interrupted, and a service restart may remove files sooner.

Completed run records are stored in PostgreSQL and may include prompts, answers, routes, sources, diagnostics, enhancement parameters, model usage, identifiers, and timestamps. At present, these completed run records do not have an automatic deletion period. Internal model-workflow checkpoints are scheduled for shorter retention, but deleting checkpoints does not delete the completed run record.

Long-audio and staged Ask/Fix job records are also stored in PostgreSQL and may include the submitted filename, prompt, status, duration, analysis results, enhancement parameters, errors, identifiers, timestamps, and request context. For an Ask with a video attachment, that request context includes the sampled JPEG stills described above. These job records currently do not have an automatic deletion period; the associated temporary audio follows the shorter temporary-file lifecycle described above.

Identity and billing records, including per-install identities, App Attest keys, subscription accounts, and usage ledgers, are stored in PostgreSQL to authenticate requests, enforce allowances, and prevent fraud.

Operational logs may contain request identifiers, status, timing, provider errors, and network metadata. We design application logs not to record raw audio, credential values, user filenames, or local file paths, but infrastructure providers may maintain their own request and security logs under their policies.

6. Service Providers

We use service providers to operate AuraLinter:

• Fly.io hosts the managed API and PostgreSQL service and processes requests, temporary files, stored run data, and operational metadata.
• Amazon Web Services (Amazon Bedrock) processes prompts, measured audio features, relevant context, sampled video stills when attached to Ask, and tool results for AI inference. Raw audio and the original video file are not sent to Bedrock by the App's current managed workflow.
• Modal may process uploaded audio or bounded audio excerpts for speech-quality scoring, speech recognition evidence, and GPU audio enhancement when those features are enabled.
• Voyage AI processes text search queries to create embeddings used by the DSP knowledge search. It does not receive uploaded audio through that search path.
• Vercel hosts this website and its contact endpoint. Resend delivers contact-form messages to our support inbox.
• Apple operates App Store distribution, TestFlight, and purchase services under Apple's own terms and privacy policy.

These providers process information on our behalf or as independent service providers under their respective terms. We may replace a provider with a functionally similar service and will update this policy when that materially changes our practices.

7. Website Contact Form

When you contact us through auralinter.makerportal.ai, Vercel and Resend process the name, reply email, topic, and message you submit. We use it to respond to and keep a record of your inquiry; we do not add you to a marketing list solely because you contacted us.

8. Your Choices and Deletion Requests

You can delete locally saved projects in the App. Deleting the App removes its app-container data, but iOS Keychain credentials and transaction state may persist across reinstallation. To request deletion of managed-service records or a contact-form message, contact us and provide enough information to locate the record, such as relevant run or thread identifiers and an approximate date. Because AuraLinter does not yet provide a conventional user account, we may need to verify the request or may be unable to reliably identify a record from an email address alone.

9. Security

We use reasonable administrative and technical safeguards, including HTTPS for the production App-to-service connection, Keychain storage for the App credential, access controls, request limits, and restricted production configuration. No transmission or storage system is completely secure, and we cannot guarantee absolute security. Do not submit material you are not authorized to process.

10. Children's Privacy

AuraLinter is not directed to children under 13, and we do not knowingly collect personal information from children under 13. Contact us if you believe a child has submitted personal information so we can investigate and delete it where appropriate.

11. International Processing

AuraLinter and its providers may process information in the United States and other countries where they operate. Those countries may have data-protection rules that differ from those where you live.

12. Changes to This Policy

We may update this policy as the product changes. We will post the revised policy here and update the date above. Material changes apply prospectively from their stated effective date.

13. Contact

For privacy questions or requests, use our Contact page or email engineer@makersportal.com.