FACTORYMORE · UPDATED 26 SEPTEMBER 2026
Data Protection and GDPR Rights
Purpose and scope
This page explains how to exercise data-protection rights in connection with FactoryMore and how those requests should be handled. The GDPR applies according to its territorial and material scope; similar rights may arise under other laws. The presence of this page does not certify the platform or replace an assessment of the processing actually carried out. Consult the Privacy Policy for the categories of information, purposes, recipients and practical controls.
Requesting access
You may ask whether personal data concerning you is being processed and request access to the relevant data and supporting information. Explain which account or activity your request concerns so it can be located. Access is not an unrestricted right to another member’s private correspondence, confidential business material or security credentials. A response may need to redact another person’s information while preserving the substance of your own information. A dashboard export is useful but may not cover every record relevant to an access request.
Correction and completion
Use Account settings to correct supported fields, and use Help Center for information you cannot edit directly. Identify the inaccurate item and the correction requested. Where a professional claim is disputed, further evidence may be needed to avoid replacing accurate information with a misleading statement. Correcting your profile does not automatically revise a message already sent to another company; a follow-up clarification may be appropriate. Where required, recipients of incorrect information should be informed of a rectification.
Erasure and account closure
A deletion request must be assessed against the purpose and lawful basis of the records concerned. Some public content may be removed while a limited record is retained for a legal obligation, security incident or claim. Closing an account does not automatically require erasing another participant’s lawful business records or an independently formed contract. If deletion is refused or limited, the relevant reason should be explained. Recovery copies and backups require controlled expiry and must not be used as an excuse for unrestricted retention or renewed marketing.
Restriction of processing
You may request restriction in circumstances such as a dispute over accuracy, an objection under review or the need to preserve information for a claim. Restriction differs from deletion: the information may remain stored while its use is limited to the applicable permitted purposes. Describe the processing you want restricted and why. Public visibility, optional analytics and account security are different functions and may require different measures. A request should be assessed at the level of the relevant activity rather than simply disabling every account feature.
Portability
Where the applicable conditions are met, you may request personal data you provided in a structured, commonly used and machine-readable format, or transmission to another controller where technically feasible. Portability does not apply to every derived score, internal security record or third-party intellectual property. The business analytics CSV/PDF feature is a separate plan feature; a legal data-subject request is not made conditional on buying a paid membership. Identity and recipient checks remain necessary before transmitting private information.
Objections and marketing withdrawal
You may object to qualifying processing based on legitimate interests and explain the particular circumstances relevant to your request. An objection to direct marketing and withdrawal of consent should be respected for the applicable channel and purpose. Essential account security or legally required recordkeeping is not automatically discontinued by a marketing opt-out. The registration marketing choice is separate from acceptance of platform terms. Contact Help Center if a withdrawal cannot be completed using an available interface control or communication link.
Consent and cookie preferences
Consent should identify a specific optional purpose and be capable of withdrawal. Use Cookie settings to review optional analytics and advertising-measurement preferences. Strictly necessary authentication and security operations are distinguished from optional measurement. Saving a consent choice is not evidence that every third-party integration has been audited. Provider behaviour, cookie inventory and the legal basis for each activity require review when a service is connected or materially changed.
Human review and automated checks
FactoryMore uses automated security checks, validation, rate limits and search or recommendation logic to operate the service. Company-document approval requires an authorised administrator; uploading a document does not automatically approve the business. If you believe an automated restriction has incorrectly affected your access, request review through Help Center with the relevant context. Do not infer from a security pass or a search position that the platform has made a complete assessment of a company or product. Any processing meeting the conditions for special automated-decision protections must be assessed under those requirements.
How to submit a request
Send a Help Center request specifying the right you wish to exercise, the account email and enough context to locate the relevant records. Never include your password, SMS code, full payment-card details or wallet recovery phrase. If you act for someone else, appropriate evidence of authority may be required. Requests about information a separate supplier received from you may also need to be directed to that supplier. FactoryMore should assist with its own processing and explain any limits rather than promise control over all independent recipients.
Identity checks and response period
For a request subject to GDPR, the usual response period is one month from receipt, subject to the applicable rules on identification, complexity and lawful extensions. Where an extension is justified, notice and the reasons should be provided within the required period. Information requested for identification should be proportionate to the risk of disclosure. A request should not be rejected merely because it uses ordinary language instead of a legal form. Any refusal, permitted fee or exception must be explained and based on the applicable requirements.
Complaints and safeguards
You may raise concerns through Help Center and, where applicable, complain to the competent data-protection authority or seek other available remedies. Private submissions should be handled by authorised people and recorded sufficiently to track the request and response. Access to verification documents and conversations must be limited to the purpose for which it is needed. Processor arrangements, international transfers, retention schedules and incident-response procedures require continuing operational review; this page does not replace those measures.
Distinguishing company data from personal data
A request may concern both a corporate profile and the people named in it. Explain whether you seek to correct business information, change your own account details or exercise a personal-data right. A business document can contain directors’ names, signatures or contact details even when its primary purpose is corporate verification. The review should focus on the information relating to an identifiable person and the applicable legal basis. A company’s wish to remove an unfavourable review is not automatically the same as an individual’s right to erase personal data.
Making a clear and proportionate request
You do not need to use a particular legal phrase to ask about your information. It helps to identify the account, approximate period, feature and type of record involved. Avoid attaching broad identity records or confidential customer lists simply to prove a point. If additional information is necessary to locate records or verify authority, the request for it should explain what is needed and why. A request can be clarified without pressuring you to abandon an applicable right or purchase a membership to exercise it.
Information about the handling of a request
A response should address the right requested and explain relevant practical limits. Where information is withheld to protect another person or a lawful exception is applied, the explanation should identify the basis without exposing the protected material. If a request covers many unrelated activities, narrowing the search can be discussed, but scope should not be reduced unilaterally merely for convenience. Correspondence about the request and the decision may be retained for accountability and dispute handling with appropriate access restrictions.
Secure delivery and representatives
Copies of personal data should be delivered through a method appropriate to their sensitivity. A request from an unfamiliar email address or a representative can require further checks before private information is disclosed. The checks should establish the relevant identity or authority without gathering disproportionate new information. If you nominate another recipient, specify the intended recipient and the scope of the disclosure clearly. A general request to share an entire account should not be treated as permission to expose another participant’s confidential attachments or credentials.
Published information and independent recipients
Where you ask for removal of public personal information, the platform should assess its own processing and any applicable duties relating to recipients. Search engine caches and copies held by independent businesses may require separate action. Members receiving inquiries can have their own responsibilities for the information they receive. FactoryMore should explain what it can change and what remains with another controller rather than promise deletion from systems it does not operate. You can request information about relevant recipient categories to help identify appropriate follow-up steps.
Corrections, restrictions and preservation of context
A record can contain both an inaccurate factual field and a historical statement of what was communicated at a particular time. Correcting the current field may be straightforward, while changing historic correspondence can require preserving the context of a dispute. Restriction may be appropriate while accuracy or another applicable issue is assessed. Information retained solely for a continuing legal or security purpose should not automatically remain available for ordinary marketing or profiling. The requested action should be evaluated record by record where necessary.
Technical measures and organisational accountability
Encryption, access checks and private storage are useful safeguards, but they do not replace purpose limitation, staff responsibilities, training and documented decisions. Access to account records, private conversations and verification documents should correspond to the task performed. New integrations should be assessed before personal information is sent to them. Operational controls should address retention, restoration from backups, provider changes and incident handling. A feature described as secure or verified must not imply independent certification or a completed legal assessment where none has taken place.
Escalation and continuing contact
If a response appears incomplete, identify the missing records or unresolved point and ask for clarification through Help Center. Preserve the request reference and earlier correspondence so the issue can be followed consistently. Where applicable, you may seek assistance from the relevant supervisory authority or other available remedies. An internal complaint process is intended to help resolve the issue; it does not prevent you from using a statutory remedy. The platform should distinguish a privacy-rights request from an ordinary technical support ticket and route it for appropriate review.