Privacy Policy

1. Company details

FUEW LTD is registered in England and Wales under company number 17560357. Its registered office is Seasonly, The Catalyst, Baird Lane, York Science Park, Heslington, York, YO10 5GA.

Seasonly is a trading name of FUEW LTD. ICO registration reference: ZC292586.

Seasonly is a mobile app that connects people looking for short-term seasonal work with local businesses that have seasonal hiring needs.

FUEW LTD, trading as Seasonly, is the data controller for personal data processed through the Seasonly app and website.

You can contact us at hello@seasonly.co.uk or write to our registered office.

2. Scope of this policy

This policy covers personal data processed through:

• The Seasonly mobile app (iOS), for both jobseekers and employers.
• The Seasonly browser app at app.seasonly.co.uk, for both jobseekers and employers.
• The seasonly.co.uk website and any waitlist or contact forms hosted there.

It does not cover the privacy practices of employers or other users. Employers are separate data controllers for the information they receive and keep about you, including information you share with them in the app. Please refer to their own privacy practices.

3. Data we collect

3.1 Jobseekers

When you create and use a jobseeker account (currently by invitation only), we collect:

• Identity and profile data: your name, date of birth, gender, bio and profile photos. We ask for your date of birth to confirm you are 18 or over.
• Location data: your location, taken from your device (with your permission) or from a place you choose. We store these coordinates with your profile to work out distances to jobs and to filter by area. In the iOS app, Apple services support place search and turning coordinates into place names. In the browser app, selected place-search text and coordinates are sent to OpenStreetMap Nominatim for place search and reverse geocoding. Nominatim also receives standard request information, such as your IP address.
• Professional data: industries and job types you are interested in, seasonal availability, employment type preference, work experience and education history.
• CV uploads: if you choose CV scanning and allow the separate AI processing request, the file is kept in our file storage and its full text is sent to OpenAI to extract information and pre-fill your profile. You can cancel instead, and you review the results before saving. This includes any contact details in your CV, such as your phone number or address.
• Authentication data: managed by our authentication provider, Clerk. This includes your email address, login credentials and email verification codes. Clerk also records the IP address and device and browser details of each sign-in session to keep accounts secure.
• Communications: messages you send and receive in in-app chat, and any files you attach. We do not request, check or verify right-to-work documents or share codes. If you choose to send them to an employer in chat, they are treated like any other file.
• Safety reports, blocks and image checks: reports record who made the report, who or what it concerns, relevant job, application, chat or message references, the reason, any note, review status and timestamps. We also record blocks so we can enforce them. Images are checked for sexual content, hate, self-harm and violence before they can be shared; pending images stay hidden. Some images may be flagged or rejected, and moderation results and review events may be recorded. If someone reports or blocks you, related information may be recorded about you. We do not tell people who reported them or that they have been blocked.
• Device and email-notification data: your push notification token, used to send match and message alerts, and whether you enable Daily email digest. If enabled, jobseekers may receive one email about new matches and one about new jobs each day, when there are relevant updates. Employers receive an email when they have new applicants to their roles, grouped by role and sent once a day when applicable.
• Diagnostic data: if the app crashes or hits an error, a crash report is sent to our error-monitoring provider (Sentry). It includes technical details such as the error, your device model, operating system and app version, an installation identifier, performance information and recent steps in the app. We do not intentionally attach your account identity to Sentry reports, but device and installation identifiers can link diagnostics to an installation; these reports should not be treated as anonymous.
• Usage data: internal event data such as swipes, matches and messages sent, used for product analytics and improvement. This is not shown to employers.

Please do not include sensitive information (for example about your health, ethnicity, religion or sexual orientation) in your CV, profile or chats unless you are happy for it to be processed as described in this policy.

3.2 Employers

When you create and use an employer account (by invitation only), we collect:

• Business data: company name, logo and description.
• Job listings: role title, pay, hours, dates and location for each listing.
• Authentication data: managed by Clerk (email, credentials, and sign-in session IP address and device details).
• Communications: messages and attachments exchanged in-app with matched jobseekers.
• Email-notification data: whether you enable Daily email digest. If enabled, we use your email address and name to email you about new applicants to your roles, grouped by role and sent once a day when applicable.
• Usage data: internal event data such as matches and messages sent.
• Safety reports and blocks: as described in section 3.1.
• Pilot contact and declarations: your business name, the name and contact details of the person we deal with, the fair work declarations you agreed to when joining the pilot, and any evidence you send us about them. We keep these to run the pilot safely.
• Diagnostic data: crash reports, as described in section 3.1.

3.3 AI-generated data

With your permission, we generate vector embeddings from jobseeker profile data (such as your bio, skills, industries, preferred employment type, past job titles and employers, and schools) and from employer job listings, using the OpenAI API. Embeddings are numerical representations used to power AI matching. They are stored in our database alongside your profile or listing and are not shared beyond what is described in section 7.

When you enable AI job picks, we also use OpenAI to write short explanations based on your preferences and the job’s details. Matching may run in the background while permission is enabled. You can turn off AI job picks in Profile → AI privacy; this clears your saved matching embedding and daily picks. You can still browse and apply without AI picks. Employer listing processing and CV scanning have separate permission prompts; declining listing processing saves the listing without an AI embedding. OpenAI requests are made from our servers. Even without an account ID, submitted text may identify you.

Image checks. Before an image can be shared, we send it to Microsoft Azure AI Content Safety to check for sexual content, hate, self-harm and violence. Pending images remain hidden. High-severity sexual content is rejected automatically; other severe category results may be flagged for review. Flagged profile and job images are hidden. Flagged chat images may appear behind a warning with a reveal option, depending on your sensitive-image settings; reported images may remain hidden. These automated checks can make mistakes and do not replace reports or human review. PDFs, including images embedded in PDFs, are not image-screened.

The Profile setting “Allow image safety checks” controls permission for future image uploads. Turning it off prevents future image uploads from being sent for checking; it does not cancel a check already in progress or delete images already uploaded. A separate sensitive-image setting controls whether flagged chat images are hidden behind a warning.

Our Azure AI Content Safety resource is in France Central. Microsoft states that images submitted for detection are not stored by the model or used to train, retrain or improve it, and that processing remains in the selected region. This describes Microsoft’s detection service and does not change Seasonly’s own image storage and retention described below.

3.4 Website visitors

If you visit seasonly.co.uk or submit a form (such as the waitlist form), we collect the details you submit (for example your name and email address). Our hosting provider also processes standard technical request data, such as IP address, needed to deliver and secure the site (see section 12).

3.5 Support and concerns you email to us

If you email us at hello@seasonly.co.uk for support or to raise a concern about an employer or another user (instead of, or as well as, reporting them in the app), we keep your email, the details you give us and any notes from looking into it. We keep this only as long as we need to investigate and resolve the concern (see section 9.5).

We may share the details of the concern with the employer involved so they can respond, but we will not tell them who raised it without your permission. We may also share information with the relevant authorities where the law requires us to.

3.6 Local operational records

We keep restricted operational files to monitor pilot activity and investigate unexpected changes or data loss. Current files include development snapshots and a classification plan for fictional profiles and reviewer/test accounts. They may contain internal record identifiers, creation times, test-account labels, proposed flags and aggregate counts. Record IDs can identify test accounts, so these files are not anonymous. They do not include names, email addresses, CVs or message contents. We do not currently keep routine local exports of real pilot users.

4. Legal bases for processing

Under UK GDPR, we rely on the following legal bases:

Where we rely on legitimate interests, we have weighed our interests against your rights and freedoms. You can object to this processing at any time by contacting us.

We send optional job-alert emails only after you enable Daily email digest. Any other direct marketing will be sent only where we have the required permission.

5. How we use your data

• Matching: to rank and present relevant job listings to jobseekers, and to rank applicants for employers, using AI-powered compatibility scoring, and to explain why a job has been suggested.
• Communication: to enable in-app messaging between matched users.
• Notifications: to send push notifications about new matches and messages. If you enable Daily email digest in Profile → Notifications, we use your email address, name and notification choice to send optional emails through Brevo. Jobseekers may receive up to two emails a day: one about new matches and one about new jobs. Employers receive an email when they have new applicants to their roles, grouped by role and sent once a day. We send each email only when there is a relevant update. Emails may include job titles, company names, locations and applicant counts, but not full chat history, CVs or attachments. They may include a link to open Seasonly and explore listings or applicants. You can turn off the digest in Profile → Notifications or use the direct unsubscribe link included in each email.
• Profile display: to show jobseeker profiles to employers, subject to section 6.
• CV processing: to read an uploaded CV and pre-fill your profile.
• Account management: to authenticate you, maintain your account and let you delete it.
• Safety: to check images before sharing, review reports, stop blocked users from seeing or contacting each other, investigate concerns and misuse, and ask employers for evidence that they meet the fair-work standards they agreed to. Pending images stay hidden; flagged images may be hidden or shown behind a warning. Seasonly reviews reports and may remove content or suspend accounts.
• Product improvement and security: to monitor performance, find and fix crashes and errors, and keep the service secure.
• Legal compliance: to comply with the law and respond to lawful requests.

We do not sell your personal data. We do not use your data for advertising profiling.

We use the restricted operational records described in section 3.6 to monitor the pilot and investigate unexpected changes or data loss.

6. Who can see your data

We aim to limit how widely your data is visible:

• Employers can only see jobseekers who have applied to their listings. They cannot browse or search the wider pool of jobseekers.
• Your work experience and education history are visible to you and to employers whose listings you have applied to, including while your application is pending or after it is rejected. Access is restricted when either participant blocks the other or the employer is banned. If you enable employer access to your uploaded CV, employers you have applied to can also view it.
• Resolved chats remain visible (read-only) to both the jobseeker and the employer after a match ends, unless hidden from your view by chat deletion or removed through blocking, account deletion, permanent listing deletion or moderation. The reason an employer marks a match as resolved is not shown to the jobseeker.
• Internal analytics are used only by us and are not shown to employers or jobseekers.

Anything you share with another user, including in chat, can be seen, saved and used by that user. We cannot control what they do with it once they have it.

Deleting a chat removes the conversation and its previous messages from your app view only. It does not withdraw your application, delete the other participant’s copy or block them. A new message can reopen the conversation, but previous messages remain hidden from the participant who deleted them. The underlying records remain subject to our retention rules, including the separate 30-day attachment-removal schedule. Account deletion, permanent listing deletion and moderation may remove records from both participants’ views.

7. Service providers (processors)

We share personal data with the following providers, who process it on our behalf under contractual terms:

We do not share your personal data with anyone else except where required by law or to protect our legal rights.

8. International transfers

Some of our service providers are based in, or may process personal data in, countries outside the UK. This includes providers listed in section 7. Brevo states that its database hosting is in the EU: its primary hosting is with OVH in France and Germany, with cloud storage on Google Cloud in Belgium. Brevo’s DPA says that some services may involve processing outside the EEA and that applicable transfer safeguards are used. The exact locations and safeguards can depend on the services and subprocessors involved.

Where a transfer is restricted under UK data protection law, we use an applicable transfer mechanism or other permitted safeguard. You can contact us for further information about relevant safeguards.

You can ask for more information about these safeguards by contacting us at hello@seasonly.co.uk.

9. How long we keep your data

9.1 Accounts

We keep account data while your account is active. Choose Profile → Delete Account to start deletion. The app removes the account’s Convex records, including related listings or applications, matches and messages, preferences, location, push token, product events, invite redemption, reports, blocks, upload records and image-permission records. Deleting either account removes its associated reports, including open reports, and removes affected messages from the other participant’s app view. Files and their upload records are deleted when no remaining user, employer, listing or message record references them. If a shared file is still needed, we retain the file and the technical information needed to display it and preserve image-safety restrictions. We remove the deleted uploader’s account identifier and free-text moderation reason from that upload record. The file itself may still identify people. Copies downloaded or saved by other people are outside our control. The app then asks Clerk to delete your sign-in. If the Convex deletion fails, the app shows an error and does not proceed to Clerk. If Convex deletion succeeds but Clerk deletion fails, a recovery marker on that device can prompt a retry the next time you sign in. Reinstalling or changing devices may lose that marker, so contact us if you cannot finish. Provider logs, backups, diagnostics and email copies may remain under separate retention arrangements described below.

Account deletion in the app does not automatically erase these local operational files. They are kept until manually removed and currently relate to development, fictional test and reviewer accounts; we do not routinely export real pilot users’ records locally.

9.2 Chat messages and attachments

Deleting a chat removes the conversation and its previous messages from your app view only. It does not withdraw your application, delete the other participant’s copy or block them. A new message can reopen the conversation, but previous messages remain hidden from the participant who deleted them. The underlying records remain subject to our retention rules, including the separate 30-day attachment-removal schedule. Account deletion, permanent listing deletion and moderation may remove records from both participants’ views.

Chat attachments are scheduled to be removed from each message after 30 days. The message text stays and shows that the attachment was removed. The underlying file and upload record remain while another record references the file. Pending images are eligible for cleanup after seven days only if no app record references them. Referenced pending images stay hidden for review. Message text has no scheduled expiry and is removed when relevant account or match records are deleted or a listing is permanently deleted, subject to section 9.1.

Please only share documents that an employer has asked you to provide, and no more than is needed. Employers are responsible for keeping their own records of right-to-work checks as the law requires, and should not rely on Seasonly to store them.

9.3 CV files

Uploaded CV files are kept in our file storage until you remove them using an available in-app control or delete your account, subject to the shared-reference safeguards in section 9.1. Profile photos and company or job images have no general age-based expiry; they remain while associated app records use them and are deleted during account deletion when no remaining record references them. A shared file may remain in storage while another record references it. Information taken from a CV becomes part of your profile.

9.4 Safety reports and blocks

Open safety reports remain until reviewed. Reports in reviewed or actioned status, and their associated review records, are scheduled for deletion six calendar months after the most recent review. If a report is reviewed again, the retention period runs from the latest review timestamp. Deleting either associated account removes its Convex report record sooner. The report record includes the Brevo message ID and delivery information, which are deleted with that Convex record. This does not delete the email from our mailbox or Brevo logs.

Blocks are kept while needed to enforce them and are removed if either associated account is deleted. Block retention is separate from report retention. Closed moderation events are scheduled for age-based cleanup; moderation-action audit records use their own creation date for cleanup and may remain after account deletion.

We send report alerts through Brevo to hello@seasonly.co.uk. Alerts include the report reason, any note, and the relevant report, job, application or message reference. They do not include photos or full chat history. We delete mailbox copies when no longer needed and no later than six months after the report is resolved, unless a legal obligation or legal claim requires longer retention. Brevo transactional logs are configured for six months, and previews are set not to be stored for new emails. Previously stored previews may not be removed by changing that setting, so they may need separate deletion.

9.5 Support and concerns emailed to us

Support emails and concerns are kept for as long as needed to respond, maintain relevant case history and resolve follow-up issues or disputes, unless the law requires us to keep them for longer (see section 9.7).

9.6 Employer pilot records

Basic details about pilot employers (business name, contact details and the declarations they agreed to) are kept while their account is active and for as long afterwards as we need to deal with any concern raised during the pilot.

9.7 Legal holds

We may keep certain data for longer where the law requires it, or where it is needed to establish, exercise or defend legal claims.

Deleting Seasonly records does not automatically delete information already sent to service providers, provider logs, platform backups, security records or diagnostics. OpenAI processes optional CV text, matching information and job-pick explanations as described in section 3.3; we have not verified the current retention settings for the OpenAI account or historical requests. Microsoft states that Azure AI Content Safety does not store submitted images in the model or use them for training, and keeps processing in the selected region; this does not describe Seasonly’s own stored images or moderation records. Brevo transactional logs are set to delete after six months. The “Never store previews” setting applies to new emails; previews created before that setting may remain unless deleted separately. We delete report-alert emails from our mailbox when no longer needed and no later than six months after resolution, except where longer retention is required for a legal obligation or claim. Other providers’ logs, backups and diagnostic records follow their applicable arrangements, which may differ.

9.8 Removed listings

Moving a listing to Recently Deleted removes it from jobseeker discovery and stops new applications. Automatic permanent deletion of listings is paused. A listing remains recoverable until the employer permanently deletes it, the associated account is deleted, or Seasonly removes it under another stated retention rule. Permanent deletion removes the listing and its associated applications, matches and conversations from both participants’ app views. Chat attachments follow section 9.2, and shared files remain while another record references them.

10. Your rights

Under UK GDPR you have the right to:

• Access the personal data we hold about you.
• Have inaccurate or incomplete data corrected.
• Have your data erased. The easiest way is to delete your account in the app, or you can contact us.
• Restrict how we process your data in certain circumstances.
• Receive your data in a structured, commonly used, machine-readable format, where processing is based on contract or consent.
• Object to processing based on legitimate interests.
• Withdraw consent at any time, where we rely on it.

Automated decisions: our AI matching ranks jobseekers and listings automatically, which affects the order in which people and jobs are shown. We do not make solely automated decisions that have legal or similarly significant effects on you. Employers make their own hiring decisions. If you have concerns about how matching affects you, please contact us.

To exercise any of these rights, contact hello@seasonly.co.uk. We will respond within one month.

11. Minimum age

Seasonly is intended for people aged 18 and over. We do not knowingly collect personal data from anyone under 18. If you are under 18, please do not use the app. If we learn that we have collected data from someone under 18, we will delete it. If you believe this has happened, please contact us at hello@seasonly.co.uk.

12. Cookies and website analytics

The Seasonly mobile app does not use cookies. It may use device identifiers and similar technologies that are needed to provide the service, such as keeping you signed in, delivering notifications, and installation identifiers used for crash and performance diagnostics.

The seasonly.co.uk website uses only strictly necessary cookies, which are needed for the site to work and stay secure (for example security cookies set by Cloudflare). These do not require your consent under the Privacy and Electronic Communications Regulations 2003 (PECR).

We do not currently use analytics or advertising cookies on the website. If we add them in future, we will update this policy and ask for your consent before they are set.

You can block or delete cookies in your browser settings, although some parts of the website may not work properly if you do.

13. Security

We take reasonable technical and organisational measures to protect your personal data against unauthorised access, loss or misuse. These include encryption in transit (TLS/HTTPS), encryption at rest provided by our database provider, access controls, and invitation-only employer account creation.

In-app chat messages and attachments are not end-to-end encrypted, so we are technically able to access them. We do not routinely read them. We may access them where needed to investigate a concern reported to us, a safeguarding concern or a security issue, or where the law requires it.

No system is completely secure. If you think your account has been compromised, please contact us straight away at hello@seasonly.co.uk.

14. Changes to this policy

We may update this policy from time to time. We will change the "last updated" date at the top and, for material changes, notify you in the app or by email. If you do not agree with a change, you can stop using the app and delete your account.

15. Contact and complaints

For questions, requests or concerns about this policy or how we handle your data, contact:

Seasonly
The Catalyst, York Science Park, Baird Lane, York, YO10 5GA, GB
hello@seasonly.co.uk

If you are unhappy with how we have handled your data, you can complain to the Information Commissioner's Office (ICO):

• Website: ico.org.uk
• Helpline: 0303 123 1113

We would appreciate the chance to address your concern first, but you do not have to contact us before going to the ICO.