By Balance IT · Updated
The media you choose stays local.
Audio files are played and analyzed by your browser. Selected artwork is decoded on your device. The application does not upload your audio, artwork, generated frames or recorded video to PHASE//VOID or Balance IT.
When you connect a microphone or audio interface, the browser asks for permission. When you choose shared tab or system audio, its sharing picker controls what is available. The application uses the returned audio; it does not place the shared screen image in your visual output or recording.
Video recording combines the generated canvas and audio on your device. A completed recording is temporarily available in the page for preview and download. There is no cloud library or automatic upload. Save your downloads before closing or reloading the page.
Your original audio and artwork files are not modified by the visualizer. The application does not send them to an AI service.
Settings can stay in this browser.
The studio uses local storage to remember scene controls, output choices, title/subtitle text, saved visual presets, show sequences with cue names and settings, projection maps with surface names, corners, crops, masks, source choices, looks and surface effects, favorites, named world banks (names and member IDs), and MIDI mappings (target, Note or CC, channel and number). This storage belongs to the current browser and site. It is not an account or a cloud backup.
Raw audio and artwork are not included in remembered settings or a saved session settings file. If you reopen a session, select those media files again. Titles, cue names, bank names and map-surface names you type can remain in local settings until replaced or cleared. Map JSON and session settings preserve geometry, Program/independent source choices, looks and surface effects rather than media bytes; calibration patterns are runtime-only and do not restart after a reload.
Use header menu → Save session to download settings you want to keep. Use Set banks → Export banks for a separate portable copy of favorites and world banks; session files do not include these lists. Clearing this site's browser data removes its locally remembered settings, banks, favorites and presets. Your previously downloaded files remain on your device until you delete them.
MIDI is optional.
The studio requests MIDI access only after you press Connect MIDI. Your browser controls permission and may remember an earlier decision. Web MIDI access can expose available input and output device information such as names, manufacturers and IDs. PHASE//VOID uses one selected input, sends no MIDI output, and requests no SysEx access.
Device information is used in memory to display inputs and manage the connection. Device IDs and names, permission, connection state and received message values are not included in local storage or downloaded session files. Portable mappings contain only the studio target, message kind, channel and control number. The app does not upload mappings or MIDI messages.
Disconnect MIDI stops the app listening; browser permission remains under your browser settings. Use Remove or Clear all in MIDI controls to delete saved mappings. Reloading or importing a session never reconnects MIDI automatically.
An AI assistant connection is optional.
If you connect a compatible assistant to the public PHASE//VOID MCP endpoint, that client sends bounded text protocol requests to Cloudflare. The endpoint returns public scene descriptions, capabilities and studio links. It does not accept a song, artwork, exported video or session file, and it has no access to the private code repository or the media you select in Studio.
PHASE//VOID does not put MCP request text into its first-party event counts. Normal hosting request metadata can still apply. Your assistant provider handles the prompt you give it under its own settings and policy; avoid putting sensitive personal information into scene-search text.
Loading a website still makes requests.
The site is served through Cloudflare. Loading the page, scripts, fonts and scene images sends normal web requests to the hosting network. Request metadata can include your IP address, requested URL, time and browser information for delivery, reliability and security.
This is separate from selected media processing: opening your own audio file in the studio does not send that file to Cloudflare. If you press Play original WAV from a techno example, your browser downloads that public 4.6 MB test file from Cloudflare; it does not upload your own audio. Hosting-level security features may process request information or use necessary mechanisms independently of the application.
The application includes no advertising pixels, third-party analytics SDK, account system or marketing subscription form. For Cloudflare's handling of service data, see Cloudflare's Privacy Policy.
PHASE//VOID sends a small first-party event request when you click a homepage start action, open either guided Studio flow, open the projector window, open the studio from a guide or video watch page, first activate a file, live input or demo in a tab, request a video download, generate a custom-visuals brief or click to open an email draft. If you reach the homepage with Product Hunt's exact ref=producthunt marker, it counts that homepage arrival. It separately counts a marked studio arrival and the first successful audio activation there, if they happen. The event request contains only a fixed action name and a fixed page or guide category. The server adds the UTC day and app version to a countable event in Cloudflare Analytics Engine. It does not include your IP address, browser details, referral URL, audio source, audio, file name, scene, artwork, video, project name, brief or email address as analytics fields. There is no visitor ID or analytics cookie. These per-page-load counts are not unique visitors, a joined conversion funnel or proof that a real visitor came from Product Hunt; the link marker can be copied. Normal hosting request metadata still applies to this request. If the analytics service is unavailable, the action continues and that count is lost. A homepage click does not prove the studio loaded or audio started. Opening the live flow does not prove an input connected; opening a projector window does not prove a second display was used. A download request does not prove the file finished saving, and clicking an email-draft link does not prove a message was sent.
The MP3/WAV guide path separately counts its marked Studio arrival, a successful public sample start and a successful own-file start. Playing a public test does not count as using your own file. These are independent aggregate milestones without a visitor identifier; they cannot reconstruct an individual journey. The Studio URL can contain the intentionally chosen public sample and frame, which normal hosting requests receive.
The homepage project builder separately counts reaching the setup summary, the first rendered preview with audio, copying a settings link and clicking through to Studio. A marked Studio arrival and its first successful audio activation are counted separately. These fixed-label counts do not include search text or selected settings, and are not joined into individual journeys. Shared links contain public choices such as purpose, world, frame, size and motion; anyone receiving the link and normal hosting requests can read those choices. The link contains no music, artwork, titles or media bytes. Opening a configuration link does not start audio or grant microphone or tab-sharing permission.
The one-projector planner separately counts a requested map download, a copied setup link and a Studio click. A marked Studio arrival, first successful audio activation and explicit application of a starter map have separate fixed-label counts. They do not contain layout choices, world IDs, geometry, private surface names or media. They cannot reconstruct an individual journey or establish physical projection. Setup URLs contain public starter choices and are readable by their recipients and normal hosting requests; manually edited maps are saved locally, not embedded in those starter links.
The public scene catalog counts the first successful audio-reactive preview and clicks that open Studio. A from=scenes link marker separately counts a Studio arrival and its first successful audio activation. These are fixed labels without a scene ID, audio name, visitor ID or session identifier; counts cannot be joined into a per-person conversion rate. The catalog preview plays only original browser-generated demo sound after a click and does not request your files or microphone.
The embed builder counts successful copies of its iframe code. Each embedded player counts its first successful audio start per page load, including when displayed on another website. These events contain fixed labels only: no host URL, scene ID, selected file name or visitor identifier is sent as an analytics field. The player loads public assets from Cloudflare, and a file selected inside it remains on the visitor device. It cannot access the host page audio, microphone or screen capture.
The custom-visuals brief builder keeps the details you enter in the current tab. It does not send them to a server or save them in browser storage. Downloading a brief creates a local text file. Opening an email draft passes the brief to your email application; you decide whether to send it to Balance IT. Contact information you include in a sent email is received by Balance IT for handling your enquiry.
If you follow a link to another website, that site receives your visit under its own policies. It does not receive your selected audio from PHASE//VOID.
Choosing a workflow stays in your tab.
The tool chooser keeps its requirements locally in the current page. It sends only fixed labels for first completion and Studio clicks; a fixed from=compare marker separately counts arrival and first successful audio activation in Studio. No answers, selected tool names, audio, filenames, project details or visitor/session identifiers are added to the measurement rows. These independent aggregate counts do not establish a joined conversion rate or unique visitors. They use the same release/day counter described above.
You control the session.
- Use Disconnect to stop a live input. Your browser also provides controls to stop sharing or revoke microphone access.
- Clear this site's browser storage to remove remembered settings and presets.
- Save exports you want to keep, and delete local downloads yourself when no longer needed.
- Close the studio when you have finished. Live capture and temporary in-page media are not a persistent cloud session.
For questions about PHASE//VOID or this notice, contact Balance IT at kontakt@balanceit.pl. If you email us, the message and contact details you choose to send are handled through that separate email conversation.
Local tempo analysis.
The BPM finder and Studio tempo panel decode a chosen 8–60 second section and analyze it in a local worker without playing sound. Files, names, waveforms, candidates and typed corrections are not uploaded, logged or saved by this tool. Clear, cancel and page exit release the work. No new permission, account, remote AI or audio cache is used.
Use track & tempo in Studio opens a same-origin tab with the public BPM number in its query and a temporary handoff nonce. The File transfers directly between these tabs after explicit receipt and arrives paused with speaker monitoring off. The BPM number is visible in the URL and normal hosting requests; the track and its filename are not put into that URL. Applying tempo changes the local Studio settings only. Method and limits.
Task search and public documentation.
The task finder in Guides and Studio filters curated public instructions in your browser. It does not store or send typed searches. Two fixed, independent Studio counters can record opening help and choosing a jump to controls; no query, workflow ID, file, title, session or visitor identifier is included. Known local/qa=1 tests are excluded.
Remote MCP search_docs and get_doc receive public text/ID requests explicitly sent by an assistant or client. They cannot inspect private Studio files or execute controls. The assistant/provider has its own handling of those requests; remote MCP queries are different from the local human search.
Recorded-file inspection stays on this device.
Timestamped capture and the recording inspector run in your browser. MP4/WebM files selected in Open a saved video to check, their decoded playback, encoded packet metadata and downloadable timing reports are not uploaded to PHASE//VOID. Reports contain technical timing, codec and size information, without the original filename or audio title. They are held in this tab until replaced or closed; download them deliberately if you want a copy.
Your media workspace stays local.
Assets reads selected videos locally for muted off-air preview and validated reattachment. Display names, bins, default trim, original filenames and cue dependencies stay in local browser settings and downloaded session JSON or checklist TXT. These files contain metadata, not video bytes or a portable media bundle; review private names before sharing. Saved-act drafts and muted previews stay in this tab. Saved cue settings may persist in browser settings/session JSON, including private cue/clip names and metadata, without media bytes. Public recipe links and read-only MCP do not carry or access these private acts. Opening the editor, first drawn preview, Save, Cancel, Undo and successful Prepare each send a fixed anonymous milestone once per page; names, settings, media and visitor identifiers are excluded. Independent counts do not prove a joined funnel, unique performers or musical synchronization. Cancel discards the draft; Undo saved edit is temporary in this tab rather than persistent history. The read-only MCP endpoint cannot inspect private clips, bins, sessions or drafts, or preview, save or fire a cue.
Opening the workspace, successfully reattaching files and requesting a checklist each send only a fixed event/page label once per page, with release and UTC day. Names, bins, trim, file bytes, paths, session contents and visitor identifiers are excluded. These independent counts cannot reconstruct a journey or prove a completed download, prepared show, unique user or conversion rate.
Selected-act transfers stay local.
Act Pack export/import reads and writes local JSON, without uploading private packs or media. Packs can contain private cue names, surface labels and original clip filenames/descriptors; review before sharing. Captured surface looks do not include venue calibration geometry. Public example downloads request fixed first-party assets; a Studio entry marker contains no private pack data. Read-only MCP can describe public examples but cannot read/export/import private acts, match local files, bind surfaces, append, undo or perform a show.
Export contains selected captured settings and clip descriptors, not a portable media bundle. Import reviews file reuse and current-surface binding before append; it does not replace Program, audio, calibration, MIDI, timing or export options. Review private names before deliberately sharing downloaded JSON. A public example entry carries only a fixed workflow marker; it does not send a private pack.
File-render media stays local.
Sound files, clip media, session settings and generated output are processed locally; this workflow does not upload them. A chosen soundtrack stays in memory, including an explicit same-origin tab transfer; optional proposed ranges, waveform data and decoded previews remain local. Public URLs, MCP and saved sessions exclude the File and proposed range; reload still requires the local file. The explicit example loader fetches only its known public session, loops and WAV, never a private media URL. A local session can contain private names, clip descriptors and calibrated geometry: review it before deliberately sharing. Public setup links and the read-only MCP do not carry these private files or mappings. Four fixed first-party milestone labels count opening, starting, result-ready and the user saved-confirmation once per page load, without private filenames, media, timelines, settings or mappings. They are independent aggregate counts, not a joined conversion funnel; saved-confirmation is not evidence that a browser download completed. Ordinary website requests still reach the hosting provider. File render can fit every queued act to a selected local MP3/WAV passage using editable film-only hold seconds, without changing the live queue. Coverage warnings require an explicit partial/extended-show approval. Sequence Review causally replays the first selected output at film FPS and samples later holds, transitions and the final picture; thumbnail stills do not certify motion or synchronization. The reviewed plan feeds the existing serial multi-format renderer. Manual BPM supports 30–300; fit does not detect beats, snap phrases or stretch audio. File render offers Soundtrack entry times for a complete cue queue: edit absolute soundtrack seconds or Place here at the separate PCM preview playhead. Each entry starts the incoming transition on the nearest film frame; the first act stays at passage start. Invalid order, bounds, overlapping transitions or holds shorter than 0.25 seconds block Review. A changed soundtrack, passage, FPS or show requires an explicit reset of retained entries. Preview windows can start later in the file and decode at most 60 seconds, with monitoring off by default. The selected film passage and live cues stay unchanged; no beat detection or physical sync guarantee is implied.
A file render silently decodes the selected soundtrack and required clips. It does not request live-input permissions or start speaker monitoring. The existing read-only MCP cannot access these media, inspect private rendering settings or start, cancel or save the job.
A custom-work scope remains local until you share it.
The custom-visuals scope builder keeps your project details in the current tab. Download editable draft .json creates a local file that may contain private project information. Reopen a saved draft reads that file locally; neither action uploads it. No entered details are saved in browser storage, and reloading loses an unsaved draft. A public world/canvas, procedural show recipe or comparison requirements can arrive through a link fragment; media, filenames, private titles and calibrated venue geometry are excluded. URL fragments are not sent in normal hosting requests.
Reference arrival, example choice, context handoff, requested draft/text download, draft reopening, copy and email-draft opening send only fixed event/page labels, with release and UTC day. These independent counts do not establish a sent enquiry, a joined conversion rate or revenue. Copy and text download keep the complete reviewed brief. A short email-draft link passes it to your configured email app, where you decide whether to send; long briefs use copy/download to avoid truncation.
Performance action counts exclude your show.
Opening performance pads, the first quantized cue request, first successful commit and first explicit queued-cue cancellation send only fixed event/page labels once per page. No cue name or ID, BPM, chosen mode, timing trace, media, session data or visitor identifier is transmitted. These independent aggregate counts do not establish a joined conversion rate, unique performers or successful musical synchronization. Launch mode remains in local settings and downloaded sessions; pending launches and running transport do not resume after restore.
Your track, from homepage to Studio.
A local MP3/WAV selected on the homepage or MP3/WAV guide stays in browser memory. Preview analyzes it locally with speaker monitoring off until enabled deliberately. An explicit same-origin, short-lived, one-use transfer can send the File to a new Studio tab after receipt is confirmed; it does not upload the file to a server or AI service. Refresh loses the local file; there is no persistent media cache or cloud library. Public setup links and custom-work context exclude audio bytes and filenames. Fixed action counters distinguish local loading, preview start, Studio receipt and failed receipt using event/page labels, release and day only; they exclude file contents, names, paths, transfer tokens and visitor identifiers. These are independent counts, not a joined conversion rate or completed films.
Your catalogue audition.
Audio stays in browser memory without upload or persistent media caching. An optional proposed passage travels privately with the File. Public setup/B2B links exclude the File, filename, proposed range and transfer token. Favorites store known world IDs in the existing browser library, separately from media. Fixed counters distinguish local loading, comparison after an actual rendered frame and a saved favorite. Labels, page, release and day exclude queries, worlds, names, timing and visitor identifiers. Independent counts do not establish a joined conversion rate or completed films.
Local room control.
Commands/status stay on private LAN and loopback; separate keys stay local. Setup addresses and key-file path are memory-only and excluded from handover, session files and measurement. The plan collects no control/status key. Production --keys-file uses an owner-private folder outside repositories/shared folders; default RAM keys change on restart. Windows mode 0600 does not set NTFS ACLs. Browser pairing keys are memory-only; sessions exclude keys/media. LAN HTTP is unencrypted; restrict the Miniserver peer. Fixed Room action counters contain only an action label, Studio category, day and release; no IP, path, key or check content. They are independent action counts, not completed installations. Normal hosting requests still occur.
Audio spectrum layer.
This layer reuses the existing local analyzed signal and introduces no new media upload, microphone permission, remote inference, audio cache or telemetry fields. Its visual settings are part of the normal local/settings-only session. The public examples use original test material. Guide-to-Studio clicks use the existing aggregate guide_studio_click event with the fixed audio_spectrum page label; no style, color, file or signal data enters it. Known local and qa=1 guide checks are excluded.
Beat-loop effect settings.
Waveform, period, endpoints and phase remain local visual settings in sessions, maps and captured acts. The loop samples the existing visual beat grid and introduces no timer, analyser, media upload, device permission or telemetry field. The public MCP endpoint returns documentation and cannot inspect or change private modulation settings.
Local workspace layout.
Stage/Studio view, inspector visibility and preferred width are stored in phasevoid-workspace-v1 on this browser. They are separate from portable sessions, maps, media and shared links. Reset layout restores the defaults. These controls add no telemetry field, media request, permission or remote-control endpoint. Storage can be cleared with the browser’s site data.
Audio-to-effect links.
Band selection, ranges and curves remain local visual settings in sessions, maps and captured compositions. The routing reuses the existing local analyzed signal. It adds no media upload, audio cache, inference endpoint, analyser, device permission or telemetry field. Existing fixed aggregate page/action counters remain separate from these private settings.
Timed words stay in your project.
Subtitle imports and typed lines remain on this device and in local/saved sessions. They are not uploaded, sent to MCP, included in public look/show links or added to aggregate events. Clearing site data removes local settings; a saved session JSON may contain private lyrics, so share it deliberately.
Copying official product information.
About copy buttons use the device clipboard. A successful description copy, official-link copy or Studio link click can send its fixed aggregate action label with page, release and UTC day through the existing measurement endpoint. Copied text, URLs, clipboard contents, project data and visitor identity are excluded. Copying does not publish a post or send an enquiry.