Trust Center Changelog

A firm can add a key from its own Stripe account and send the preparer payouts it approves. Each payment is made from the firm's Stripe account, on the firm's instruction. GoRefer never holds or moves the money, and preparers enter their bank details on Stripe's form, not GoRefer's.

Sub-processors: Stripe's entry now includes these payouts and the preparer names, email addresses and amounts they need. The Data Processing Addendum and the Terms describe them too.

Sub-processors: Stripe processes the client invoice payments a firm takes on its own Stripe account. The firm is the merchant of record. GoRefer's platform fee, shown on our pricing page and in your account, is deducted automatically from each client payment.

Hosting: GoRefer runs on its own server at Google Cloud. Amazon Web Services stores files, sends email and keeps our backups. Earlier pages named a different database provider and hosting region.

Backups: we back up the full database every night, encrypt each backup, store it with a provider separate from the database server and keep it for 30 days, and we have tested restoring from a backup. We removed recovery-time and data-loss targets and backup schedules that do not reflect what we run.

Sub-processors: the list now names every service provider, with the integrations a firm chooses to connect shown separately. It no longer describes payouts through Stripe, which GoRefer does not make.

Statements about audits, certifications, penetration tests, staff screening and training, network tools and documents we do not have. The Penetration Testing page is gone, and the Trust Portal now offers only documents that exist.

Incident notice: if we confirm unauthorized access to your firm's client information, we notify your firm's administrators within 72 hours of confirming it. GoRefer maintains a written incident response plan and a written information security program.

Compliance now leads with the US laws that apply to tax firms: GLBA and the FTC Safeguards Rule, IRC §7216 and state privacy laws. The service is for US businesses.

Gio cases, case documents and their files are kept for the life of the firm's account and deleted with the workspace after cancellation. Only Gio's finished background-job logs expire, after 90 days. The earlier 90-day case cleanup is gone.

The Microsoft sub-processor entry now says plainly how uploaded documents are handled: our AI provider reads document images to extract their text, and the documents are stored with the firm's records. Before any text is sent to an AI model, Social Security numbers, ITINs, EINs and bank account and routing numbers are masked.

Smart Intake now shows clients a short notice before AI reads their documents, with a way to continue without AI.

Business Continuity now gives the same 30-day backup retention as the Data Retention page. Records on legal hold are kept until the hold is released.

Privacy, Safeguards and Data Retention now describe the same process: a firm's workspace is deleted after the deletion date shown at cancellation, while billing and payment records and the security audit trail are kept.

Stated that deleted data can remain in backups for up to 30 days, and that each deletion is recorded and can be confirmed on request.

Replaced "per retention schedule" with the actual lifetime of firm and client data, and scoped the communications and analytics periods to the data they cover.

Clarified that Security Hub is a platform-operations tool and distinguished web token lifetimes from the extension session cap.

Scoped field encryption, AI context and cookie descriptions to the relevant workflows.

Replaced cloud, network, staff-training, backup and incident-history statements we could not verify with our policy targets and details of what you can request.

Corrected scoped decrypted-intake access, key migration, account-retention and Gio case-cleanup descriptions.

Disclosed marketing-site Meta Pixel and raw document-recognition processing separately from case-context redaction.

Removed statements we could not support — that all controls were verified, that independent testing had taken place, and about HIPAA — and separated policy targets from completed assessments.

Data export audit-logging documentation updated; coverage and tamper-evidence depend on the export workflow

Documented enhancement areas include password policy configuration, vulnerability scanning and session timeout enforcement; ask us for their current status

AI Security & Governance page (/trust/ai-security)

Business Continuity page (/trust/business-continuity)

Employee Security page (/trust/employee-security)

Network Security page (/trust/network-security)

Trust Center hub: scorecard, key facts, grouped navigation and our core data commitments

Sub-processors page grouped by category, with a data-sensitivity level for each provider

Trust Center at /trust

Dedicated Security, Privacy, Compliance, Infrastructure, and Access Control pages

Sub-processors page

Data Protection and Data Retention pages with structured tables

Incident Response page

Vulnerability Disclosure policy with responsible disclosure commitments

Data Processing Addendum (DPA) summary page

Trust Portal for document requests

Security contact form (direct disclosure to security@gorefer.io)

Sidebar navigation with grouped sections and active-page highlighting

The old /security page now redirects to /trust/security

Security Hub section with firm health score details

Field-level encryption list (SSN, EIN, bank accounts, driver's license)

Added AI service providers to subprocessors list

Initial security & compliance page at /security

Security overview: encryption, firm separation, roles, sign-in, monitoring and infrastructure

Privacy Policy (v1.0)

Terms of Service (v1.0)

Cookie Policy