Information in Qrewflo
Qrewflo is used by account owners to manage procedures and by workers who open a shared checklist link. The app handles these records:
- Account and sign-in records: an owner’s name and email address, plus session records. A session record can include an IP address and browser user-agent; either field may be absent.
- Worker roster: a worker’s name and optional phone number entered by the account owner.
- Procedures: titles, transcripts, steps, and saved translations. A transcript can be written by the owner or produced from a draft recording.
- Draft recordings: audio files uploaded for transcription, with a file key and URL and file details such as filename, format, and size.
- Checklist submissions: an optional worker name, procedure title, a snapshot of the steps marked completed or skipped, and the submission time. The selected language is used to show and validate a checklist, but the submission record has no separate language field.
How the app uses it
- Account details and sessions support account creation, sign-in, and access.
- Owners use worker names and optional phone numbers to maintain their crew roster.
- Procedure text, steps, and translations are used to create, edit, translate, and share checklists through QR links.
- Draft audio is uploaded and transcribed so an owner can turn a spoken procedure into editable steps.
- Checklist submissions let the account owner review which steps were completed or skipped.
Account owners manage their saved procedures, worker records, and checklist submissions. Workers can open a shared QR link and submit a checklist without creating an account.
Cookies and browser storage
- An authentication cookie keeps an owner signed in. The
NEXT_LOCALEcookie stores the selected interface language. - A worker name can be saved in browser local storage and filled into another checklist opened in that browser.
- The browser can cache up to 10 recently opened checklist copies for offline use. Copies older than 30 days are dropped when the checklist cache is next read or updated. This is a local cache limit, not a server-side deletion period.
- If
POLSIA_ANALYTICS_SLUGis configured, Qrewflo stores a randompolsia_vidin local storage and sends a page-load beacon to Polsia analytics with the site slug and that identifier.
Qrewflo does not request GPS/location or camera access; the browser’s permissions policy keeps both disabled. The worker checklist submission has no photo field, so it does not submit worker photos. Owners can record audio for procedure drafts. You can clear browser storage and cached site data in your browser settings.
Services Qrewflo uses
These services are called by the current app to run its features. They are separate from advertising.
- Database: Qrewflo records use PostgreSQL. The app code does not identify the database host or where its data is physically located.
- Audio files and transcription: draft audio is uploaded through Polsia’s file service and sent through Polsia’s transcription service. The transcription instructions say OpenAI processes the audio outside the EU.
- Procedure organization and translation: procedure transcripts and saved procedure content are sent to Polsia’s AI proxy for organization or translation. The app code does not identify the model or processing region for these requests.
- Email: Polsia’s email service sends account verification and password-reset messages.
- Analytics: when configured, the page-load beacon described above goes to Polsia analytics.
The app code contains no cross-context behavioral advertising integration. It does send information to the services listed above to provide app features and, when enabled, analytics. Code alone does not establish whether any processing meets a legal definition of a “sale” or “sharing” under California law; Qrewflo’s business practices and service agreements would need to be reviewed to make that legal determination.
How long information stays
- The browser checklist cache has a 10-item cap and a 30-day age cutoff, as described above.
- Polsia deletes transcription jobs and their text 7 days after a job is complete. This applies to the transcription service’s job data. It does not delete the audio file or transcript saved by Qrewflo in a draft.
- The current app code does not show a fixed automatic purge period for uploaded draft audio, draft transcripts, or saved procedures. It does not provide an app-wide retention schedule for the other database records here.
GDPR rights
If the GDPR applies to your information, you may have the right to ask for access, correction, erasure, restriction of processing, data portability, or to object to processing. If a particular use is based on your consent, you may withdraw that consent. The app code does not document which lawful basis applies to each use, so Qrewflo has not named one here.
Under GDPR Article 12, a controller generally must respond without undue delay and within one month. The law allows up to two more months when necessary because of the request’s complexity or number of requests, with notice and reasons within the first month. This describes the statutory rule; it is not a Qrewflo response-time promise. You may also complain to your data-protection authority.
California privacy rights
If the CCPA applies to you and the information involved, you may have the right to know what personal information is collected, request deletion, request correction, opt out of sale or sharing, limit the use or disclosure of sensitive personal information, and receive equal treatment for exercising your rights. The CCPA generally allows a free request to know up to twice in a 12-month period.
Qrewflo’s app code shows no cross-context behavioral advertising integration. It does show the Polsia analytics beacon when configured and the Polsia processing used for app features, described above. The code does not establish whether those transfers qualify as a sale or sharing under the CCPA, so Qrewflo does not make a broader sale-or-sharing claim here.
For covered businesses, California law generally sets a 45-calendar-day response period for requests to know, delete, or correct and allows an additional 45 days when necessary if the business gives notice and explains the delay. These are statutory time limits, not a Qrewflo response guarantee. California residents may also contact the California Attorney General about their rights.
Contact for privacy requests
To ask a privacy question or make a request, email Qrewflo at the address below. The app provides this email contact; it does not include an in-app privacy request form.
Privacy requests
qrewflo@polsia.app