Severity: 8192
Message: Return type of CI_Session_files_driver::open($save_path, $name) should either be compatible with SessionHandlerInterface::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 132
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 292
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 166
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 235
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 315
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 356
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 282
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: Warning
Message: session_set_cookie_params(): Session cookie parameters cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 294
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 304
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 314
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 315
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 316
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 317
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 375
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: Warning
Message: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 110
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: Warning
Message: session_start(): Session cannot be started after headers have already been sent
Filename: Session/Session.php
Line Number: 143
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
WhatsApp, the social messaging app has recently rolled out a new privacy policy which is supposed to be live from 8th February 2021.
But this update in privacy had raised many eyebrows and caused havoc in the social space regarding people’s safety of private data in the online space. This also led to the boom of another messaging app Signal, which has shot up as one of the most downloaded apps in the app store.
Post declaration of the new privacy update by Facebook-owned WhatsApp, people had raised concerns about their privacy and exposure of their family and friends data from WhatsApp to the public domain at Facebook.
However, in the midst of all this commotion, WhatsApp has released a detailed blog post which clarifies that the new update will not share private data of users or any sensitive information regarding location with Facebook. The blog post further clarified that only some of the business conversations will be readable by Facebook to be used for better advertising. The WhatsApp groups’ data will also remain private to the users and will not be shared for Facebook ads.
On their official Twitter handle, WhatsApp also shared that the new privacy update will not keep any record of the calls or message logs of its app users. They will not see or hear any user’s calls as well. There will be complete transparency from Whatsapp about how they collect and use the data of their users.
The data which will be shared by its parent company, Facebook will mostly comprise of the user’s account registration information, i.e. the phone number, service-related information, transaction data, and the way users interact with other businesses on the platform. Other data which will be collected by WhatsApp includes information about the mobile device, IP address the details mentioned in the “Information We Collect” section of their website’s Privacy Policy.
Post this disclosure by WhatsApp, it is predicted that users will get some relief in regards to their data privacy concern and they would need to accept the new privacy policy before 8th February, 2021 to continue using WhatsApp.
12-01-2021
Email: info@imciindia.org
Telephone: +91 9650304949.
Copyright © 2023 Institute of Marketing Communications India (IMCI®) . Trademark duly registered under The Department of Industrial Policy and Promotion Ministry of Commerce & Industry, Government of India. Trademarks are the property of the owner. All Rights Reserved
