DeltaBreen File Requests

No. The form runs in a frame served by Share, which a page's own scripts cannot read, and the files are encrypted before they leave the visitor's device.

Share shows a file request only on the websites listed for it. In Share, press Add to your website on the request and add your site's address exactly as visitors see it (with or without www). If a security plugin sets a Content-Security-Policy on your site, it must allow frames from your Share address (frame-src). Visitors whose browser still cannot show the form get a link to open it in a new tab.

Yes. In the block's settings, set "Load the form" to "After the visitor clicks a button". Nothing loads from Share until then.

Yes, on a page they sign in to. Connect this site, make a file request for people you invite, and in Share, under Requests, tick "Give each client signed in to this website their own place on a file request" for this site. Then add the Share client's file request block and choose the request. Each signed-in client gets their own access code without typing it, Share never emails them, and their uploads are listed under their address. Under Settings, Share, you can limit it to some roles. Share limits how many new people the site adds a day, so a site someone breaks into costs you little; it can never read what clients send.

Yes, with the Share documents block. Connect this site, then in Share, under Requests, tick "Show files you send in clients' portals on this website" for this site: Share shows a security code, which must match the one under Settings, Share here. Then, when you send a file in Share, choose "Show it in their portal" and name the client. The link is sealed to this site's own key, so Share cannot read it; the client sees the file when they sign in here, and opens it after confirming their email with a code.

Yes, if your Share plan includes ID checks. Connect this site, and in Share, under Requests, tick "Let clients signed in to this website start an ID check" for this site and choose what each check covers (a sanctions screen, a proof of address, a copy of the pictures). Then add the Share ID check block to a page your clients sign in to. A client presses "Check my ID", confirms their email address with a code Share sends them, and photographs their ID document and takes a selfie on Share's page; Didit checks them. You open the result in Share. This site learns only whether the check passed, is being looked at or did not, and when. Each check counts toward your month, and Share limits how many this site may start a day.

Yes. In the classic editor or a page builder such as Elementor, Beaver Builder or SiteOrigin Page Builder, paste a shortcode: [deltabreen_file_request link="…"] for a file request, [deltabreen_client_request id="…"] for a client's own place (Settings, Share lists each request's shortcode once the site is connected), [deltabreen_id_check] for the ID check and [deltabreen_documents] for the documents. Blocks and shortcodes take the full width of a container that centres its items, as a Group set to Stack or Row, Elementor, Kadence Blocks and GenerateBlocks can. To make one narrower, give it a width in the builder.

Yes. In the block's settings, under After sending, search for one of your pages or paste a link; with a shortcode, add redirect="/thank-you/". The visitor sees the form's own "Sent" for a moment first. On a checklist, they go there once everything you asked for has arrived. For analytics, the page also hears each send: document.addEventListener( 'deltabreen-share:sent', function ( e ) { /* e.detail.complete */ } );. Nothing about the files, the visitor or the key crosses to your page.

Yes. On a phone the visitor can take a photo of a document with the camera, or choose a file. If their connection drops during a large upload, the form offers to carry on where it stopped when they choose the same file again, and a visitor can cancel an upload at any time.

Files never reach your website or its server, so nothing sent can run there. Because they are encrypted end to end, Share cannot scan them either: open files from people you do not know with the care you would give an email attachment.

Yes. The pages hold nothing about who is looking at them, so a page cache can keep them, and the plugin marks its one script so that WP Rocket, LiteSpeed Cache, SiteGround Optimizer, Autoptimize, Jetpack Boost and Cloudflare Rocket Loader leave it alone. Otherwise a client's blocks would stay blank until they first moved the mouse.

It sets no tracking cookies. While an upload is under way, the visitor's browser keeps a note of it so they can carry on after an interruption; the note goes when the upload finishes, is cancelled or is discarded. If your consent tool should hold the form back until a visitor agrees, set "Load the form" to "After the visitor clicks a button".

Yes. Each site connects to Share on its own and keeps its own clients' codes. Removing someone from a site stops that site's codes for them, and deleting the plugin from the network ends every site's connection.

With WordPress's own tools, Tools, Export Personal Data and Erase Personal Data. The plugin keeps only the access codes it got for a signed-in client on your file requests; an export lists them without the codes, and erasing stops them in Share. What the person sent you stays in your Share workspace: delete it there if you need to.

Email contact@deltabreen.eu with "Security report" as the subject, as https://share.deltabreen.eu/.well-known/security.txt says, and not in the support forum.

In your Share inbox, after you unlock it with your encryption password. Share emails whoever made the request when files or answers arrive.

The plugin is free. Share's free plan includes one file request; its paid plans are listed at https://share.deltabreen.eu/pricing?ref=wordpress-org.