Privacy Policy

01.Introduction and Scope

This Privacy Policy ("Policy") explains the privacy practices for Audify ("Audify", "we", "us", or "our"), an interactive web-based audio digital signal processing (DSP) application engineered by Nyxen in collaboration with sound curator Xpert Melody.

This Policy applies to your interaction with the Audify web application, accessible at https://audify.nyxen.in, and all associated tools, documentation, blogs, and contact dispatch endpoints.

02.Information You Provide

We receive information directly from you in two specific contexts:

03.Audio File Ingest, Memory Lifecycle, and Export

Audify is engineered to run as a client-side audio workstation. The end-to-end lifecycle of an audio file is as follows:

1. Ingestion: The browser reads selected file bytes into an ephemeral in-memory ArrayBuffer.
2. Decoding: The browser Web Audio API decodes the buffer into raw uncompressed Pulse Code Modulation (PCM) float samples (AudioBuffer) and computes visual peaks for the waveform display.
3. DSP Graph Computation: When auditioning or mastering, our audio graph executes Web Audio nodes (biquad filters, convolvers, dynamics compressors, delay lines, and stereo panners) on your local CPU.
4. Master Encoding & Download: Exported files are written by client-side encoders (WAV PCM, LAME MP3, or AIFF) directly into a local Blob and delivered via an in-memory object URL (blob:https://...).
5. Purge & Cleanup: When you click "Remove Track", load a new file, refresh the page, or close your browser tab, all allocated object URLs are revoked via URL.revokeObjectURL(), and the audio buffer is released to the browser's garbage collector.

04.Whether Audio is Processed Locally or Transmitted to Servers

In contrast, communication sent through the Contact Dispatch form (/api/contact) is transmitted securely over HTTPS (TLS encryption) directly to our server infrastructure so that our team can review and respond to your inquiry.

05.Technical Data, Server Logs, and Abuse Prevention

When you visit Audify, our edge hosting provider (Vercel) automatically receives standard technical request data necessary to deliver web assets. This includes:

• Internet Protocol (IP) address
• Browser type and version (User-Agent)
• Operating system and device platform
• Referring URL and requested page paths
• HTTP response status and timestamps

Contact Form Rate Limiting: To safeguard the contact endpoint against automated denial-of-service and spam attacks, our API server maintains an ephemeral, in-memory sliding-window bucket that limits dispatches to 5 requests per 10-minute window per client IP. IP addresses are masked in logs (e.g. 198.51.*.*) and automatically discarded after 10 minutes of inactivity.

06.Cookies, Local Storage, and Client State

Audify utilizes client-side cookies and browser localStorage exclusively for essential functionality and user interface preferences:

This table lists cookies and storage set by Audify itself. When advertising is enabled (see Section 7), third-party advertising scripts loaded in ad containers may set their own cookies or client-side identifiers independently of Audify, subject to your consent preferences and regional settings. We do not embed web analytics, session-replay scripts, or behavioral profiling tags of our own. You can adjust your consent choices at any time via the Cookie Preferences link in our footer, or directly here:

07.Third-Party Infrastructure and Content Delivery

We rely on trusted infrastructure providers to deliver Audify reliably:

• Edge Hosting & CDN (Vercel Inc.): Hosts our Next.js frontend code and executes serverless API routes on a global edge network. Vercel adheres to rigorous enterprise security standards.
• External Media Links (YouTube): Links to acoustic demonstrations, tutorials, and music tracks curated by Xpert Melody redirect to YouTube (Google LLC), where Google's independent privacy policy applies.
• Sponsor Placements (Advertising): In production environments where advertising is explicitly enabled (via the NEXT_PUBLIC_ADS_ENABLED deployment flag), banner advertisement containers marked "Advertisement" are rendered on some pages and served by a third-party advertising network (Adsterra). These placements:
  • Never receive your audio files, audio buffers, filenames, or audio metadata — audio processing is fully local and advertising code has no access to it.
  • Load third-party JavaScript from the advertiser's servers, which can observe standard browser-level information (IP address, device characteristics, referrer, cookies) plausibly needed to serve ads, as with any advertising network.
  • May cause the advertising network to set its own cookies or local identifiers for ad delivery, frequency capping, and fraud prevention; these are the vendor's processing operations and are governed by the vendor's privacy policy, not ours.
  Advertising remains disabled by default — in development, test environments, and any deployment that has not explicitly opted in. Where advertising is active, on-device privacy controls (browser ad-blockers, tracking protection, cookie clearing) apply to these third-party containers as they would to any website's ads.

08.Purposes and Lawful Bases for Processing

Under applicable data protection frameworks (such as the EU/UK General Data Protection Regulation (GDPR) and the Indian Digital Personal Data Protection Act (DPDP)), we process information under the following legal bases:

• Performance of Service: Executing DSP transformations in local memory as requested by user actions.
• Legitimate Interests: Protecting the application against abuse, diagnosing client compatibility issues, and responding to direct inquiries.
• Consent: Where required for optional non-essential cookies or analytics technologies.

09.Data Retention and Deletion Practices

• Audio Data: Retained for exactly zero seconds on any server. Exists solely in your local browser tab RAM and is erased when you close the session.
• Contact Messages: Stored securely in our support inbox only for as long as necessary to address your inquiry or technical bug report, after which messages are periodically archived and purged.
• Browser Storage: LocalStorage keys remain on your device until cleared through your browser settings or overridden by your preferences.

10.Security Measures and Architectural Limitations

We implement comprehensive technical protections: HTTPS-only delivery via modern TLS, strict Content Security Policies, client-side CPU rate limiting via look-ahead peak limiting (−0.3 dBFS ceiling) to prevent audio distortion and hardware damage, and sandboxed memory handling.

Limitations: Because audio processing runs locally inside your browser, the ultimate security of your local files depends on the security of your device, operating system, and browser extensions. We recommend keeping your web browser updated and using caution with untrusted third-party browser extensions.

11.Children's Privacy

Audify is not structured for or directed at children under the age of 13 (or under 16 in certain European jurisdictions). We do not knowingly collect personal information from children. If you believe a child has submitted personal details through our contact form, please notify us at support@nyxen.in and we will promptly delete the data.

12.Your Privacy Rights

Depending on your jurisdiction (including the European Economic Area, the United Kingdom, California, and India), you hold statutory rights regarding your personal information:

• Right to access personal information held about you.
• Right to request rectification or correction of inaccurate information.
• Right to request deletion (erasure) of personal correspondence.
• Right to object to or restrict certain types of processing.
• Right to withdraw consent at any time without affecting lawful prior processing.

Because we do not maintain user accounts or store your audio files, we cannot retrieve or supply copies of audio processed in past sessions. To exercise your rights regarding contact inquiries, email support@nyxen.in.

13.International Transfers

Static web assets (HTML, JavaScript, CSS) are served via globally distributed Content Delivery Network (CDN) edge locations. Contact submissions may be processed by edge serverless nodes located across international jurisdictions where our cloud infrastructure providers maintain operations, subject to appropriate contractual and security safeguards.

14.Policy Modifications and Contact Information

We may periodically revise this Privacy Policy to reflect technical updates, new DSP tools, or statutory changes. Any revisions will be published on this page with an updated "Last updated" timestamp.