How fund and founder data is protected

Every deal, document, interview, room, guest and search index row carries its fund, and the database refuses links between records of different funds.

The same check runs for pages, APIs, search, AI answers, background jobs, notifications and exports, always at the narrowest scope: fund, deal, folder, file.

Asking for another fund's record answers "not found", without saying whether it exists, and the attempt is recorded as a security event.

A founder who applies to two funds has two separate records. Nothing is shared or matched across funds.

Every request is routed by its address: a fund's portal answers only portal pages, app pages answer only on the app's own address, and anything else gets a plain not found page. Portals run on a separate domain from the investor app, so founder and investor sessions are never shared.

Founders sign in with a one-time code sent to their email. The session cookie works only on that fund's portal, and a cookie replayed on another portal is refused and logged.

Founders use one Delsivo account for every fund. A portal gets a sign-in only after the founder approves that fund, through a single-use code that lasts 60 seconds and works only on that portal's own address.

A custom domain is attached only after a DNS ownership record checks out, and daily checks catch a domain that stops pointing at the portal.

Funds brand portals with logos, colours, fonts from a list and copy. Custom CSS and JavaScript aren't offered, and uploaded logos are cleaned of scripts.

Every portal footer has a link to report a portal that looks like phishing or impersonation. Reports alert Delsivo staff, who can suspend the portal.

Every upload is scanned for malware before anyone can preview it, AI can read it or it is added to search. Suspicious files stay quarantined.

Decks, interview recordings and room documents are kept under private storage paths, encrypted at rest, with keys generated by the server rather than from file names.

Download links last 15 minutes at most and are issued only after a permission check on that exact file version. Emails link to the page, never to the file.

Deleting a file or a deal stops access at once, then removes previews, extracted text, search index rows and AI caches.

Data room guests are named, their access expires, and preview-only guests never get a download link. Revoking a guest ends their access at once.

Search and AI answers are filtered by the asker's permissions before anything reaches a prompt, so a restricted file can't leak through a summary or citation.

Founder phone numbers and email addresses are replaced before content goes to an AI provider, unless the task needs them.

AI providers are used under terms that don't train on submitted content. Those terms are confirmed for each provider before any fund's content is processed.

Decks, room files and web pages are handled as data, never as instructions. The AI has no tools that send messages, change stages or change permissions.

Every finding must cite a real deck slide, transcript timestamp or document page. Quotes that can't be found in the source are dropped.

AI never changes a deal stage, passes on a founder or sends a message. A Partner approves every message to a founder, and overrides need a recorded reason.

Nobody can create an account in the investor app without an invite to their email. Passwords are stored hashed, and a reset signs out every other device.

Required for Delsivo staff. Offered and recommended to every fund role, and required for the roles a fund asks for.

Admin, Partner, Analyst, Committee member and Guest expert each see only what their role and the deal's access allow. Founders never see internal ratings or notes.

Delsivo staff can view a fund's workspace only after a fund Admin grants time-limited, read-only access. Data room files and recordings stay hidden unless the grant says otherwise.

Staff can lock an account and end all its sessions at once, with a reason recorded in the audit trail.

The audit trail, security events and AI call logs live in their own database, apart from fund data.

Actions by fund users and Delsivo staff are recorded with who, what, when and from where.

Each AI call records its purpose, model, prompt and rubric version and references to the documents used, never deck text, transcripts or contact details.

Failed sign-ins, bot checks, rate-limit hits, cross-fund attempts, quarantined files and access by revoked guests are recorded, and serious ones alert staff.

Logs never contain passwords, sign-in codes, tokens, deck or transcript text, or full founder contact details.

Public forms, sign-in, founder sign-in codes, applications and portal reports use Cloudflare Turnstile to tell people from bots.

Every public endpoint is rate limited across servers, and every input is validated with length limits.

Events from payment, email, transcription and scanning providers are accepted only with a valid signature.

HTTPS everywhere with HSTS, a content security policy, and protection against framing and content sniffing. Microphone and camera are allowed only on interview pages.

Payments run on Stripe's hosted checkout and Razorpay Checkout. Delsivo receives only the card brand and last 4 digits.