Privacy
Rung is run by Vigu Enterprises LLC ("Rung"). This page explains, in plain words, what happens with your information when you use Rung.
The short version
Your resume draft stays in your browser, and Rung keeps no copy. When an AI step needs information, Rung sends only the text and facts needed for that task to OpenRouter. Requests use routes that deny provider data collection and require zero data retention. Rung does not store request text. See Privacy for details. If Rung matches the job you describe, it does not keep your original wording. If it cannot match the job, Rung may keep what you typed after removing text shaped like an email address or phone number. Other details in that text may remain. The next section lists what Rung keeps and for how long.
What stays on your device
Your answers and your resume draft are saved in your browser, on your device. Rung's servers do not store them. If you clear your browser data, they are gone, so save your finished resume as a PDF or Word file.
A draft you leave alone for eight days clears itself, and once you have saved your file you can remove it from this browser at any time from the finished resume. On a shared or public computer that is worth doing before you walk away.
What leaves your device to build your resume, and what happens to it there
A few steps use services outside Rung. This section says what leaves your device, why it leaves, and what each service may retain.
- AI-assisted writing and interpretation. OpenRouter receives the text and facts needed to draft resume wording, check or improve that wording, write a cover letter, or interpret an answer when a model-assisted step is needed. Whole-resume drafting deliberately leaves out your name. A signed cover letter includes it, and a name or other detail you volunteer inside an answer remains part of that answer. Rung does not store this request text. Every request denies provider data collection and requires zero-data-retention routing. Under that routing, providers are not permitted to retain the prompt or response or use it for training.
- Occupation meaning matching. When matching by words is not enough, the job title, work description, or first sentence being matched may be sent to OpenRouter. Rung adds no separate name, contact details, or resume to this request; anything volunteered inside the sentence remains part of it. The same request-level zero-retention and no-data-collection requirements apply.
- Existing-resume import. PDF, DOCX, and image files are read in your browser. The raw file and locally detected contact header stay on your device. The remaining resume text, including work, education, skills, languages, projects, volunteer work, and additional sections, is sent through the same zero-retention OpenRouter path used for writing and interpretation. The normalized draft stays in this browser under the same eight-day draft policy.
- Voice features. They are switched off, so Rung sends no audio or read-aloud text to a speech service.
What supports these controls
Vigu keeps dated records of the account settings and written terms behind the provider controls described above. Those records support the published statements about data collection and retention.
The services behind Rung
The writing, hosting, and traffic services are set out again for a compliance review: what each one does and what each may retain. The account settings and written terms behind this table are dated and kept on record. When voice is active, its current processing services are named in the voice line above.
| Service | What it does | What it may keep |
|---|---|---|
| OpenRouter | Routes AI-assisted writing, interpretation, and meaning-matching requests to a compatible model endpoint and returns the result | No prompt or response content under Rung's required zero-data-retention routing. OpenRouter may keep request metadata such as the model used, token count, time, and latency, without the prompt or response |
| Current AI model routes: openai/gpt-4o-mini, google/gemini-2.5-flash, meta-llama/llama-3.3-70b-instruct, google/gemini-embedding-001. This list comes directly from the active writing, interpretation, and meaning-matching configuration. | These are the model routes the current product can call | Each route must accept the same zero-retention and no-data-collection requirements. If no compatible endpoint is available, the request fails and Rung uses its grounded fallback |
| Render | Runs Rung's servers and holds the records described below | Those records for up to 90 days. No resume, account, or contact field is stored. The only words you type that are kept are feedback and a job title Rung could not place; email- and phone-shaped text is removed, while other details you volunteer remain part of those words |
| Cloudflare | Carries traffic to Rung and reports the visitor's country, state and city | Its own connection logs, under its own terms. Rung sends it no resume content |
The model routes above come from the same active configuration and shipped meaning index used by the product, so a deployment change updates this disclosure without a separate manual model list.
What Rung keeps
Your resume draft stays in your browser, and Rung keeps no copy. When an AI step needs information, Rung sends only the text and facts needed for that task to OpenRouter. Requests use routes that deny provider data collection and require zero data retention. Rung does not store request text. See Privacy for details.
The job title you type works the same way while Rung can place it: what gets recorded is the occupation it matched you to, a code from a public government list, and your own words are not kept. When Rung cannot place it, those words are kept instead of the code. Rung is built on a public list of around a thousand occupations, and real work sometimes sits outside it; the words are the only way to see which work that is, so it can be covered. Before they are stored, anything shaped like an email address or a phone number is removed from them. They are kept with nothing beside them that could say who wrote them: no name, no contact detail, no device, and nothing that links one visit to another. They are your words, so if you typed more than a job title into that box and would rather Rung did not keep it, write to privacy@rung.guru with the day you sent it and it will be removed.
Rung's structured product records carry no name, contact field, or resume content: they can include the occupation someone is working toward, the starting situation they chose, the general device type, and a coarse location. Separately, Rung keeps feedback and a job title it could not place. Email- and phone-shaped text is removed first, but any other detail volunteered inside those words remains part of them. Everything Rung keeps is kept for up to 90 days and then deleted. These records go nowhere but Rung: no advertiser, data broker or buyer ever receives them.
Location
Rung reads your country from your network connection to select a reviewed market pack and a first-visit language default. If no local pack is available, Rung uses its neutral experience: occupation duties, skills, tools, writing help, and resume export remain available, while local pay, licensing claims, security clearances, and government links are not shown. An unsupported country never falls back to United States market information. The market decision is kept with the draft on this device and is not tied to the resume content Rung processes.
Product signals
Rung records a small set of simple product events, like which starting situation people choose, which questions they answer or skip, whether the app had to fall back from its AI cleanup, the interface language, the general device type, and whether the request came from a person or from an automated client such as a search engine crawler. Each page load is tagged with a random, in-memory id so Rung can see how a single visit flows, but that id is never saved on your device, uses no cookie, and cannot link one visit to another or to you. These events include a coarse location (your country, your state or province, and your city where the network provides it) so Rung can understand how it works in different places. That location comes from your network connection, never from your exact position, and no IP address is stored with it. The events carry no names, no contact details, and no resume content.
When an AI application uses Rung's public MCP server, Rung processes the public lookup term for that request and does not retain the term or returned result. The MCP tools have no dedicated name, contact, work-history, or resume fields; send public lookup terms only. Rung keeps fixed aggregate counts for server discovery, tool and prompt lists, searches that found or did not find a guide, occupation exploration, the requested language, and fixed outcome classes for invalid requests, protocol incompatibility, rejected origins, rate limits, and internal errors. Those machine counts contain no request, result, visitor id, device, location, or IP address. On the public MCP connection page, the product events described above can record that the page was read, which fixed setup panel was opened, which fixed copy control succeeded, and which type of Rung handoff was selected. They never carry the copied text, AI account, prompt, lookup term, returned result, or destination URL.
When you tell us how Rung is doing
If you answer the feedback question in the app, Rung keeps what you chose and anything you wrote, along with the occupation you are working toward, your situation, the screen you were on, your languages, your general device type and your country. This and a job title Rung could not place are the only things you write that Rung keeps, because a report nobody can read would not be worth asking for. The report itself has no name field and no contact details, and before your words are stored anything that looks like an email address or a phone number is replaced. If you wrote something in that box you would rather Rung did not keep, write to privacy@rung.guru and it will be removed. The same random, in-memory visit tag described above travels with it, so a report can be read alongside how that visit went; it still cannot link one visit to another or to you. Please do not put your phone or email in that box: there is nothing there that needs them.
Your choices
- Your resume itself is never kept: it is made and saved on your device, and Rung holds no copy of it.
- Rung creates no record of the name, email, phone number, or other personal fields in your resume. What you can ask to have removed is something you wrote and Rung kept: feedback, or a job title Rung could not place. Name the day you sent it and it will be removed. Questions about your information go to privacy@rung.guru.
Your resume content
What goes into your resume, and what you download, is yours to decide. Rung can make mistakes, and it does not review or endorse what you write. The terms of use set out your responsibility for it.
Age
Rung is meant for people 16 and older.
Changes
If this page changes in a way that matters, the effective date above changes with it.
Contact
Questions about privacy: privacy@rung.guru