Privacy Policy

1. Who we are

This policy explains how seeyoushortly handles personal information when you create an account, organise an event, visit an invitation, respond to a host, or use AI Assist.

Operator

Howson Digital Limited, operating seeyoushortly

Address

6 Bartlett Grove, Sherburn in Elmet, Leeds, England, LS25 6FT

Registered in

England and Wales

Privacy contact

privacy@seeyoushortly.com

We decide how account administration, security and our own service operations use information. Event hosts decide whom to invite, what questions to ask, and how to use replies for their events. Where we process guest information on a host’s behalf, the applicable responsibilities depend on that arrangement. [Confirm controller/processor roles and any required host data-processing agreement before launch.]

2. Information we collect

• Accounts: your name, email address, password hash, account status and creation/update dates.
• Events: titles, descriptions, dates, timezone, venue address and map coordinates, schedules, practical details, uploaded photos and captions, and page settings.
• Guests: names and email addresses supplied by the host, invitation credentials stored as hashes, attendance, answers to custom questions and response dates. We receive guest details from hosts and replies directly from guests.
• Payments: the selected event plan, payment confirmation and checkout references. Card details are entered with Stripe; our app does not store your full card number.
• AI Assist: the description you submit and the event-editor details included to prepare or refine a suggestion.
• Service operation: session identifiers, request and rate-limit information, and technical information received by our hosting and service providers, such as IP addresses and browser details.

A host’s questions may invite you to disclose health, disability, allergy or religious information. Provide only what is needed. Contact the host if you would prefer another way to discuss a sensitive requirement. Hosts must identify a lawful basis and any additional condition needed for sensitive information, and give guests appropriate notice.

Account details are needed to provide a host account. Invitation details are needed to access a private event. A host may require some questions for attending guests; missing those answers can prevent submission. Optional AI Assist and browser location features can be left unused.

3. How and why information is used

We use information to run accounts and events, authenticate guests, deliver replies to hosts, process payments, send service emails, provide requested AI suggestions, and protect the service from misuse.

Where UK or EU data-protection rules apply, the proposed bases for our own processing are performing our contract with hosts for account and paid services; legitimate interests in providing secure guest access, preventing abuse and supporting the service; and legal obligations for required financial or regulatory records. Optional processing that requires consent must use a separate, appropriate consent mechanism. [Confirm these bases, the interests assessment and any sensitive-data conditions against the final operating arrangements.]

AI Assist produces suggestions for the host to review. It does not make decisions about guest eligibility, creditworthiness or other matters with legal or similarly significant effects.

4. Who receives information

Your host can see your attendance and answers. Other guests are not given access to the guestlist or individual responses through the event page. People with a guest’s private invitation and event password can use that guest’s access, so keep both private.

• Stripe: checkout and payment processing.
• Amazon Web Services: storage and delivery of uploaded photos.
• Mailjet: configured transactional emails, such as an account welcome message.
• OpenAI: AI Assist requests, as described below.
• Map and font services: OpenStreetMap tiles and Google Fonts are requested by your browser when those resources load. These providers receive technical request information; map requests also indicate the area being displayed.
• Hosting, database and operational providers: the infrastructure needed to run the service. [Confirm deployed providers.]

Authorised administrators can manage accounts and events. Access to underlying systems is limited to people who need it for service operations. Information may also be disclosed where required by law, to handle legal claims or to protect against abuse.

5. AI Assist and your information

Using AI Assist sends your brief and selected event-editor context to OpenAI. This may include the title, description, venue text, dates, schedule, questions and visual settings. The app excludes account passwords, guestlists, invitation credentials, uploaded media and private day-of access details from automatically supplied context. Anything you type into your brief is still included.

The app does not save AI conversations as a chat history. Suggestions remain in your current editor session until discarded or applied; saved event details become part of your event record. Requests ask OpenAI not to store the response using its response-storage setting. This does not mean zero provider retention: provider processing and retention depend on the applicable OpenAI agreement and account configuration. [Confirm those arrangements before launch.]

6. Cookies and browser location

We use an essential session cookie, otd.sid, to keep account and guest sessions working. Its configured maximum lifetime is seven days; it may end earlier when you log out or access is revoked. Blocking it may prevent login and private-event access. Optional first-party website analytics runs only when you choose to allow it. You can change your choice using Analytics preferences on the public website. Browser Do Not Track and Global Privacy Control signals keep optional analytics off.

With your permission, we store an anonymous browser identifier in local storage for up to 180 days and a session identifier in tab storage, renewed after 30 minutes of inactivity. Your preference is remembered for 180 days. We measure marketing page visits, referral domains, campaign labels, device categories, link clicks, form activity, visible page time, scroll depth, performance and error categories. Raw analytics events expire after 90 days. These browser identifiers do not identify individual people.

Private event pages, galleries, account recovery links and administration pages are excluded. We do not collect form contents, URL query strings, invitation tokens, error messages or stack traces in these analytics. Country codes may be supplied by our hosting proxy; we do not store IP addresses in analytics or send them to an external geolocation service. Declining analytics does not affect essential app features.

Map tiles and Stripe checkout make requests to their respective providers. [Review their final browser-storage behaviour and any consent requirements before launch.]

If a host selects “Use my current location”, the browser asks for permission. The resulting coordinates can be used as the saved venue pin and shown to authorised guests. The host can instead enter an address or choose a map pin manually.

7. Storage, retention and deletion

Event expiry closes guest access. Gallery photos and videos are retained for 30 days after the event website closes. Hosts can download their complete gallery as a ZIP during that period, including after the website closes. The gallery page shows the deletion deadline and we send advance notices to the host. At the deadline, gallery access and new downloads stop; the scheduled cleanup deletes stored media and its older versions. A download already in progress can finish within a short time limit. Photos needed for paid print orders are held privately until dispatch or cancellation. Replaced, removed and abandoned uploads have a separate 24-hour cleanup grace period. Previously issued photo links can remain usable for up to five minutes after access changes.

The final retention schedule must set periods for accounts, event content, uploaded media, payment records, security logs and backups. [Retention periods, backup deletion times and deletion-request procedures to be confirmed.] Media cleanup depends on the scheduled worker and storage permissions being configured. Event and payment records have separate retention requirements.

We use password hashing, private media storage and access checks to protect information. No online service can guarantee complete security. Hosting regions, international transfers and the safeguards used for any restricted transfers must be confirmed for the deployed providers. [Insert actual regions, transfer arrangements and how to obtain safeguard details.]

8. Your choices and rights

Depending on the law that applies, you may have rights to access, correct, delete or obtain a copy of your information, restrict its use, or object to certain processing. Where consent is the basis, you can withdraw it without affecting earlier lawful processing. These rights have conditions and exceptions.

Hosts can update their profile name and event details. Guests can update replies while their event remains available. For other requests, contact privacy@seeyoushortly.com; for the host’s use of guest information, contact the host as well. We may need to verify identity before acting. Hosts can close their account in Account settings. This removes active account, event and guest records; media files enter the cleanup process.

You can complain to the relevant data-protection authority. If UK law applies, you can contact the Information Commissioner’s Office. [Confirm the operator’s lead authority and contact procedure.]

9. Children and policy updates

The service is intended for people able to manage an event account responsibly. Hosts should minimise children’s information and obtain the permissions required for their event. [Confirm the minimum account age, intended audience and any arrangements for children before launch.]

We will update this policy when our handling of information changes, showing the revision date above and providing additional notice where required. Read our Terms of Use for the rules for using the service.