1. Who is responsible for your information
House of Vanessa is operated by ND Investments, the controller responsible for deciding why and how personal information is used for this platform. References to “we”, “us”, “our”, “the House” and “the platform” refer to that operator. Goddess Vanessa is the name used in the sub-facing service.
For privacy questions, access requests, corrections or deletion requests, contact info@houseofvanessa.com. You can also raise a request through your existing platform conversation. An active paid contract is not required to exercise a privacy right. Please use the email contact if you cannot sign in or your contract has ended.
The operator’s responsibilities are distinct from those of independent payment and gift providers. Those providers decide how to process information for their own services and explain that processing in their own notices.
2. Who this policy applies to
This policy applies to visitors to the House of Vanessa website, applicants, enrolled subs and people who contact the operator through the platform. It covers the website, application process, saved educational progress, contract acknowledgement, access-code system, sub and administrator chat, uploaded files, payment-related records and gift notifications.
It also explains relevant differences between live and sandbox testing. It does not replace an educational agreement, purchase terms, a refund policy or a provider’s privacy notice. Accepting a contract is not blanket permission for unrelated uses of your personal information. Visiting the site does not authorise publication of your private messages or media.
3. Where information comes from
Most information comes directly from you: details you type, choices you make during the application, acknowledgements you give, messages you send and files you upload. Some records are produced as the service operates, including application references, message timestamps, read positions, session expiry dates and payment status.
Square supplies payment outcomes and related transaction information. Throne may supply signed gift-purchase notifications that the platform uses to match a purchase to a sub reference. The administrator may add an approval, decline, suspension, verification response or other service decision. Hosting and storage services process technical information needed to deliver requests and keep the service working.
We do not require you to share your contacts, your entire photo library, unrelated conversations or a social-media password. A name typed into a form or a gift reference is information supplied by the person using it; it is not independent proof of identity.
Application identity: when you enter your name and email and continue, these details are saved with your application progress for Goddess to identify your entry, including unfinished applications. No typed questionnaire answers or card details are collected by the activity tracker.
4. Applications, learning preferences and agreements
The application process can hold your name, email address, selected learning path, questionnaire answers, selected entry-fee option and contract option. Questions and available answers can be changed by the operator. The information actually collected depends on the current published application, rather than an unchanging generic questionnaire.
When you submit an application, the platform saves an application reference, creation and update timestamps, your answers and a snapshot of the relevant application and agreement settings. The snapshot can include the agreement text, acceptable-use wording, selected prices, your typed signature, age confirmation, acknowledgements and the time of acknowledgement. It allows the operator to understand what you saw and accepted at the time.
Typing your name records an acknowledgement; it is not biometric identity verification. Saved historical agreement records can remain even when current wording or prices change. Where educational progress is enabled, completed lesson identifiers are stored against your enrolment so the platform can resume your learning state.
Providing required application information is necessary to assess and administer the service you request. You may choose not to proceed, but the platform cannot create a complete application or agreement without its required fields.
5. Accounts, codes and contract-linked access
Sub access records include an internal identifier, the linked application identifier, name, email, account status, creation time and access-code expiry. Codes are issued on the platform. A hash of a sub access code is stored for validation; the system does not use that hash as a displayable copy of the original code.
Sub codes remain reusable until replacement, suspension or the applicable paid contract’s end. Issuing a replacement revokes the previous code. A new sign-in rotates the chat session. Codes and sessions cannot extend beyond an applicable paid contract’s end. Session cookies and server-side session records allow the service to recognise a signed-in sub without repeatedly asking for the code.
Replacement-code requests and the administrator’s approval or decline are saved so requests can be reviewed and a replacement collected. Account suspension, logout or code rotation may end access. These access controls do not, by themselves, erase applications, agreement snapshots, chat history, uploaded media or payment records.
Administrator sign-in and security settings are separate from sub access. Private security credentials and recovery information are not supplied to subs or included in normal conversation responses.
6. Private conversations and conversation activity
The platform stores the text of messages sent between a sub and Goddess Vanessa, including native phone emojis. Message records include the conversation identifier, sender role, timestamp and ordering information. Attachments are linked to messages. Retries use identifiers intended to avoid creating duplicate messages after a connection problem.
The service also holds read positions, typing indicators and activity information used to show that a conversation is active and whether messages have been read. A message marked read does not prove the recipient understood it or agreed with it. Typing and presence indicators are operational signals, not a detailed guarantee about someone’s availability.
The sub can view their authorised conversation. The operator can view and respond through the administrator area. Conversations are not public posts and are not intended to be visible to other subs. However, this is not a Telegram Secret Chat or an end-to-end encrypted service: the platform operator and authorised technical services can process stored content where necessary to provide, maintain or protect the service.
Please avoid putting passwords, payment-card details, government-document numbers or information about someone else into chat. The operator may need to retain relevant correspondence when investigating a support issue, a dispute or misuse.
7. Photos, videos, voice notes and attachments
When you select and send an attachment, the platform receives the file itself and records its filename, detected media type, size, upload identifier, conversation or request association, sender role and timestamp. Voice notes recorded through the platform are stored as audio files when you send them. The service does not receive the contents of files you merely browse on your device without selecting and uploading them.
Photos and videos can reveal faces, voices, surroundings, documents, location clues and other personal details. Files may also contain embedded metadata added by your device or editing software, including location or capture information. The current upload flow does not promise to strip that metadata. Remove identifying details and location metadata before sharing if they are unnecessary.
Private attachments are held in restricted storage. Access checks and temporary signed links are used to deliver authorised files. A recipient who legitimately receives a file may still save it, take a screenshot or record playback. No technical measure can guarantee that content already delivered to a recipient cannot be copied.
The current attachment limit is 50 MB per file, with a 1 GB allowance associated with a sub. In-platform voice recording is limited to five minutes. File size limits are operational limits, not retention periods. A rejected or interrupted upload may temporarily leave a staging record or file pending cleanup. Administrator-selected chat backgrounds and their pink or burgundy overlay settings are also stored for the relevant conversation.
8. Sensitive and third-party information
Some information has additional legal protection, including health information, racial or ethnic origin, religious beliefs, sexual orientation and information about a person’s sex life. A photograph or voice recording is not automatically biometric identification data merely because it contains a face or voice; how it is processed matters.
The application does not require you to disclose those sensitive categories simply to choose a learning path or buy access. Do not send intimate media, medical records, identity documents or other highly sensitive information unless a specific necessary process has been explained to you, together with the appropriate legal basis and safeguards. This policy does not itself establish explicit consent for all sensitive material you might volunteer.
If such information is received unexpectedly, the operator must assess whether it is necessary and whether there is an appropriate legal basis to retain or otherwise use it. Unnecessary sensitive material should be removed or restricted as appropriate. This statement is not a claim that every uploaded file is automatically inspected, classified or deleted.
Only share another person’s image, voice, messages or personal details when you have a valid reason and the right to do so. If you believe your information was shared without permission, use the privacy contact above to identify the content without sending additional sensitive copies unnecessarily.
9. Square payments
Square is used for the entry fee and the separate contract payment. Card entry is handled by Square’s payment interface or payment components. Our application does not store your full card number or card security code. We do not ask you to send card details through chat.
The platform stores payment-related information needed to connect a transaction with an application: the payment stage, selected plan and price snapshot, internal references, order and payment identifiers, payment status, payment timestamps, receipt links, relevant provider-update information and contract expiry where applicable. Payment reconciliation and signed provider notifications are used to determine whether a transaction completed; returning to the site alone is not treated as proof of payment.
Square may independently collect payment credentials, billing information, device information and other information needed for processing, fraud prevention, compliance and its own services. Its notice governs those activities. The exact information collected by Square can depend on the payment method and checkout process.
A refund, disputed transaction or incomplete payment can affect access and may require review. Records needed to reconcile money received or resolve a payment dispute may remain after access ends or an account is removed. For information about Square’s own processing, see Square’s Privacy Notice.
10. Throne gifts, sub references and notifications
The chat includes a catalogue linked to the operator’s Throne wishlist. Selecting an item takes you to Throne or its purchase interface. Throne handles the purchase and may collect purchaser, delivery, payment and gift information under its own terms and privacy notice. A platform gift card is not itself confirmation that money has been received.
To make gifts recognisable, the integration uses a sub-name reference rather than only a long opaque code. That reference can identify you to the recipient and to Throne. It should not contain a private email, access code, address or sensitive personal description. Matching may involve an additional identifier where names are not unique.
The platform can store a purchase reference, item or gift description, provider notification identifiers, completion status and timestamps. A valid signed success notification can be associated with a conversation and displayed as a gift message. Notification availability and timing depend on Throne. An abandoned purchase, cancellation or failure is not always reported by the provider, so the absence of a success message does not prove which of those events occurred.
Only relevant authorised notifications should be used to update the platform. Gift references and webhook records are service records, not a public sub directory. Read Throne’s privacy information before providing details on its service.
11. Verification and identity-related information
Government identity checks are not a required step in the current sub application described by this policy. The platform contains functionality for verification requests, administrator responses and associated videos where a verification process is actually used. Those records can include request identifiers, status, submitted content, response text and timestamps.
The fact that a feature exists does not mean every applicant must supply identity documents or that all applicants are independently identity-verified. Age confirmation currently records an acknowledgement. Square’s verification of the payment recipient is a separate provider process and is not a sub identity check performed by this platform.
If the operator introduces a new identity, biometric or age-verification provider, the collection requirements, recipient, lawful basis and retention arrangements must be explained before the new information is requested. Do not upload passports or similar documents in an ordinary chat in anticipation of a future process.
12. Technical information and security records
Website delivery and security can involve IP addresses, request times, requested paths, browser or device information, error records, request references, login-attempt information and rate-limit counters. Some information is processed by the hosting provider rather than written into an application profile. A security record may use a hash or internal identifier instead of directly displaying a raw value.
We use technical information to serve pages and files, maintain sessions, investigate failures, detect misuse and limit repeated requests. Hashing an identifier does not necessarily make all related records anonymous: records can remain personal information when they can be linked to an individual.
We do not need precise device location to provide the application or chat. Location information may nevertheless be exposed by information you send, file metadata, or a provider’s independent processing. We do not describe the service as immune to attacks or guarantee uninterrupted availability.
13. Why information is used and the applicable legal bases
Information is used for the particular service or operational purpose for which it is needed. Under the UK GDPR, ordinary personal-data processing requires an appropriate lawful basis. Different purposes can have different bases; accepting this notice is not a substitute for identifying them.
| Purpose | Relevant information | Ordinary lawful basis |
|---|---|---|
| Take steps at your request and administer the service | Application details, learning choices, agreement acknowledgement, enrolment and access records | Steps before entering a contract and performance of a contract, where the processing is necessary for that purpose |
| Deliver private chat and requested media features | Messages, uploaded files, conversation associations and essential activity state | Performance of the requested service where necessary; otherwise an assessed legitimate interest in operating the requested communication feature |
| Process and reconcile payments and gifts | Selected prices, transaction references, provider outcomes, receipts and gift references | Contract administration; legitimate interests in accurate reconciliation; applicable legal obligations for relevant records |
| Protect access and investigate misuse | Session records, code hashes, rate limits, operational logs and relevant incident information | Legitimate interests in protecting users and the service, balanced against individual rights |
| Respond to rights requests and legal requirements | Contact details, request information and proportionate verification records | Compliance with applicable legal obligations |
| Optional processing that requires consent | Only the information described for that particular optional activity | Consent, obtained separately where required and capable of being withdrawn |
A legitimate-interest basis requires the operator to consider necessity, proportionality and the effect on you. It does not override your rights or justify unrelated reuse. Where additional protected information is involved, an appropriate additional legal condition is needed. We do not treat a purchase, a typed signature or an ordinary chat message as universal consent to marketing, publicity or sensitive-data processing.
15. International processing
Hosting, storage, payment and gift services may operate internationally. The location of a database region does not necessarily describe every support, backup, logging or payment-processing location. This notice does not claim that all personal information stays within the United Kingdom.
Where a transfer is restricted under applicable data-protection law, the operator must ensure an appropriate lawful transfer arrangement applies. Depending on the recipient and circumstances, that can involve an adequacy arrangement or approved contractual safeguards together with the necessary assessments. The arrangement should be established from the applicable provider contract, rather than assumed from the fact that a provider is well known.
You can ask the privacy contact for information about applicable transfer safeguards for your data. Provider notices and contractual privacy information also explain their own international operations.
16. How long information remains
Different records serve different purposes. Session and access-code expiry are security deadlines, not general deletion deadlines. A contract ending stops applicable access but does not automatically remove your application, agreement snapshots, chat history, attachments, gift notifications or payment records.
The current platform does not have a blanket automatic deletion schedule for completed applications, conversations or uploaded media. Those records remain until removed through an authorised process. In deciding what may continue to be held, the operator must consider whether it is still necessary for the service, a support matter, a dispute, an accounting requirement or another identified lawful purpose. An “infinite” access option is not, by itself, justification to keep every piece of information forever.
Failed upload reservations expire and there is maintenance functionality for removing old staging files, expired sessions and expired rate-limit records. Actual cleanup depends on maintenance being run. An expired record may remain stored for a period even though it can no longer be used for access.
Deleting a conversation or sub chat record does not necessarily remove the separate application or historical agreement record. Payment providers retain their own records independently. Copies in backups, provider logs or temporary caches can follow the relevant system’s own retention cycle and may not disappear at the exact instant an application record is deleted.
You can ask what remains about you and request erasure where applicable. The operator should identify any specific legal or dispute-related reason for refusing or postponing removal of particular information rather than using a general claim that everything must be retained.
Contact details, private support notes and activity counts
Name and email are entered at the final contract review and signing stage. The Basic/Advanced entry selector does not collect an additional email address. Administrator-approved contract invitations use a separate private application session. Previously supplied contact details remain private. Providing contact details does not verify them or opt you into marketing. Earlier applications may not contain a phone number. Goddess can keep relevant private notes attached to a Sub profile; these notes are accessible only through authenticated administrator tools.
For operational activity counts we use a random tab identifier, hashed on the server, and a short-lived heartbeat. The administrator sees approximate active visitor tabs, visitor tabs today and the names of signed-in Subs active within the last 90 seconds. Private tabs may count separately. We do not store IP addresses, browsing history or message content in these visitor records. Visitor records expire after 24 hours. Closing or hiding a tab stops active updates. Rate limits use hashed network identifiers for abuse prevention separately from these counts.
18. Microphone, file and notification permissions
Vanessa can opt in to browser alerts for incoming messages, media and Throne gift confirmations. Alerts are discreet by default. Enabling previews can display the sub’s name, message excerpt, attachment name or image on the device’s notification screen, including a lock screen depending on device settings. Notification and preview preferences are stored in that browser and can be disabled from Conversations or browser settings. No private conversations or attachments are cached by the notification service worker.
Recording a voice note requires microphone permission from your browser or device. Recording starts through the recording control; sending the resulting audio is a separate action. You can stop recording, remove the selected note before sending, or deny microphone permission and attach an existing supported audio file instead.
File selection provides access to the selected file, not unrestricted permission to read every file on your device. Permissions can be changed in browser or device settings. The current chat feature does not require continuous microphone access, background location tracking or an address-book upload to function.
Device-level permissions and an appropriate legal basis for processing are separate questions. Granting a microphone permission does not authorise unrelated recording, publication or indefinite retention of everything you say.
Approximate live visitor locations
The dashboard shows approximate city and country from the hosting provider’s IP-based location headers for recently active visits. It does not request device GPS or record a precise location, postal address or coordinates. Location details are removed after the active 90-second window on the next visit update; aggregate visit counts remain for the day. VPNs and network routing can make the location inaccurate.
19. Security and discretion
The platform uses controls such as server-side authorisation, private storage, session expiry, contract-bound access-code validation, signed provider notifications, rate limits and secure transport. Sensitive application operations are checked on the server rather than relying only on whether a button is visible.
These measures reduce risk but cannot guarantee that a website will never be compromised, that a recipient will never copy content, or that a provider will never have an outage. “Private” means access is restricted within the service; it does not mean information is invisible to the operator or end-to-end encrypted between devices.
Protect your email, device and access code, avoid using a shared browser profile for private conversations, and sign out when finished. Do not send login credentials through chat. If you suspect unauthorised access or disclosure, contact the operator promptly and include enough context to identify the issue without unnecessarily forwarding sensitive media.
If a personal-data breach occurs, the operator must assess it and make any notifications required by applicable law. The existence of a security control does not remove those obligations.
Application step activity
While you fill in an application, the private Goddess dashboard can show the current step, when you started and whether you are recently active. Activity is linked to the existing application continuity cookie. Step updates do not collect typed answers, keystrokes, card data or precise location. Applicants are shown anonymously during the earlier steps. The name and email supplied at the final contract review stage can then be shown alongside progress and server-confirmed signing/payment status. Step activity is kept for up to 30 days and removed on subsequent new application starts. It is visible only to the administrator and is not shared with an external analytics service.
20. Your data-protection rights
Depending on the circumstances and the legal basis for processing, you may have the right to obtain information about processing and a copy of your personal information; correct inaccurate information; request erasure; restrict processing; object to processing based on legitimate interests; and receive eligible information in a portable format. You can withdraw consent for a particular activity where that activity relies on consent.
Withdrawing consent does not make earlier lawful processing unlawful. Some information may still be needed for a different valid purpose, which must be explained. Rights are not all absolute: an applicable exemption, another person’s rights, a legal obligation or a live legal claim can affect the response.
Deleting your account is not the only way to exercise a right. You can ask about a particular message, file or record. Likewise, cancelling a contract or clearing a cookie is not automatically a complete erasure request. Requests should be handled on their substance rather than requiring an exact legal phrase.
The platform does not provide a promise that every rights request is automated or can be completed immediately through a dashboard button. The operator is responsible for assessing and responding to requests.
21. How to make a privacy request
Email info@houseofvanessa.com or use your existing platform conversation. Explain what you want to access, correct, remove or understand. Where available, provide your application reference, the email you used, or enough information to locate the relevant conversation. You do not need to publish the request publicly.
The operator may ask for proportionate information to confirm that the request concerns your records, particularly before disclosing a private conversation. Do not send an identity document unless it is genuinely needed and a suitable method has been explained. The response should not disclose another person’s information unnecessarily.
Under the UK GDPR, requests normally require a response within one month, subject to applicable rules and extensions for relevant circumstances. If an extension or exception applies, the operator should explain it. Requests are generally free, although applicable rules can permit a fee or refusal in limited cases involving manifestly unfounded or excessive requests.
If you cannot use chat because access has ended, use the public privacy email. Exercising your rights does not require another payment.
22. People under 18
This platform is intended for adults aged 18 and over. The application records an age confirmation; that acknowledgement should not be confused with a completed independent identity or age check. A person under 18 should not apply, buy access or upload personal media.
If you believe information relating to someone under 18 has been submitted, contact the operator. The operator should assess the report, stop inappropriate continued use and consider appropriate removal and any necessary legal or safeguarding action. Please do not circulate the person’s images or documents while making the report.
23. Applications and automated access decisions
The administrator can approve or decline relevant requests, issue codes, respond to subs and suspend an account. The software also makes routine access checks using saved account status, payment status, expiry and security limits. For example, it can refuse an expired code or prevent access after a paid contract ends.
Those checks do not analyse your personality or the meaning of a voice note to decide eligibility. They are not a claim that every application decision is made by a human, because some access decisions are automatic. If a payment or expiry record appears incorrect, contact the operator so the underlying record and provider outcome can be reviewed.
There is no general content-analysis or automated transcription feature described in the current chat flow. Any future profiling, AI analysis or materially different automated decision process would require its own privacy assessment and explanation.
24. Sandbox and testing
The sandbox site is used to test application and payment flows with separate payment settings and separate application database records. A sandbox payment is not a live payment and does not purchase access to the live platform. Sandbox accounts do not automatically become live sub accounts.
Testing is not an exemption from privacy obligations. The operator and technical providers can still process information typed into a test site. Use invented application details and harmless media for tests wherever possible. Do not enter real card details into a sandbox checkout or upload identity documents to demonstrate that an attachment control works.
Some underlying technical infrastructure may be shared even where application records are separated. This policy therefore does not describe a sandbox as a completely separate physical system. Test records should be assessed and removed when they are no longer needed, through an authorised process.
25. Other websites and independent providers
Links can take you away from this website, including Square receipts, Throne purchases and resources linked from educational material. Those services can receive information from your browser and collect details you choose to provide. Their policies and controls apply on their pages.
Before entering private details, check the destination and provider notice. A link included in this platform is not a guarantee that an external service has identical privacy, retention or security arrangements. A change to your settings here will not necessarily change settings or delete records held by an independent provider.
Useful provider information includes Vercel’s privacy policy, Supabase’s privacy policy, Square’s notice linked above, and Throne’s privacy information. Contact an independent provider directly where a request concerns information it holds for its own purposes.
26. Changes, questions and complaints
This policy should be updated when the platform changes how it collects, uses or shares personal information. The date above identifies this version. A new notice does not, on its own, authorise an incompatible new use of records already collected. Material changes should be brought to users’ attention in an appropriate way, and any necessary new consent obtained separately.
If something in the service appears inconsistent with this notice, contact info@houseofvanessa.com and identify the issue. You may complain to the operator and also have the right to raise concerns with the relevant data-protection authority. In the United Kingdom this is the Information Commissioner’s Office (ICO). Other authorities may be relevant depending on your location and the applicable law.
You do not have to waive a privacy right to use the platform, and contacting the operator first does not remove your right to contact an authority.