Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/iovdvorfeostory/public_html/qip/wp-includes/functions.php on line 6131

Deprecated: acf_get_value(): Optional parameter $post_id declared before required parameter $field is implicitly treated as a required parameter in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/advanced-custom-fields-pro/includes/acf-value-functions.php on line 54

Deprecated: acf_update_value(): Optional parameter $value declared before required parameter $field is implicitly treated as a required parameter in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/advanced-custom-fields-pro/includes/acf-value-functions.php on line 166

Deprecated: acf_update_value(): Optional parameter $post_id declared before required parameter $field is implicitly treated as a required parameter in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/advanced-custom-fields-pro/includes/acf-value-functions.php on line 166

Deprecated: Creation of dynamic property ACF::$fields is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/advanced-custom-fields-pro/includes/fields.php on line 136

Deprecated: Creation of dynamic property ACF::$locations is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/advanced-custom-fields-pro/includes/locations.php on line 130

Deprecated: Creation of dynamic property ACF::$json is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/advanced-custom-fields-pro/includes/json.php on line 184

Deprecated: Creation of dynamic property acf_loop::$loops is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/advanced-custom-fields-pro/includes/loop.php on line 26

Deprecated: Creation of dynamic property ACF::$loop is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/advanced-custom-fields-pro/includes/loop.php on line 270

Deprecated: Creation of dynamic property ACF::$revisions is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/advanced-custom-fields-pro/includes/revisions.php on line 413

Deprecated: Creation of dynamic property acf_validation::$errors is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/advanced-custom-fields-pro/includes/validation.php on line 26

Deprecated: Creation of dynamic property ACF::$validation is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/advanced-custom-fields-pro/includes/validation.php on line 212

Deprecated: ACF_Ajax::set(): Optional parameter $key declared before required parameter $value is implicitly treated as a required parameter in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/advanced-custom-fields-pro/includes/ajax/class-acf-ajax.php on line 76

Deprecated: Creation of dynamic property acf_form_customizer::$preview_values is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/advanced-custom-fields-pro/includes/forms/form-customizer.php on line 26

Deprecated: Creation of dynamic property acf_form_customizer::$preview_fields is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/advanced-custom-fields-pro/includes/forms/form-customizer.php on line 27

Deprecated: Creation of dynamic property acf_form_customizer::$preview_errors is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/advanced-custom-fields-pro/includes/forms/form-customizer.php on line 28

Deprecated: Creation of dynamic property ACF::$form_front is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/advanced-custom-fields-pro/includes/forms/form-front.php on line 603

Deprecated: Creation of dynamic property acf_form_widget::$preview_values is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/advanced-custom-fields-pro/includes/forms/form-widget.php on line 34

Deprecated: Creation of dynamic property acf_form_widget::$preview_reference is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/advanced-custom-fields-pro/includes/forms/form-widget.php on line 35

Deprecated: Creation of dynamic property acf_form_widget::$preview_errors is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/advanced-custom-fields-pro/includes/forms/form-widget.php on line 36

Deprecated: Return type of WPCF7_FormTag::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/contact-form-7/includes/form-tag.php on line 396

Deprecated: Return type of WPCF7_FormTag::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/contact-form-7/includes/form-tag.php on line 388

Deprecated: Return type of WPCF7_FormTag::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/contact-form-7/includes/form-tag.php on line 382

Deprecated: Return type of WPCF7_FormTag::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/contact-form-7/includes/form-tag.php on line 400

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/contact-form-7/includes/mail.php on line 221

Deprecated: Return type of WPCF7_Validation::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/contact-form-7/includes/validation.php on line 78

Deprecated: Return type of WPCF7_Validation::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/contact-form-7/includes/validation.php on line 72

Deprecated: Return type of WPCF7_Validation::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/contact-form-7/includes/validation.php on line 59

Deprecated: Return type of WPCF7_Validation::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/contact-form-7/includes/validation.php on line 82

Deprecated: Creation of dynamic property Cookie_Law_Info_Cli_Policy_Generator::$plugin_name is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/cookie-law-info/admin/modules/cli-policy-generator/cli-policy-generator.php on line 190

Deprecated: Use of "self" in callables is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/cookie-law-info/includes/class-cookie-law-info.php on line 669

Deprecated: Use of "self" in callables is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/cookie-law-info/includes/class-cookie-law-info.php on line 669

Deprecated: Use of "self" in callables is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/cookie-law-info/includes/class-cookie-law-info.php on line 669

Deprecated: Use of "self" in callables is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/cookie-law-info/includes/class-cookie-law-info.php on line 669

Deprecated: Use of "self" in callables is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/cookie-law-info/includes/class-cookie-law-info.php on line 669

Deprecated: Use of "self" in callables is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/cookie-law-info/includes/class-cookie-law-info.php on line 669

Deprecated: Use of "self" in callables is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/cookie-law-info/includes/class-cookie-law-info.php on line 669

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the cookie-law-info domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/iovdvorfeostory/public_html/qip/wp-includes/functions.php on line 6131

Deprecated: mtphr_dnt_ticker_class(): Optional parameter $id declared before required parameter $meta_data is implicitly treated as a required parameter in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/ditty-news-ticker/inc/helpers.php on line 171

Deprecated: mtphr_dnt_ticker_class(): Optional parameter $class declared before required parameter $meta_data is implicitly treated as a required parameter in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/ditty-news-ticker/inc/helpers.php on line 171

Deprecated: get_mtphr_dnt_ticker_class(): Optional parameter $id declared before required parameter $meta_data is implicitly treated as a required parameter in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/ditty-news-ticker/inc/helpers.php on line 178

Deprecated: get_mtphr_dnt_ticker_class(): Optional parameter $class declared before required parameter $meta_data is implicitly treated as a required parameter in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/ditty-news-ticker/inc/helpers.php on line 178

Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/map-multi-marker/map-marker.php on line 72

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the post-smtp domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/iovdvorfeostory/public_html/qip/wp-includes/functions.php on line 6131

Deprecated: Creation of dynamic property PowerpackElements\Classes\PP_Elements_WPML::$type is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/powerpack-elements/classes/class-pp-wpml.php on line 7

Deprecated: Search_Filter_Taxonomy_Object_Walker::__construct(): Optional parameter $defaults declared before required parameter $options_obj is implicitly treated as a required parameter in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/search-filter-pro/public/includes/class-search-filter-taxonomy-object-walker.php on line 22

Deprecated: Search_Filter_Taxonomy_Object_Walker::display_element(): Optional parameter $depth declared before required parameter $output is implicitly treated as a required parameter in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/search-filter-pro/public/includes/class-search-filter-taxonomy-object-walker.php on line 31

Deprecated: Search_Filter_Wp_Data::get_taxonomy_term_by(): Optional parameter $by declared before required parameter $taxonomy_name is implicitly treated as a required parameter in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/search-filter-pro/includes/class-search-filter-wp-data.php on line 115

Deprecated: Creation of dynamic property Search_Filter_Post_Cache::$cache_table_name is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/search-filter-pro/includes/class-search-filter-post-cache.php on line 32

Deprecated: Creation of dynamic property Search_Filter_Post_Cache::$term_results_table_name is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/search-filter-pro/includes/class-search-filter-post-cache.php on line 33

Deprecated: Creation of dynamic property Search_Filter_Post_Cache::$table_name_options is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/search-filter-pro/includes/class-search-filter-post-cache.php on line 34

Deprecated: Creation of dynamic property Search_Filter_Post_Cache::$option_name is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/search-filter-pro/includes/class-search-filter-post-cache.php on line 35

Deprecated: Creation of dynamic property wfPOMO_FileReader::$is_overloaded is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/wordfence/waf/pomo/streams.php on line 65

Deprecated: Creation of dynamic property wfPOMO_FileReader::$_pos is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/wordfence/waf/pomo/streams.php on line 66

Deprecated: Creation of dynamic property wfPOMO_FileReader::$_f is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/wordfence/waf/pomo/streams.php on line 185

Deprecated: Creation of dynamic property wfMO::$_gettext_select_plural_form is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/wordfence/waf/pomo/translations.php on line 337

Deprecated: Creation of dynamic property wfLog::$loginsTable is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/wordfence/lib/wfLog.php on line 91

Deprecated: Creation of dynamic property wfLog::$blocksTable is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/wordfence/lib/wfLog.php on line 92

Deprecated: Creation of dynamic property wfLog::$lockOutTable is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/wordfence/lib/wfLog.php on line 93

Deprecated: Creation of dynamic property wfLog::$throttleTable is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/wordfence/lib/wfLog.php on line 94

Deprecated: Creation of dynamic property wfLog::$statusTable is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/wordfence/lib/wfLog.php on line 95

Deprecated: Creation of dynamic property wfLog::$ipRangesTable is deprecated in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/wordfence/lib/wfLog.php on line 96

Deprecated: YoastSEO_Vendor\GuzzleHttp\Promise\queue(): Implicitly marking parameter $assign as nullable is deprecated, the explicit nullable type must be used instead in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/wordpress-seo/vendor_prefixed/guzzlehttp/promises/src/functions.php on line 22

Deprecated: YoastSEO_Vendor\GuzzleHttp\Promise\each(): Implicitly marking parameter $onFulfilled as nullable is deprecated, the explicit nullable type must be used instead in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/wordpress-seo/vendor_prefixed/guzzlehttp/promises/src/functions.php on line 304

Deprecated: YoastSEO_Vendor\GuzzleHttp\Promise\each(): Implicitly marking parameter $onRejected as nullable is deprecated, the explicit nullable type must be used instead in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/wordpress-seo/vendor_prefixed/guzzlehttp/promises/src/functions.php on line 304

Deprecated: YoastSEO_Vendor\GuzzleHttp\Promise\each_limit(): Implicitly marking parameter $onFulfilled as nullable is deprecated, the explicit nullable type must be used instead in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/wordpress-seo/vendor_prefixed/guzzlehttp/promises/src/functions.php on line 323

Deprecated: YoastSEO_Vendor\GuzzleHttp\Promise\each_limit(): Implicitly marking parameter $onRejected as nullable is deprecated, the explicit nullable type must be used instead in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/wordpress-seo/vendor_prefixed/guzzlehttp/promises/src/functions.php on line 323

Deprecated: YoastSEO_Vendor\GuzzleHttp\Promise\each_limit_all(): Implicitly marking parameter $onFulfilled as nullable is deprecated, the explicit nullable type must be used instead in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/wordpress-seo/vendor_prefixed/guzzlehttp/promises/src/functions.php on line 338

Deprecated: YoastSEO_Vendor\Symfony\Component\DependencyInjection\Container::__construct(): Implicitly marking parameter $parameterBag as nullable is deprecated, the explicit nullable type must be used instead in /home/iovdvorfeostory/public_html/qip/wp-content/plugins/wordpress-seo/vendor_prefixed/symfony/dependency-injection/Container.php on line 60

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpcf7-redirect domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/iovdvorfeostory/public_html/qip/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the mbsocial domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/iovdvorfeostory/public_html/qip/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/iovdvorfeostory/public_html/qip/wp-includes/functions.php on line 6121
Privacy Policy - Q Investment Partners

Privacy Policy

Q Investment Partners Fund Privacy Notice

The purpose of this notice is to provide you with information on our use of your personal data in accordance with the Data Protection Law, 2017 (the “DPL”). In this document, “we”, “us” and “our” refers to the Q Investment Partners (Single Asset Real Estate Private Equity) Fund SPC (the “Fund”), QIP Investment Partners Pte. Limited (the “Investment Manager”) and its or their affiliates and/or delegates.

Our Approach to Privacy

Q Investment Partners Pte Limited operates and owns www.q-investmentpartners.com (the “Site”). We are committed to protecting your privacy in accordance with its obligations under the Personal Data Protection Act 2012 (PDPA) and the General Data Protection Regulation (GDPR). When you access and use this website, you agree to be legally bound by our terms and conditions as well as our privacy policy.

Investor Data

By virtue of making an investment in the Fund and your associated interactions with us (including any subscription, capital commitment or capital contribution, as the case may be (whether past, present of future), including the recording of electronic communications or phone calls where applicable) or by virtue of you otherwise providing us with personal information on individuals connected with you as an investor (for example directors, trustees, employees, representatives, shareholders, investors, clients, beneficial owners or agents), you will provide us with certain personal information which constitutes personal data within the meaning of the DPL (“Investor Data”). We may also obtain Investor Data from other public sources.

Investor Data includes, without limitation, the following information relating to you and/or any individuals connected to you as an investor: name, residential address, email address, contact details, corporate contact information, signature, nationality, place of birth, date of birth, tax identification, credit history, correspondence records, passport number, bank account details, source of funds details and details relating to your investment activity.

In our use of Investor Data, the Fund will be characterised as a “data controller” for the purposes of the DPL. The Fund’s affiliates and delegates may act as “data processors” for the purposes of the DPL.

Who this Affects

If you are a natural person, this will affect you directly. If you are a corporate investor (including, for these purposes, legal arrangements such as trusts or exempted limited partnerships) that provides us with Investor Data on individuals connected to you for any reason in relation to your investment with us, this will be relevant for those individuals, and you should transmit this document to such individuals or otherwise advise them of its content.

How We May Use Your Personal Data

The Fund, as the data controller, may collect, store, and use Investor Data for lawful purposes, including, in particular:

(i) where this is necessary for the performance of our rights and obligations under the Subscription Agreement and/or the constitutional and operational documents of the Fund;

(ii) where this is necessary for compliance with a legal and regulatory obligation to which the Fund is subject (such as compliance with anti-money laundering and FATCA/CRS requirements); and/or

(iii) where this is necessary for the purposes of our legitimate interests and such interests are not overridden by your interests, fundamental rights, or freedoms.

Additionally, Tricor IAG Fund Administration (Singapore) Pte. Limited (the “Administrator”), may use Investor Data, for example to provide its services to the Fund or to discharge the legal or regulatory requirements that apply directly to it or in respect of which the Fund relies upon the Administrator, but such use of Investor Data by the Administrator will always be compatible with at least one of the aforementioned purposes for which we process Investor Data.

The Administrator may handle Investor Data set out in its privacy notice, which is available at https://www.tricorglobal.com/privacy-policy/.

Should we wish to use Investor Data for other specific purposes (including, if applicable, any purpose that requires your consent), we will contact you.

Why We May Transfer Your Personal Data

In certain circumstances we and/or our authorised affiliates or delegates may be legally obliged to share Investor Data and other information with respect to your interest in the Fund with the relevant regulatory authorities such as the Cayman Islands Monetary Authority or the Tax Information Authority. They, in turn, may exchange this information with foreign authorities, including tax authorities.

We anticipate disclosing Investor Data to the following parties who provide services to the Fund and their respective affiliates (which may include certain entities located outside the Cayman Islands or the European Economic Area), who will process your personal data on our behalf:

1. Tricor IAG Fund Administration (Singapore) Pte. Limited [1]

The Data Protection Measures We Take

Any transfer of Investor Data by us or our duly authorised affiliates and/or delegates outside of the Cayman Islands shall be in accordance with the requirements of the DPL.

We and our duly authorised affiliates and/or delegates shall apply appropriate technical and organisational information security measures designed to protect against unauthorised or unlawful processing of Investor Data, and against accidental loss or destruction of, or damage to, Investor Data.

We shall notify you of any Investor Data breach that is reasonably likely to result in a risk to the interests, fundamental rights or freedoms of either you or those data subjects to whom the relevant Investor Data relates.

Getting In Touch

Should you have any queries or wish to discuss your data protection rights with us, please contact our data protection team at contact@q-investmentpartners.com.

[1] This list should be tailored following consultation with the client and should include any person or entity to whom they anticipate investor personal data being transferred in connection with the operation of the fund – i.e. if any data that can identify an individual (and which is technically in the control of the fund) is being passed to a service provider, that service provider should be listed where indicated. If data is going to be passed to services providers which does not identify individuals, then such service providers need not be listed. Note further that, for any service provider included in this list, the fund should ensure appropriate data processing agreements are in place providing requisite assurances.

blank

Let’s Talk