From: Spencer Scheer Date: October 10, 2016 Client Alert: From the Scheer Law Group:
( Disclaimer): The following bulletin refers to legal issues subject to developing case law or regulatory oversight. In the event that you encounter issues covered in this bulletin, you should review the appropriate response with counsel experienced in this area of law and should update the status of any legislation, regulation or case law mentioned.. The intention of SLG is to give an overview of the subject covered and to highlight trends that are emerging, not to provide advice applicable to any particular case. No permission for the general public to use this Outline is granted by SLG
Subject: California SB 1150 (Survivors Bill of Rights) Passed.
As if you did not have enough regulatory concerns, you can now add another to the “pile”. On September 29, 2016, SB 1150 was chaptered and signed into law. The law goes into effect in January of 2017.
In essence the Bill is designed to facilitate the ability of successors to a deceased borrower (hence the reference to the Bill as the “Survivors Bill of Rights”) and lender/servicers to communicate. In addition, and in appropriate circumstance the Bill will allow a successor to assume a loan, obtain foreclosure prevention alternatives, and/or sue under the CA HOBR.
The following is a recap of the highlights of the legislation with some comments and questions. Please note the footnotes.
California SB 1150 (Survivor Bill of Rights): Passed 9.29.16, effective January 2017.
General:
SB 1150 clarifies the responsibilities of a mortgage servicer when a borrower dies and leaves a surviving homeowner who is not on the loan.
The enacted statute applies to a first lien mortgage that is secured by an owner occupied residential 1-4 unit property that was the principal residence of the deceased borrower. The statute does not apply to a “smaller lender” that forecloses on 175 or fewer 1-4 residential properties during its preceding annual reporting period (Civ. Code §2920.7(j)).
SB 1150 does not require a lender/servicer to allow assumption of a loan or obtain a modification, but requires that the lender/servicer provide information about loan assumption and foreclosure avoidance options.
Particular Provisions:
Restrictions on Recording NOD to Allow Successors Time to Provide Proof of Status: Civ. Code § 2920.7(a) provides that the servicer cannot record a NOD until it does both of the following: (1) provides the claimant a reasonable period of time, not less than 30 days, to provide proof of the borrower’s death; and (2) provides the claimant with a reasonable period of time, not less than 90 days, to provide proof of that person’s interest in the real property.
Note: This could add at least 90 days to the pre-foreclosure process if the borrower’s death occurs during the pre-foreclosure contact period under the CA HOBR.
Who can be a Successor? Civ. Code §2920.7(i) (4), defines who can be a successor. The statute requires a “natural person” and one of the enumerated persons described in the statute, who must also have occupied the property within the last six continuous months prior to deceased’s death, and who currently resides on the property. [1]
Documentation required of a Successor: Civ. Code § 2920.7 (i) (3), defines what “reasonable documentation” is required to establish successor status [2] and if specified documents listed are not available, “what is deemed sufficient by the mortgage servicer.”
Becoming a Successor on the Loan and Loan Assumption: Civ. Code §2920.7(b)(1) and (2) provide that, once the claimant provides the required proof, he or she is defined as a “successor in interest” The statute specifically states that there can be more than one successor (Civ. Code § 2920.7(a)(2).
Note: This can result in inconsistent rights e.g. if not all successors will assume the loan. The statute provides that applicable state and federal laws govern assumption rights and that where multiple successors will not agree to proceed as co-borrowers or applicants, the servicer can require that any non-applicant consent to the application for loan assumption (Civ. Code §2920.7(b)(2).
Note: No time to for the successor to assume the loan or apply for loss mitigation is specified, which can lead to disputes.
Providing Information to Successors and Assumption of Loan: Civ. Code §2920.7(c) provides that, within 10 days of the claimant becoming a successor, the servicer must provide the successor with key information on the loan. The statute does not address the fact that providing some of that information could violate applicable Federal privacy law.
Successor rights to Assume Loan or Qualify for Foreclosure Prevention Rights: Civ. Code §2920.7(d) provides that the servicer shall allow a successor to: (1) Apply to assume the loan (subject to applicable investor requirements and guidelines), or; (2) Where the successor of an assumable loan also wants a foreclosure prevention alternative, simultaneously apply for both.
Note: Loan assumption is dependent on the creditworthiness of the successor, subject to applicable investor requirements and guidelines (Civ. Code §292.7(d) (1)). However, the statute does not provide any guidance on how long the servicer must give the successor to assume the loan or apply for loss mitigation.
A Qualified Successor has Borrower HOBR Rights: Civ. Code §2920.7(e) (1), gives a qualifying successor the rights as a borrower under HOBR.
Note: The statute does not address a scenario where the servicer had already complied with the provisions of HOBR as to the borrower and then the borrower dies prior to the recording of the NOD. Will this require a restart of the HOBR pre-foreclosure time clock?
A Qualified Successor has Rights to Assert Injunctive and Damage Claims under CA HOBR: 2920.7(e)(2) through (4) give the successor the same private right of action afforded to a former borrower under the CA HOBR, including the right to an injunction (pre-sale), damages (post-recording of the TDUS) and attorneys’ fees.
When Statute Conflicts with Federal Law: Civ. Code §2920.7 (k) resolves problems with potential with federal [CFPB] servicing guidelines , by providing that compliance with successor provisions in 12 CFR part 1024 and 1026 will be deemed compliance with the requirements of this statute.
A Successor who Has Filed a Legal Action re the Property is not Covered by the Statute: Civ. Code §2920.7(l).
One thing is certain: Every lender and servicer should coordinate the requirements of the Bill with corresponding federal regulations on successor status, and state and federal regulations re loan assumption. Also, CA HOBR procedures should be expanded to include mandated review and communications when a successor claim is raised and a successor is confirmed. If not, you are inviting more litigation and delay.
[1] Civ. Code §2920.7(i)(3) (4): “Successor in interest” means a natural person who provides the mortgage servicer with notification of the death of the mortgagor or trustor and reasonable documentation showing that the person is the spouse, domestic partner, joint tenant as evidenced by grant deed, parent, grandparent, adult child, adult grandchild, or adult sibling of the deceased borrower, who occupied the property as his or her principal residence within the last six continuous months prior to the deceased borrower’s death and who currently resides in the property [2] Civ. Code §2920.7(i)(3) “Reasonable documentation” means copies of the following documents, as may be applicable, or, if the relevant documentation listed is not available, other written evidence of the person’s status as successor in interest to the real property that secures the mortgage or deed of trust deemed sufficient by the mortgage servicer: (A) In the case of a personal representative, letters as defined in Section 52 of the Probate Code. (B) In the case of devisee or an heir, a copy of the relevant will or trust document. (C) In the case of a beneficiary of a revocable transfer on death deed, a copy of that deed. (D) In the case of a surviving joint tenant, an affidavit of death of the joint tenant or a grant deed showing joint tenancy. (E) In the case of a surviving spouse where the real property was held as community property with right of survivorship, an affidavit of death of the spouse or a deed showing community property with right of survivorship. (F) In the case of a trustee of a trust, a certification of trust pursuant to Section 18100.5 of the Probate Code. (G) In the case of a beneficiary of a trust, relevant trust documents related to the beneficiary’s interest.
The cf_use_ob cookie informs Cloudflare to fetch the requested resource from the Always Online cache on the designated port. Applicable values are: 0, 80, and 443. The cf_ob_info and cf_use_ob cookies are persistent cookies that expire after 30 seconds.
session
__cfwaitingroom
The __cfwaitingroom cookie is only used to track visitors that access a waiting room enabled host and path combination for a zone. Visitors using a browser that does not accept cookies cannot visit the host and path combination while the waiting room is active.
session
cf_chl_rc_i
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
cf_chl_rc_ni
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
cf_chl_rc_m
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
__cfruid
Used by the content network, Cloudflare, to identify trusted web traffic.
session
__cf_bm
Cloudflare's bot products identify and mitigate automated traffic to protect your site from bad bots. Cloudflare places the __cf_bm cookie on End User devices that access Customer sites that are protected by Bot Management or Bot Fight Mode. The __cf_bm cookie is necessary for the proper functioning of these bot solutions.
session
__cflb
When enabling session affinity with Cloudflare Load Balancer, Cloudflare sets a __cflb cookie with a unique value on the first response to the requesting client. Cloudflare routes future requests to the same origin, optimizing network resource usage. In the event of a failover, Cloudflare sets a new __cflb cookie to direct future requests to the failover pool.
session
_cfuvid
The _cfuvid cookie is only set when a site uses this option in a Rate Limiting Rule, and is only used to allow the Cloudflare WAF to distinguish individual users who share the same IP address.
session
cf_clearance
Whether a CAPTCHA or Javascript challenge has been solved.
session
__cfseq
Sequence rules uses cookies to track the order of requests a user has made and the time between requests and makes them available via Cloudflare Rules. This allows you to write rules that match valid or invalid sequences. The specific cookies used to validate sequences are called sequence cookies.
session
cf_ob_info
The cf_ob_info cookie provides information on: The HTTP Status Code returned by the origin web server. The Ray ID of the original failed request. The data center serving the traffic
session
These cookies are needed for adding comments on this website.
Name
Description
Duration
comment_author
Used to track the user across multiple sessions.
Session
comment_author_email
Used to track the user across multiple sessions.
Session
comment_author_url
Used to track the user across multiple sessions.
Session
Name
Description
Duration
cookietest
Session
Google reCAPTCHA helps protect websites from spam and abuse by verifying user interactions through challenges.
Name
Description
Duration
_GRECAPTCHA
Google reCAPTCHA sets a necessary cookie (_GRECAPTCHA) when executed for the purpose of providing its risk analysis.
179 days
Google Tag Manager simplifies the management of marketing tags on your website without code changes.
Name
Description
Duration
td
Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator.
session
cookiePreferences
Registers cookie preferences of a user
2 years
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
Google Ads is an online advertising platform that enables businesses to create targeted ads displayed on Google search results and partner sites.
Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads.
90 Days
_gcl_gs
Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads.
90 Days
_gcl_gb
Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads.
90 Days
_gac_gb_
Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads.
90 Days
FPGCLGB
Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads.
90 Days
FPGCLAW
Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads.
90 Days
ADS_VISITOR_ID
Cookie required to use the options and on-site web services
2 months
__Secure-3PSIDCC
Targeting cookie. Used to create a user profile and display relevant and personalised Google Ads to the user.
2 years
__Secure-3PSIDTS
Targeting cookie. Used to create a user profile and display relevant and personalised Google Ads to the user.
2 years
__Secure-1PSIDTS
Targeting cookie. Used to create a user profile and display relevant and personalised Google Ads to the user.
2 years
__Secure-1PAPISID
Targeting cookie. Used to create a user profile and display relevant and personalised Google Ads to the user.
2 years
__Secure-3PSID
Targeting cookie. Used to profile the interests of website visitors and display relevant and personalised Google ads.
2 years
Conversion
Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads.
90 days
__Secure-1PSID
Targeting cookie. Used to create a user profile and display relevant and personalised Google Ads to the user.
2 years
__Secure-1PSIDCC
Targeting cookie. Used to create a user profile and display relevant and personalised Google Ads to the user.
2 years
__Secure-3PAPISID
Profiles the interests of website visitors to serve relevant and personalised ads through retargeting.
2 years
AEC
AEC cookies ensure that requests within a browsing session are made by the user, and not by other sites. These cookies prevent malicious sites from acting on behalf of a user without that user's knowledge.
6 months
Google Maps is a web mapping service providing satellite imagery, real-time navigation, and location-based information.