1. Who is responsible
The controller for website and account administration data is [LEGAL ENTITY NAME], [REGISTERED OFFICE ADDRESS]. Privacy contact: [PRIVACY EMAIL — currently using hello@vorq.app until a dedicated address is confirmed] (hello@vorq.app).
2. Scope and roles
Website and account data. When you browse the marketing site, create a login, or contact us, VORQ decides the purposes and means of processing (controller).
Workspace (customer) content. Inventory, suppliers, purchase orders, stock movements, transfers, counts, product images, and similar operational records are Customer Data. The customer organisation determines why that data is processed in day-to-day warehouse operations. VORQ processes it to provide the Service (processor/service provider), except where we process it for our own operations, security, billing, or legal compliance.
[IF serving UK/EEA customers as processor: approve and publish a Data Processing Agreement and subprocessor list]
3. What we collect and why
3.1 Account and profile
We collect:
- identity and contact details (name, email, optional phone, display name);
- authentication data (password credentials stored by our auth provider, or Google sign-in identifiers and profile fields returned by Google);
- profile preferences (avatar, locale such as English/Spanish UI preference);
- organisation membership, role (owner, admin, manager, warehouse staff, viewer), and invite status.
Purpose: create and secure accounts, show the right workspace permissions, personalise the app, and communicate about the Service.
3.2 Workspace and onboarding
When a workspace is created we store organisation name and settings (including currency and locale), plan and subscription status, optional industry/use-case onboarding answers, and seat limits. Invites store the invitee email, role, expiry, and acceptance or revocation state.
3.3 Operational Customer Data
Users enter warehouse data such as products, locations, inventory batches and QR labels, receipts, deductions, transfers, stock counts, purchase orders, and supplier contact details. Product and profile images may be uploaded to file storage. This data is processed to run warehouse workflows the customer configures.
3.4 Audit and activity
The Service records activity needed for operations and accountability, including stock movements and certain profile changes in audit-style records (who changed what, and related notes). Workspace roles with audit permissions can review movement history and export CSV where enabled. IP address and device fields exist in the data model but are not currently populated by the application for those profile audits.
3.5 Notifications and email
We store in-app notifications and notification preferences. Where email digests or transactional messages are enabled, we send email via our email provider (for example team invites, purchase-order emails to suppliers you designate, and daily digests).
3.6 Billing
If you start a paid checkout, payment is handled by Paddle. We store subscription and customer identifiers on the organisation record needed to sync plan status. Card data is handled by Paddle, not stored in VORQ databases.
3.7 Contact and support
The public contact form opens your email client to message hello@vorq.app. VORQ does not store that form submission in the application database. Emails you send are processed as ordinary business correspondence.
3.8 Marketing site content
Public blog and marketing pages may load images from content delivery networks (for example Unsplash-hosted images). Those requests are made by your browser to the image host.
4. Lawful bases (UK GDPR)
Where UK GDPR applies, we rely on:
- Contract — to provide the Service you request (account, workspace, core inventory features);
- Legitimate interests — to secure the Service, prevent abuse, improve reliability, and communicate service notices, balanced against your rights;
- Legal obligation — where we must keep records for tax, accounting, or regulatory reasons;
- Consent — where required for optional cookies or marketing we may add later (we do not currently run third-party advertising analytics pixels on the site).
[CONFIRM target markets: UK only / UK+EEA / US / other — adjust notices accordingly]
5. Who receives data
We share personal data with:
- Supabase — authentication, database, and file storage for the Service;
- Google — if you choose Google sign-in;
- Paddle — if you use paid checkout or the billing portal;
- Resend — transactional email delivery;
- Hosting provider (currently deployed on Vercel) — serving the website and app, logs, and scheduled jobs;
- Your organisation’s users — according to roles (for example managers viewing stock activity);
- Suppliers you email — when you send a purchase order email from the product;
- professional advisers or authorities when required by law, or parties to a business transfer under appropriate safeguards.
We do not sell personal data.
6. International transfers
Providers may process data in the United Kingdom, European Economic Area, United States, or other countries. Where required, we rely on appropriate safeguards such as the provider’s standard contractual clauses or equivalent mechanisms. [CONFIRM provider regions and document SCCs / DPF participation]
7. Cookies and similar technologies
VORQ currently uses:
- Essential authentication cookies set by our auth provider to keep you signed in and refresh sessions;
- Locale cookie (
vorq-locale) to remember interface language preference; - Theme preference stored in browser localStorage (
vorq-theme), not a cookie; - Blog admin cookie (
vorq_blog_admin) only if someone unlocks the internal blog CMS with the site password.
We do not currently load Google Analytics, Meta Pixel, or similar advertising trackers on the marketing site or app. SOP “video coming soon” placeholders do not embed third-party video players yet. If we add analytics or embedded video that sets non-essential cookies, we will update this Policy and, where required, add a consent mechanism.
You can control cookies through your browser settings. Blocking essential auth cookies will prevent sign-in.
8. Retention
We keep personal data only as long as needed for the purposes above:
- account and membership data — for the life of the account/workspace relationship and a wind-down period after closure;
- Customer Data — while the workspace is active, then according to deletion or closure requests and backup cycles;
- audit and movement history — while needed for operational accountability and customer access to history;
- billing records — as required for accounting and tax;
- support emails — for as long as needed to handle the request and maintain a business record.
[SET numeric retention: e.g. backups 30 days; closed workspace 30/90 days; audit logs X months]
9. Your rights
Depending on where you live, you may have rights to access, correct, delete, restrict, or object to certain processing, and to data portability. You may also withdraw consent where processing is consent-based.
To exercise rights, email hello@vorq.app. We may need to verify your identity. If you are a workspace user, some requests may need to be handled with your workspace owner because Customer Data is controlled by that organisation.
Self-service account deletion and full data export are not yet built into the product. We will handle verified requests manually until those tools ship.
10. Security
We use industry-standard measures appropriate to a cloud SaaS product, including encrypted transport (HTTPS), authenticated access controls, role-based permissions inside workspaces, and database access rules enforced by our backend provider. No method of transmission or storage is perfectly secure. Please use strong passwords and protect devices used on the warehouse floor.
11. Children
The Service is directed at businesses and is not intended for children under 16. We do not knowingly collect personal data from children.
12. Changes
We may update this Policy from time to time. The effective date at the top will change when a revision is published at /privacy. Material changes may also be notified by email or in-product message where practical.
13. Contact and complaints
Privacy requests: hello@vorq.app.
If you are in the United Kingdom and unhappy with our response, you may complain to the Information Commissioner’s Office (ICO) at ico.org.uk/make-a-complaint. [ADD other regulators if you serve EEA/US states that require notices]
Review draft. Highlighted placeholders need owner or legal approval before this page is treated as final.
